Record the input contract that non-TUI mode now guarantees:
- --message / --message-file are one-shot; there is no follow-up answer path
in that mode, so a question-ending instruction cannot be answered. Multi-turn
runs use interactive mode instead.
- In interactive mode input comes from the TUI box (tui: true), from stdin with
a re-prompt per turn (tui: false), or from a queue push ({"text": ...} and
{"confirmed": ...}) used by the WebSocket/ACP server and the AgentService
wake path.
- Both the TUI and non-TUI input paths consume the same per-coder queue, so a
headless or server-driven session can answer prompts with no terminal.
Documentation only; no code change. Planned to merge after the non-TUI
queued-input fix so the queue contract it describes is accurate.
What
Documents the input contract for non-TUI sessions:
the model act, then exits. There is no follow-up prompt, so a question-ending
instruction has nowhere to collect an answer. --yes covers fully
non-interactive runs.
turn (tui: false), or a queue push ({"text": ...}, {"confirmed": ...})
from the WebSocket/ACP server and the AgentService wake path.
server-driven session can answer prompts with no terminal.
Files: cecli/website/docs/config/tui.md, cecli/website/docs/scripting.md.
Sequencing
Depends on #697 (the non-TUI queued-input fix). Merge that first so the
queue contract described here is accurate. Docs only; no code change.