TUI default change plus clarify options formatting fix
Cluster 47285 · agent. Data as of
1 open item. Fix merged in #49089 on 19 Jun 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 0 issues already closed.
- Fix event
- A fix was merged to main in PR #49089. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 0 PRs.
Next step: read #49089, then check whether your report is the one still open.
Read #49089Pick up a Lab taskOne item introduces a native OpenTUI terminal UI as the new default (with Ink as fallback). The remaining three items, likely duplicates or related iterations, address a fix to keep clarify tool options in the choices array rather than enumerating them in question text.
Open issues1
- Issue#47285clarify_tool: put options in choices[] only, never enumerate in question text
Open PRs0
Fixes on record
-
#49089 fix(clarify): put options in choices[] only, never enumerate in question text
files:
tools/clarify_tool.pyShow the diff
-
tools/clarify_tool.py@@ -131,6 +131,12 @@ def check_clarify_requirements() -> bool: "or types their own answer via a 5th 'Other' option.\n" "2. **Open-ended** — omit choices entirely. The user types a free-form " "response.\n\n" + "CRITICAL: when you are offering options, put each option ONLY in the " + "`choices` array — NEVER enumerate the options inside the `question` " + "text. The UI renders `choices` as selectable rows; options written " + "into the question string render as dead prose the user can't pick. " + "Right: question='Which deployment target?', choices=['staging', " + "'prod']. Wrong: question='Which target? 1) staging 2) prod', choices=[].\n\n" "Use this tool when:\n" "- The task is ambiguous and you need the user to choose an approach\n" "- You want post-task feedback ('How did that work out?')\n" @@ -145,16 +151,22 @@ def check_clarify_requirements() -> bool: "properties": { "question": { "type": "string", - "description": "The question to present to the user.", + "description": ( + "The question itself, and ONLY the question (e.g. 'Which " + "deployment target?'). Do NOT embed the answer options here " + "— pass them as separate elements in `choices`." + ), }, "choices": { "type": "array", "items": {"type": "string"}, "maxItems": MAX_CHOICES, "description": ( - "Up to 4 answer choices. Omit this parameter entirely to " - "ask an open-ended question. When provided, the UI " - "automatically appends an 'Other (type your answer)' option." + "REQUIRED whenever you are presenting selectable options: " + "each distinct option is its own array element (up to 4). " + "The UI renders these as pickable rows and auto-appends an " + "'Other (type your answer)' option. Omit this parameter " + "entirely ONLY for a genuinely open-ended free-text question." ), }, },
-
2 PRs closed without merging
From the close comments: merged via another change 1 · other 1
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Merged PRs
- #49089
- Closed issues
- 0
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 19 Jun 2026