Skip to content

[docs] agent: record why a mid-turn message cannot be sent, and the queue design - #382

Draft
wtz2333 wants to merge 1 commit into
ThinkFlowLab:mainfrom
wtz2333:docs/midturn-message
Draft

wtz2333 wants to merge 1 commit into
ThinkFlowLab:mainfrom
wtz2333:docs/midturn-message

Conversation

@wtz2333

@wtz2333 wtz2333 commented Nov 17, 2026 •

Copy link
Copy Markdown

Summary

  • Add 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.
  • Register the page in the docs/README.md index.

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 #379

  • Refs #379 is included

Labels

  • Not applied: wtz2333 cannot add labels to this repository (GitHub refuses AddLabelsToLabelable). Suggested: type:docs, area:agent, needs-design.

Test plan

  • Local: no code changed. Checked that the Markdown renders, that the index row points at an existing file, and that the one relative link (../architecture/agent-runtime.md) resolves from the page.
  • Left to CI: the docs-only path of Release checks.

Evidence that it works

  • Media attached, or N/A because: docs only.

Provider verification

  • Real-provider calls are described honestly, or none were made: none.

Bilingual UI

  • Both locales are updated, or no user-facing copy changed: no user-facing copy changed.

@github-actions github-actions Bot added area:agent Agent runtime, assistant chat and tools type:docs Documentation only labels Nov 17, 2026
@github-actions
github-actions Bot requested review from FayeSpica and wuzhf9 November 17, 2026 03:13
@github-actions github-actions Bot added the area:docs Documentation / 文档 label Nov 17, 2026
@wtz2333
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
wtz2333 force-pushed the docs/midturn-message branch from 44c19bf to a2e95c1 Compare November 17, 2026 11:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:agent Agent runtime, assistant chat and tools area:docs Documentation / 文档 type:docs Documentation only

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant