MCP Detached Chat Task Lifecycle

MCP Detached Chat Task Lifecycle A lifecycle diagram generated by Archify. 01 / Fresh ask 02 / Interruptions + recovery 03 / Terminal retention Submitted · resolved semantic inputs · Fresh ask · chat_start 01 Submitted resolved semantic inputs chat_start Claim Key · atomic map lookup · Fresh ask · SHA-256 02 Claim Key atomic map lookup SHA-256 Queued · await concurrency slot · Fresh ask · FIFO 03 Queued await concurrency slot FIFO Generating · server-owned asyncio task · Fresh ask · detached 04 Generating server-owned asyncio task detached Result Cached · pollable by task id · Fresh ask · 30 min TTL 05 Result Cached pollable by task id 30 min TTL Cancelled · queued, active, or shutdown · Terminal retention · pollable Cancelled queued, active, or shutdown pollable Error Cached · projected at read time · Terminal retention · pollable Error Cached projected at read time pollable Expired / Unknown · entry dropped · Terminal retention · chat_start to ask again Expired / Unknown entry dropped chat_start to ask again Legend start active state waiting decision terminal success failure / exit neutral

Detached Completion

  • • ChatTaskRegistry.start detaches work behind the gate

Bounded Admission

  • • Semantic duplicates attach; only unfinished saturation rejects

Truthful Observation

  • • chat_status exposes state until wall-clock TTL expiry