[Bug] Error: No Assistant Message Found
Bug Description
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: No assistant message found
at Nm (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3310:12886)
at async file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3310:21634
at async va0 (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3310:2011)
at async LJ (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3310:21490)
at async HBB (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3317:200)
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: No assistant message found
at Nm (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3310:12886)
at async file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3310:21634
at async va0 (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3310:2011)
at async LJ (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3310:21490)
at async HBB (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3317:200)
Environment Info
- Platform: win32
- Terminal: windows-terminal
- Version: 2.0.22
- Feedback ID:
Errors
[{"error":"Error: Request was aborted.\n at Jy.makeRequest (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:357:3850)\n at processTicksAndRejections (node:internal/process/task_queues:105:5)\n at runNextTicks (node:internal/process/task_queues:69:3)\n at process.processTimers (node:internal/timers:540:9)","timestamp":"2025-10-20T01:04:16.247Z"},{"error":"SyntaxError: Expected property name or '}' in JSON at position 1 (line 1 column 2)\n at JSON.parse (<anonymous>)\n at file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:62:719\n at Q (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:8:15093)\n at zn2 (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1057:20629)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)","timestamp":"2025-10-20T01:04:16.907Z"},{"error":"Error: Tool LS not found\n at $NB (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1555:12555)\n at d$ (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:73:19414)\n at ms (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:42814)\n at _9 (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:38355)\n at $d (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:38283)\n at e$ (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:38137)\n at xC (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:35216)\n at T6 (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:73:4841)\n at g5 (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:32461)\n at YJ (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:73:24919)","timestamp":"2025-10-20T01:04:26.107Z"},{"error":"Error: Tool LS not found\n at $NB (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1555:12555)\n at d$ (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:73:19414)\n at bx (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:3227)\n at ms (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:43595)\n at _9 (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:38355)\n at $d (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:38283)\n at e$ (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:38137)\n at xC (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:35216)\n at T6 (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:73:4841)\n at g5 (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:75:32461)","timestamp":"2025-10-20T01:04:26.126Z"},{"error":"Error: Tool LS not found\n at $NB (file:///G:/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1555:12555)\n at d$ (file:///G:/AppData/Roaming/npm/node_modules/@an
Note: Error logs were truncated.
Showing cached comments. Read the full discussion on GitHub ↗
28 Comments
Same here, on my Mac.
Same here, on my Mac
Same here, on my Mac.
me too.
windows 11
2.0.22
Same here on my back.
I find this issue with latest claude version
2.022. Rolled back to2.0.10and still seeing this one.I had to rollback to
1.0.128version.This appears to happen when referencing directories with the "@" sign. Removal of the directory reference prevents the error.
Environment: WSL Ubuntu 22.04 LTS
Claude Code: 2.0.22 (Claude Code)
Same here
No assistant message found - Claude Code v2.0.22 mac, native installation flow
Happens to me when i tag a folder with multiple files/folders inside of it
Mac
Node.js v20.18.0
Claude Code v2.0.22 Sonnet 4.5
using AWS bedrock
same here
It seems the bug was introduced in v2.0.22. I reverted to v2.0.21 and it works fine.
I reproduced this.
Yes, That's my problem, redproduced by claude 2.0.24
Just reproduced on 2.0.25 🤷
Just reproduced on 2.0.25, mine due to
.terraformfiles. I've denied tools with this in settings.json but that doesn't resolve the issue. Claude seems to think it's due to indexing access. Hope this helpsIf I remove the
@symbol, as was quoted/suggested in your comment, it seems to work just fine. So that seems to be the center of this issue. Specifically, this is when I use a claude code command that takes an@path/to/directoryor@path/to/file.mdMac Sequoia 15.7 (repro'd on v.2.0.22 through v2.0.25)
edit: 10/23
v2.0.26 fixed
@path/to/file.md, but still crashes when receiving a directory as@path/to/directoryCan repro in 2.0.25
I can also confirm that removing
@tags from the prompt solves the problem, but makes experience worse as CC now needs to find files from context, rather than references.+1
Usually after my first message in the session.
Seeing this too, specifically with slashes.
Looks like it will need the handling of this updating.
Removing references to another dir/file fix it for me.
Running into this, specifically the message in #10007.
Appears to be related to when you reference a folder (not a direct file) like
review @docs/reference/claude-code/instead of sayreview @docs/reference/claude-code/hooks.mdi've found. can reproduce on demand :(Is this issue happening in 2.0.26?
Yes. I updated from 2.0.25 to 2.0.26 hoping it had been fixed.
Interestingly after setting the following I haven't experienced the issue, but need to test more thoroughly.
'export USE_BUILTIN_RIPGREP=0'
When was the built in riprep added or last edited?
Two months ago https://www.linkedin.com/posts/john-pribesh-61892027_claude-code-team-is-always-shipping-%F0%9D%98%83%F0%9D%9F%AD-activity-7363565503748927488-kirh/ v1.0.84
Fix tool_use/tool_result id mismatch error when network is unstable
Fix Claude sometimes ignoring real-time steering when wrapping up a task
@-mention: Add ~/.claude/* files to suggestions for easier agent, output style, and slash command editing
Use built-in ripgrep by default; to opt out of this behavior, set USE_BUILTIN_RIPGREP=0
Thanks for the report. We should have this fixed in today's release
still getting the error when using @some_folder/ but using ./some_folder is working
This is fixed in 2.0.27
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.