From 840aefc0a01992561b90fda54920146e781d1dbd Mon Sep 17 00:00:00 2001 From: Jeremy Michelson Date: Thu, 16 Jul 2026 16:13:13 -0500 Subject: [PATCH] docs(rfd): Forking of existing sessions Edited the expected response from a 'session/fork' request to include the sessionId of the new fork. --- docs/rfds/session-fork.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/rfds/session-fork.mdx b/docs/rfds/session-fork.mdx index 55ccbf665..11ab3edfe 100644 --- a/docs/rfds/session-fork.mdx +++ b/docs/rfds/session-fork.mdx @@ -63,7 +63,7 @@ Then the client would be able to request a fork of the given session: The request expects the same options as `session/load`, such as `cwd` and `mcpServers`. -Similarly, the agent would respond with optional data such as config options, the same as `session/load`. +Similarly, the agent would respond with the `sessionId` of the new session, plus optional data such as config options, the same as `session/new`. Agents may reply with an error if forking of that specific session or with the given options is not supported, for example if the agent does not support forking with a different working directory than the initial session.