Version: 0.6.0 (latest 0.6.0)
Command: /flow:continue (question-protocol.md, "Presenting a question")
What happened:
Every open question costs two turns: the agent ends a turn with a
briefing plus a handoff line ("Reply anything and I'll open the
options"), the user types a throwaway reply, and only then the
AskUserQuestion dialog opens. With several queued decisions this
doubles the round trips and the throwaway replies feel like busywork.
What I expected:
Context first, then the dialog, in ONE turn: the briefing renders and
the AskUserQuestion opens right after it without the user having to
say "open".
Why the protocol is two-turn today (as I understand it):
Text emitted in the same message as a tool call is not reliably
rendered by the host, so a briefing "above the dialog" was often
invisible and the user got naked dialogs with no context. The
two-turn rule fixed that, but at the cost of an extra reply per
question.
^ assumed — correct me
Suggestion:
Keep the context guarantee but drop the extra turn, e.g. by carrying
the briefing INSIDE the dialog: put the full context (mechanism, why
it matters, trade-off table) into AskUserQuestion's question field
and each option's consequence into its description, and/or use the
per-option preview field for the comparison table. Then the
protocol can be one turn: recap/briefing text is optional, the dialog
is self-contained either way.
Repro:
Any /flow:continue with 2+ open questions; observe the
"reply anything" handoff before each dialog.
Version: 0.6.0 (latest 0.6.0)
Command: /flow:continue (question-protocol.md, "Presenting a question")
What happened:
Every open question costs two turns: the agent ends a turn with a
briefing plus a handoff line ("Reply anything and I'll open the
options"), the user types a throwaway reply, and only then the
AskUserQuestion dialog opens. With several queued decisions this
doubles the round trips and the throwaway replies feel like busywork.
What I expected:
Context first, then the dialog, in ONE turn: the briefing renders and
the AskUserQuestion opens right after it without the user having to
say "open".
Why the protocol is two-turn today (as I understand it):
Text emitted in the same message as a tool call is not reliably
rendered by the host, so a briefing "above the dialog" was often
invisible and the user got naked dialogs with no context. The
two-turn rule fixed that, but at the cost of an extra reply per
question.
^ assumed — correct me
Suggestion:
Keep the context guarantee but drop the extra turn, e.g. by carrying
the briefing INSIDE the dialog: put the full context (mechanism, why
it matters, trade-off table) into AskUserQuestion's
questionfieldand each option's consequence into its
description, and/or use theper-option
previewfield for the comparison table. Then theprotocol can be one turn: recap/briefing text is optional, the dialog
is self-contained either way.
Repro:
Any /flow:continue with 2+ open questions; observe the
"reply anything" handoff before each dialog.