@@ -24,7 +24,7 @@ Therefore we want to be able to fork a session, issue additional messages, and t
2424
2525> What are you proposing to improve the situation?
2626
27- One possible solution is to add a session/fork command .
27+ To add a " session/fork" method .
2828
2929## Shiny future
3030
@@ -41,26 +41,27 @@ functionality like editing previous messages and similar.
4141
4242> Tell me more about your implementation. What is your detailed implementation plan?
4343
44- <!--
45- Use this section to add details that were not covered in the " What we propose to do about it" section and also include an implementation plan with phases.
44+ We propose to add a new "session/fork" method. Agents must declare this option is
45+ available by returning ` forkSession: {} ` in its capabilities. The object is reserved
46+ to declare future capabilities, such as forking from a message, a tool call, or similar.
4647
47- Note: This section is OPTIONAL and NOT RECOMMENDED when RFDs are first opened. It can distract from the discussion of the problem.
48- -->
48+ A proof of concept is available here: https://github.com/zed-industries/claude-code-acp/pull/145
4949
5050## Frequently asked questions
5151
5252> What questions have arisen over the course of authoring this document or during subsequent discussions?
5353
54- <!--
55- Keep this section up-to-date as discussion proceeds. The goal is to capture major points that came up on a PR or in a discussion forum -- and if they reoccur, to point people to the FAQ so that we can start the dialog from a more informed place.
56- -->
54+ ** Q: Should a new method be introduced or should "session/new" be expanded?**
55+
56+ They must be different because they will effectively require different options.
57+ For example, "session/new" has options such as capabilities and MCP which are not
58+ recommended to be set when forking, as the context being forked was built with other
59+ tools, and forking may accept a messageId for checkpoints.
5760
5861### What alternative approaches did you consider, and why did you settle on this one?
5962
6063None. This proposal is inspired by the abilities exposed in Claude Agent SDK. It must be validated against other agents too.
6164
62- <!-- You...may want to adjust this. -->
63-
6465## Revision history
6566
66- <!-- If there have been major updates to this RFD, you can include the git revisions and a summary of the changes. -->
67+ 2025-11-17: Mentioned capabilities format, updated FAQ.
0 commit comments