claude-code - 💡(How to fix) Fix [Regression bug] AskUserQuestion tool_use event not written to session.jsonl until user responds

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
RAW_BUFFERClick to expand / collapse

Bug Description there is a regression I notice with your transcript event writes. the current version does not write the AskUserQuestion event to the session .jsonl on disk until after the user provides an answer. older versions (2.1.119 verified) do as expected which is write the AskUserQuestion event to disk immediately upon prompting.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 2.1.139
  • Feedback ID: 0b70a2ea-4db7-46a6-9927-d99e7736ca14

The prior behavior is needed so external tooling can notify the user that interaction is required to continue.

repro steps:

  • new session
  • user prompt: qna prompt test: ask me a simple question
  • wait for the question to be shown on screen
  • inspect the session .jsonl, AskUserQuestion tool_use event is missing
  • back in the session, respond to the question
  • check the .jsonl and the AskUserQuestion tool_use event will now be written, using the original ask timestamp (not the timestamp in which it's finally written to disk)

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING