Summary
Include conversation forking configuration in scaffolded projects. Users exploring multiple solution paths need the ability to branch a conversation at any point and resume each fork independently.
Requirements
- Add
branching section to scaffolded agent.yaml with enabled toggle and max_forks_per_session.
- Document the fork API endpoints (
POST /v1/sessions/{id}/fork, GET /v1/sessions/{id}/forks) in the scaffolded README.
- Note the session store schema requirement: message-level addressing is needed for fork-point identification.
- Scaffold a YAML comment explaining the copy-on-write fork model.
Companion Issues
Companion issues filed on fips-agents/agent-template, fips-agents/gateway-template, fips-agents/ui-template, and fips-agents/examples.
Size
S
Summary
Include conversation forking configuration in scaffolded projects. Users exploring multiple solution paths need the ability to branch a conversation at any point and resume each fork independently.
Requirements
branchingsection to scaffoldedagent.yamlwithenabledtoggle andmax_forks_per_session.POST /v1/sessions/{id}/fork,GET /v1/sessions/{id}/forks) in the scaffolded README.Companion Issues
Companion issues filed on fips-agents/agent-template, fips-agents/gateway-template, fips-agents/ui-template, and fips-agents/examples.
Size
S