{"slug": "your-turn-is-a-session-handoff-not-a-completion-claim", "title": "Your Turn Is a Session Handoff, Not a Completion Claim", "summary": "Agent Island v1.7.1 introduces a precise 'your-turn' state model for coding agents like Claude Code and Codex, distinguishing between mere inactivity and a genuine handoff to the developer. The system uses semantic session events—such as questions, approval prompts, or completion events—rather than stale signals like CPU usage or file modification times, to determine when the developer's input is needed.", "body_md": "When a coding agent stops producing output, the next step is not automatically yours. It may be waiting on a tool, calculating, stalled, or actually finished. A useful **your-turn** state needs stronger evidence than silence.\n\nThe definition I use is narrow: your-turn means a specific Claude Code or Codex session has produced evidence that the next useful action belongs to the developer.\n\n“Stopped” describes activity. “Your turn” describes ownership of the next step.\n\nA semantic session event can support that handoff: an assistant message that asks a question, a structured approval prompt, or a completion event that explicitly returns control. File modification time, low CPU, and an unchanged process list are freshness clues, not proof of a handoff.\n\nThis distinction prevents two common errors:\n\nWhen evidence is stale or ambiguous, the honest state is uncertainty.\n\nMulti-session workflows make generic alerts almost useless. If three Codex sessions are open, “Codex needs you” still leaves the developer searching.\n\nThe handoff record should preserve the provider, project or thread identity, semantic event, and event time. Aggregation can rank a real your-turn state above passive working or stale state, but it must not erase the origin of the event.\n\nIf two sessions need attention, the UI should show both or apply a deterministic priority rule. A single generic badge is not enough.\n\nYour-turn does **not** mean:\n\nThose are separate verification and authorization questions. A status label should not smuggle them into a convenient notification.\n\nNotification policy is part of the state model. When the exact target session is already frontmost, an extra sound may add no value. The visual state can remain while the sound is suppressed. If the developer switches away, the pending handoff must remain eligible for an alert.\n\nThe monitor must also deduplicate events. Re-reading the same local record after an app restart should not produce a second alert. Stable event identity, or a documented replay key, keeps one handoff equal to one notification.\n\nAgent Island v1.7.1 applies this model to Claude Code and Codex status on macOS and Windows. It reports the handoff; it does not silently operate the coding agent.\n\nThe [canonical your-turn guide](https://agent-island.dev/your-turn-state/?utm_source=devto&utm_medium=owned_social&utm_campaign=your_turn_state_20260727) contains the full boundary and verification sequence.", "url": "https://wpnews.pro/news/your-turn-is-a-session-handoff-not-a-completion-claim", "canonical_source": "https://dev.to/agentis/your-turn-is-a-session-handoff-not-a-completion-claim-1ech", "published_at": "2026-07-27 01:38:46+00:00", "updated_at": "2026-07-27 02:29:33.990318+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-tools"], "entities": ["Agent Island", "Claude Code", "Codex"], "alternates": {"html": "https://wpnews.pro/news/your-turn-is-a-session-handoff-not-a-completion-claim", "markdown": "https://wpnews.pro/news/your-turn-is-a-session-handoff-not-a-completion-claim.md", "text": "https://wpnews.pro/news/your-turn-is-a-session-handoff-not-a-completion-claim.txt", "jsonld": "https://wpnews.pro/news/your-turn-is-a-session-handoff-not-a-completion-claim.jsonld"}}