Context
As part of the Shared Deployment MVP (#10721), agents need a mechanism to resume work after a disconnect. The substrate primitive RequestContextService was shipped in #10692, but the operator/agent surface to utilize it for resuming a specific session is missing.
The Problem
When an agent reconnects after a disconnect (or during a planned handoff), it is currently ambiguous whether they resume an existing session or start fresh. The lack of a clear resume tool surface prevents continuous workflows across connection boundaries.
The Architectural Reality
The RequestContextService maintains client-scoped session contracts. This task involves a design-and-implement decision on how to expose resumption. It might be a new MCP tool (e.g., resume_session) or a parameter integrated into the existing connection/startup payload.
The Fix
Design and implement the session-handoff surface. Coordinate cleanly with the RequestContextService to allow an agent to specify an existing session ID and resume operations without data corruption or redundant summarization.
Contract Ledger Matrix
| Target Surface |
Source of Authority |
Proposed Behavior |
Fallback |
Docs |
Evidence |
| Session Resumption |
RequestContextService |
Agent can successfully resume an existing session_id and continue appending memories. |
Reject invalid session IDs and default to a new session with explicit warning. |
Add to learn/agentos/SharedDeployment.md |
L3 (Integration test showing contiguous memory sequence across disconnects) |
Acceptance Criteria
Out of Scope
- Multi-agent concurrent editing of a single session (sessions remain 1:1 with active client connections).
Avoided Traps
- Rejected: Re-architecting
RequestContextService. The substrate shipped in #10692 is solid; this task is strictly about providing the surface to utilize it, avoiding unnecessary foundational churn.
Related
Origin Session ID: 79042442-bebc-431d-8968-8a2e7d7a1151
Retrieval Hint: query_raw_memories(query="Resume tool session-handoff RequestContextService")
Context
As part of the Shared Deployment MVP (#10721), agents need a mechanism to resume work after a disconnect. The substrate primitive
RequestContextServicewas shipped in #10692, but the operator/agent surface to utilize it for resuming a specific session is missing.The Problem
When an agent reconnects after a disconnect (or during a planned handoff), it is currently ambiguous whether they resume an existing session or start fresh. The lack of a clear resume tool surface prevents continuous workflows across connection boundaries.
The Architectural Reality
The
RequestContextServicemaintains client-scoped session contracts. This task involves a design-and-implement decision on how to expose resumption. It might be a new MCP tool (e.g.,resume_session) or a parameter integrated into the existing connection/startup payload.The Fix
Design and implement the session-handoff surface. Coordinate cleanly with the
RequestContextServiceto allow an agent to specify an existing session ID and resume operations without data corruption or redundant summarization.Contract Ledger Matrix
session_idand continue appending memories.learn/agentos/SharedDeployment.mdAcceptance Criteria
RequestContextService.Out of Scope
Avoided Traps
RequestContextService. The substrate shipped in #10692 is solid; this task is strictly about providing the surface to utilize it, avoiding unnecessary foundational churn.Related
Origin Session ID: 79042442-bebc-431d-8968-8a2e7d7a1151 Retrieval Hint:
query_raw_memories(query="Resume tool session-handoff RequestContextService")