Repository navigation
v1.0.12 — Preserve Ask decision cards
Persistent Ask decision records
- Keeps completed
ask_user_questioncards and their selected answers visible after an agent run ends. - Excludes Ask from turn-summary aggregation while read-only tools in the same run continue to collapse normally.
- Applies the same behavior to live runs and restored sessions, including when mutating-tool collapse is enabled.
- Leaves the existing Ask card presentation (
Questions,Output, elapsed time, and word count) unchanged.
Root cause
The completed-turn summarizer treated every unknown extension tool as collapsible and formatted it with the generic fallback used <count> <toolName>. Ask is now classified as a durable user-decision record rather than changing that generic fallback for unrelated custom tools.
Verification
npm run checkpassed: 71 tests, typecheck, dependency-cruiser, build, and package smoke.- Windows PTY E2E reproduced
➔ used 1 ask_user_questionon npm v1.0.11 before the fix. - Windows PTY E2E through the built v1.0.12 local package completed a real Ask interaction and verified that the full answer card remained visible after
DONE. - Mixed-turn and restored-session regression tests confirm ordinary read-only summaries are unchanged.
- Premium strict UI audit completed with 0 findings.
npm pack --dry-runcontained the expected 7 published files.