[BUG] messages queued instead of sent even if claude is not busy

[marcospgp]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

queued messages sometimes won't be sent and will just sit in the queue, requiring a restart of claude code

When this happens, any message sent becomes queued and is not actually sent through.

What Should Happen?

queued messages should always be sent whenever Claude has finished the previous task.

Error Messages/Logs

Steps to Reproduce

It happens randomly so it's hard to reproduce

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.0.34 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

VS Code integrated terminal

Additional Information

No response

[arthurwolf]

I have this too, on ubuntu, latest version (2.0.37), it's very annoying, it now happens nearly every time...

I have a hook for the end of tasks that's supposed to check of typescript errors, could it be what is preventing the system from executing the queued/added prompt? But I just tried in a project that has zero typescript files and it still hangs forever, also I see no evidence the typescript error checking hook is doing any work, it just looks like nothing is happening but for some reason it's putting the prompt into the queue and never executing it, instead of just executing it right away.
Clicking escape twice or more and trying past prompts etc, doesn't fix the situation.

[github-actions]

This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.

[arthurwolf]

I'm not seeing this happen anymore with the most recent version(s).
I think this could be closed.

[github-actions]

This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.