session-workflow

# Session Workflow Separate gateway bookkeeping from native provider continuity. `session_create`, `session_list`, `session_set_active`, and `session_get` manage gateway metadata; they do not create or prove a provider-native conversation. Never pass a gateway-generated ID to a provider as though it were a native handle. For a review session, dispatch requests through the local stdio gateway MCP surface. A session does not authorize a direct provider CLI, connector/shadow gateway, or shell fallback. ## Discover before resuming Before using a provider-specific session field, query: ```text provider_tool_capabilities({cli:"claude"}) provider_tool_capabilities({cli:"codex"}) provider_tool_capabilities({cli:"gemini"}) provider_tool_capabilities({cli:"grok"}) provider_tool_capabilities({cli:"mistral"}) provider_tool_capabilities({cli:"devin"}) provider_tool_capabilities({cli:"cursor"}) ``` Use a native `sessionId` only when it came from that provider or was supplied by the caller as a verified native handle. A fresh gateway session often uses a `gw-*` bookkeeping ID. It is not resumable for Codex, Grok, Mistral, Devin, or Cursor, and must never be replayed to Gemini either. ## Native continuity matrix | Provider | Native resume | Important boundary ...