feat(unstable): Rename unstable session/stop method to session/close

This better encapsulates the usage and differentiates it more from
session/cancel

Author: benbrandt

Cargo.toml

@@ -22,7 +22,7 @@ unstable = [
     "unstable_session_list",
     "unstable_session_model",
     "unstable_session_resume",
-    "unstable_session_stop",
+    "unstable_session_close",
     "unstable_session_usage",
     "unstable_message_id",
     "unstable_boolean_config",
@@ -34,7 +34,7 @@ unstable_session_info_update = []
 unstable_session_list = []
 unstable_session_model = []
 unstable_session_resume = []
-unstable_session_stop = []
+unstable_session_close = []
 unstable_session_usage = []
 unstable_message_id = []
 unstable_boolean_config = []

docs/docs.json

@@ -123,7 +123,7 @@
               "rfds/diff-delete",
               "rfds/boolean-config-option",
               "rfds/elicitation",
-              "rfds/session-stop"
+              "rfds/session-close"
             ]
           },
           {
@@ -206,6 +206,11 @@
       "source": "/registry",
       "destination": "/get-started/registry",
       "permanent": false
+    },
+    {
+      "source": "/rfds/session-stop",
+      "destination": "/rfds/session-close",
+      "permanent": true
     }
   ]
 }

docs/protocol/draft/schema.mdx

@@ -196,6 +196,71 @@ See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/exte
   The ID of the session to cancel operations for.
 </ResponseField>
 
+<a id="session-close"></a>
+### <span class="font-mono">session/close</span>
+
+**UNSTABLE**
+
+This capability is not part of the spec yet, and may be removed or changed at any point.
+
+Closes an active session and frees up any resources associated with it.
+
+This method is only available if the agent advertises the `session.close` capability.
+
+The agent must cancel any ongoing work (as if `session/cancel` was called)
+and then free up any resources associated with the session.
+
+#### <span class="font-mono">CloseSessionRequest</span>
+
+**UNSTABLE**
+
+This capability is not part of the spec yet, and may be removed or changed at any point.
+
+Request parameters for closing an active session.
+
+If supported, the agent **must** cancel any ongoing work related to the session
+(treat it as if `session/cancel` was called) and then free up any resources
+associated with the session.
+
+Only available if the Agent supports the `session.close` capability.
+
+**Type:** Object
+
+**Properties:**
+
+<ResponseField name="_meta" type={"object | null"} >
+  The _meta property is reserved by ACP to allow clients and agents to attach additional
+metadata to their interactions. Implementations MUST NOT make assumptions about values at
+these keys.
+
+See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/extensibility)
+
+</ResponseField>
+<ResponseField name="sessionId" type={<a href="#sessionid">SessionId</a>} required>
+  The ID of the session to close.
+</ResponseField>
+
+#### <span class="font-mono">CloseSessionResponse</span>
+
+**UNSTABLE**
+
+This capability is not part of the spec yet, and may be removed or changed at any point.
+
+Response from closing a session.
+
+**Type:** Object
+
+**Properties:**
+
+<ResponseField name="_meta" type={"object | null"} >
+  The _meta property is reserved by ACP to allow clients and agents to attach additional
+metadata to their interactions. Implementations MUST NOT make assumptions about values at
+these keys.
+
+See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/extensibility)
+
+</ResponseField>
+
 <a id="session-fork"></a>
 ### <span class="font-mono">session/fork</span>
 
@@ -897,71 +962,6 @@ See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/exte
 
 </ResponseField>
 
-<a id="session-stop"></a>
-### <span class="font-mono">session/stop</span>
-
-**UNSTABLE**
-
-This capability is not part of the spec yet, and may be removed or changed at any point.
-
-Stops an active session and frees up any resources associated with it.
-
-This method is only available if the agent advertises the `session.stop` capability.
-
-The agent must cancel any ongoing work (as if `session/cancel` was called)
-and then free up any resources associated with the session.
-
-#### <span class="font-mono">StopSessionRequest</span>
-
-**UNSTABLE**
-
-This capability is not part of the spec yet, and may be removed or changed at any point.
-
-Request parameters for stopping an active session.
-
-If supported, the agent **must** cancel any ongoing work related to the session
-(treat it as if `session/cancel` was called) and then free up any resources
-associated with the session.
-
-Only available if the Agent supports the `session.stop` capability.
-
-**Type:** Object
-
-**Properties:**
-
-<ResponseField name="_meta" type={"object | null"} >
-  The _meta property is reserved by ACP to allow clients and agents to attach additional
-metadata to their interactions. Implementations MUST NOT make assumptions about values at
-these keys.
-
-See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/extensibility)
-
-</ResponseField>
-<ResponseField name="sessionId" type={<a href="#sessionid">SessionId</a>} required>
-  The ID of the session to stop.
-</ResponseField>
-
-#### <span class="font-mono">StopSessionResponse</span>
-
-**UNSTABLE**
-
-This capability is not part of the spec yet, and may be removed or changed at any point.
-
-Response from stopping a session.
-
-**Type:** Object
-
-**Properties:**
-
-<ResponseField name="_meta" type={"object | null"} >
-  The _meta property is reserved by ACP to allow clients and agents to attach additional
-metadata to their interactions. Implementations MUST NOT make assumptions about values at
-these keys.
-
-See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/extensibility)
-
-</ResponseField>
-
 ## Client
 
 Defines the interface that ACP-compliant clients must implement.
@@ -3387,12 +3387,35 @@ This capability is not part of the spec yet, and may be removed or changed at an
 Whether the agent supports `session/resume`.
 
 </ResponseField>
-<ResponseField name="stop" type={<><span><a href="#sessionstopcapabilities">SessionStopCapabilities</a></span><span> | null</span></>} >
+<ResponseField name="stop" type={<><span><a href="#sessionclosecapabilities">SessionCloseCapabilities</a></span><span> | null</span></>} >
   **UNSTABLE**
 
 This capability is not part of the spec yet, and may be removed or changed at any point.
 
-Whether the agent supports `session/stop`.
+Whether the agent supports `session/close`.
+
+</ResponseField>
+
+## <span class="font-mono">SessionCloseCapabilities</span>
+
+**UNSTABLE**
+
+This capability is not part of the spec yet, and may be removed or changed at any point.
+
+Capabilities for the `session/close` method.
+
+By supplying `\{\}` it means that the agent supports closing of sessions.
+
+**Type:** Object
+
+**Properties:**
+
+<ResponseField name="_meta" type={"object | null"} >
+  The _meta property is reserved by ACP to allow clients and agents to attach additional
+metadata to their interactions. Implementations MUST NOT make assumptions about values at
+these keys.
+
+See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/extensibility)
 
 </ResponseField>
 
@@ -3818,29 +3841,6 @@ See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/exte
 
 </ResponseField>
 
-## <span class="font-mono">SessionStopCapabilities</span>
-
-**UNSTABLE**
-
-This capability is not part of the spec yet, and may be removed or changed at any point.
-
-Capabilities for the `session/stop` method.
-
-By supplying `\{\}` it means that the agent supports stopping of sessions.
-
-**Type:** Object
-
-**Properties:**
-
-<ResponseField name="_meta" type={"object | null"} >
-  The _meta property is reserved by ACP to allow clients and agents to attach additional
-metadata to their interactions. Implementations MUST NOT make assumptions about values at
-these keys.
-
-See protocol docs: [Extensibility](https://agentclientprotocol.com/protocol/extensibility)
-
-</ResponseField>
-
 ## <span class="font-mono">SessionUpdate</span>
 
 Different types of updates that can be sent during session processing.

docs/rfds/session-stop.mdx docs/rfds/session-close.mdxdocs/rfds/session-stop.mdx renamed to docs/rfds/session-close.mdx

@@ -1,5 +1,5 @@
 ---
-title: "Stopping active sessions"
+title: "Closing active sessions"
 ---
 
 Author(s): [@SteffenDE](https://github.com/SteffenDE)
@@ -8,7 +8,7 @@ Author(s): [@SteffenDE](https://github.com/SteffenDE)
 
 > What are you proposing to change?
 
-We propose adding the ability to stop active sessions. This allows the agent to free up any memory
+We propose adding the ability to close active sessions. This allows the agent to free up any memory
 and threads/subprocesses associated with that session.
 
 ## Status quo
@@ -29,31 +29,31 @@ lead to a bad user experience.
 
 > What are you proposing to improve the situation?
 
-Add a new `session/stop` method. If supported, the agent **must** cancel any ongoing work
+Add a new `session/close` method. If supported, the agent **must** cancel any ongoing work
 related to the session (treat it as if `session/cancel` was called) and then free up any resources
 associated with the session.
 
 ## Shiny future
 
 > How will things will play out once this feature exists?
 
-Clients can track what sessions are actively used by a user and automatically stop old sessions.
+Clients can track what sessions are actively used by a user and automatically close old sessions.
 
 ## Implementation details and plan
 
 > Tell me more about your implementation. What is your detailed implementation plan?
 
-We propose to add a new `"session/stop"` method. Agents must declare this option is
-available by returning `session: { stop : {} }` in their capabilities. The object is reserved
+We propose to add a new `"session/close"` method. Agents must declare this option is
+available by returning `session: { close : {} }` in their capabilities. The object is reserved
 to declare future capabilities.
 
-Then the client would be able to stop a specific session with:
+Then the client would be able to close a specific session with:
 
 ```json
 {
   "jsonrpc": "2.0",
   "id": 1,
-  "method": "session/stop",
+  "method": "session/close",
   "params": {
     "sessionId": "sess_789xyz"
   }
@@ -76,4 +76,5 @@ seems like a good idea.
 
 ## Revision history
 
+2026-03-09: Rename from session/stop to session/close
 2026-02-24: Initial draft

docs/updates.mdx

@@ -5,9 +5,9 @@ rss: true
 ---
 
 <Update label="February 24, 2026" tags={["RFD"]}>
-## session/stop RFD moves to Draft stage
+## session/close RFD moves to Draft stage
 
-The RFD for allowing agents to close or stop a given session has been moved to Draft stage. Please review the [RFD](./rfds/session-stop) for more information on the current proposal and provide feedback as work on the implementation begins.
+The RFD for allowing agents to close a given session has been moved to Draft stage. Please review the [RFD](./rfds/session-close) for more information on the current proposal and provide feedback as work on the implementation begins.
 
 </Update>
 

schema/meta.unstable.json

@@ -3,6 +3,7 @@
     "authenticate": "authenticate",
     "initialize": "initialize",
     "session_cancel": "session/cancel",
+    "session_close": "session/close",
     "session_fork": "session/fork",
     "session_list": "session/list",
     "session_load": "session/load",
@@ -11,8 +12,7 @@
     "session_resume": "session/resume",
     "session_set_config_option": "session/set_config_option",
     "session_set_mode": "session/set_mode",
-    "session_set_model": "session/set_model",
-    "session_stop": "session/stop"
+    "session_set_model": "session/set_model"
   },
   "clientMethods": {
     "fs_read_text_file": "fs/read_text_file",