session/delete method lets Clients remove sessions from an Agent’s session/list results, so users can clean up session history from any ACP Client.
Before deleting sessions, Clients MUST first complete the initialization phase and verify the Agent supports this capability.
Checking support
Before attempting to delete a session, Clients MUST verify that the Agent supports this capability by checking thesessionCapabilities.delete field in the initialize response:
sessionCapabilities.delete is omitted or null, the Agent does not support deleting sessions and Clients MUST NOT attempt to call session/delete. Supplying {} means the Agent supports the method.
Deleting a session
Clients delete a session by callingsession/delete with the session ID to remove from session history:
Semantics
- Deleted sessions no longer appear in future
session/listresults. - Deleting an already-deleted session, or a session that never existed, SHOULD succeed silently.
- Clients SHOULD treat a
-32002response tosession/deleteas a successful delete. - Agents may implement soft delete or hard delete. ACP only specifies the user-facing session-list behavior.
- Behavior for
session/loadon a deleted session is implementation-defined. - Behavior for deleting an active session is implementation-defined.