Skip to content

docs(rfd): draft turn_complete signal for session/update sync#644

Open
stablegenius49 wants to merge 1 commit intoagentclientprotocol:mainfrom
stablegenius49:docs/rfd-turn-complete-signal-554
Open

docs(rfd): draft turn_complete signal for session/update sync#644
stablegenius49 wants to merge 1 commit intoagentclientprotocol:mainfrom
stablegenius49:docs/rfd-turn-complete-signal-554

Conversation

@stablegenius49
Copy link

@stablegenius49 stablegenius49 commented Mar 4, 2026

Summary

Draft RFD to address #554 by proposing a protocol-level turn_complete signal in session/update.

This gives clients a deterministic end-of-turn barrier for streamed updates and removes the need for sleep-based heuristics after session/prompt resolves.

What this PR changes

  • Adds a new Draft RFD: docs/rfds/turn-complete-signal.mdx
  • Adds the RFD to docs navigation (docs/docs.json under RFDs > Draft)

Proposal highlights

  • New update variant: sessionUpdate: "turn_complete"
  • Emitted once per prompt turn, after all other updates for that turn
  • Includes turn correlation (promptRequestId) and optional stopReason
  • Explicit capability advertisement via sessionCapabilities.turnComplete

Why RFD-first

This appears to touch ordering semantics and SDK behavior across multiple implementations. Starting with an RFD should help converge on semantics before unstable schema/runtime changes.

Refs #554

Add a Draft RFD proposing a session/update turn_complete signal to provide a deterministic end-of-turn barrier for clients consuming streaming updates (issue agentclientprotocol#554). Also add the RFD to docs navigation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant