Repository navigation
Conversation
wtz2333
marked this pull request as draft
November 17, 2026 08:47
A supplementary message cannot be sent while a reply runs: the composer swaps send for stop, Enter is a silent no-op, and the API refuses a second turn with 409. Nothing in the chain is missing a button — there is no place for a second message at all. This page records the check that established that (with the probe output), the three delivery semantics weighed (queue and continue, steer inside the turn, interrupt and restart), and the queue design: a message is stored at once with `queued`, runs as its own turn after the active one, and the stream stays open across turns through `nextTurnId` so a viewer keeps receiving without reconnecting. It also says which trade-offs were taken and which are still open, including what P1 would need from each runtime. Behaviour semantics live in the agent runtime page; this is the record of the reasoning behind them.
wtz2333
force-pushed
the
docs/midturn-message
branch
from
November 17, 2026 11:50
44c19bf to
a2e95c1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/development/midturn-message.md: why a supplementary message could not be sent while a reply ran (measured, with the file and line behind each claim), the three delivery semantics weighed — queue and continue, steer inside the turn, interrupt and restart — and the queue design that follows.docs/README.mdindex.The page is written as a design record, not a status page: it says when it was recorded and which revision the check ran against, keeps its findings in the past tense, and leaves progress to issue #379. The behaviour that now exists is documented where semantics belong, in the agent runtime page's run lifecycle section (
docs/architecture/agent-runtime.md, changed by #381), so this page will not read as if nothing had been built and will not go stale when the pull requests merge.Linked issue
Refs #379Refs #379is includedLabels
wtz2333cannot add labels to this repository (GitHub refusesAddLabelsToLabelable). Suggested:type:docs,area:agent,needs-design.Test plan
../architecture/agent-runtime.md) resolves from the page.Evidence that it works
Provider verification
Bilingual UI