Sub-Agents Not Detected: Missing Agents in CLI List Despite Directory Creation
Resolved 💬 56 comments Opened Jul 28, 2025 by Lordymine Closed Jul 29, 2025
💡 Likely answer: A maintainer (ant-kurt, collaborator)
responded on this thread — see the highlighted reply below.
Bug Description
claude code sub agents are not working, when created they simply do not appear in the agents list, they are created in the /.claude/agents directory, but it is not possible to use them in the CLI and they do not even appear in the list, claude code version 1.0.62
Environment Info
- Platform: win32
- Terminal: vscode
- Version: 1.0.62
- Feedback ID: ef107845-f4df-4204-bc0f-5e215983b266
Errors
[{"error":"Error: spawn /c/Users/Rafael Oliveira/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/vendor/ripgrep/x64-win32/rg.exe ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","timestamp":"2025-07-28T23:51:42.912Z"},{"error":"Error: spawn /c/Users/Rafael Oliveira/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/vendor/ripgrep/x64-win32/rg.exe ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","timestamp":"2025-07-28T23:51:42.921Z"},{"error":"Error: 1: 1 Extension 'c:\\users\\rafael' not found.\nMake sure you use the full extension ID, including the publisher, e.g.: anysphere.csharp\nFailed Installing Extensions: c:\\users\\rafael\n(node:15624) [DEP0168] DeprecationWarning: Uncaught N-API callback exception detected, please run node with option --force-node-api-uncaught-exceptions-policy=true to handle those exceptions properly.\n(Use `Cursor --trace-deprecation ...` to show where the warning was created)\n\n at KT6 (file:///C:/Users/Rafael%20Oliveira/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1345:4765)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async VT6 (file:///C:/Users/Rafael%20Oliveira/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1345:2187)","timestamp":"2025-07-28T23:51:44.659Z"},{"error":"Error: spawn /c/Users/Rafael Oliveira/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/vendor/ripgrep/x64-win32/rg.exe ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","timestamp":"2025-07-28T23:51:53.259Z"},{"error":"Error: spawn /c/Users/Rafael Oliveira/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/vendor/ripgrep/x64-win32/rg.exe ENOENT\n at ChildProcess._handle.onexit (node:internal/child_process:285:19)\n at onErrorNT (node:internal/child_process:483:16)\n at process.processTicksAndRejections (node:internal/process/task_queues:82:21)","timestamp":"2025-07-28T23:52:57.531Z"}]
56 Comments
+1
@hacir My agents and commands from my super claude framework haven't appeared since I updated to version 1.0.62, was yours like that too?
Yes, that's correct. Same issue and began immediately after updating; no other changes.
@hacir For now, use this command to revert to the previous version and disable auto-update so you don't get downgraded to version 1.0.62 again. I downgraded the version and it worked:
npm install @anthropic-ai/claude-code@1.0.61 -g
+1, also commands are missing too
@erencelik For now, use this command to revert to the previous version and disable auto-update so you don't get downgraded to version 1.0.62 again. I downgraded the version and it worked:
npm install @anthropic-ai/claude-code@1.0.61 -g
#4579
I have the same problem, except I'm using macOS and I'm trying to upgrade now
https://github.com/anthropics/claude-code/pull/3938
+1
+1
+1
this is what happened to me. rolling back to 1.0.61 fixed everything!
also here. not working either for local / user config
Agree. Roll back fixed it.
Rollback works, but how to disable auto-update
not rolling back now. i guess ill do a full removal
+!
To Disable Auto Update
/config`` and press Enter [toppicture]false`` [bottom picture]<img width="1092" height="450" alt="Image" src="https://github.com/user-attachments/assets/537ff8d9-c394-48c3-b874-20780b13a919" />
<img width="1086" height="498" alt="Image" src="https://github.com/user-attachments/assets/cb0a0b42-8445-41f8-8757-3aaa4e3fcf9c" />
Thanks
+1
+1 - the latest update has prevented Agents from showing on my Windows machine. Both Personal and Project level are not working anymore.
+1 It also prevents you from using @{path/to/file}, it doesn't detect any file at all and it only detects the available agents, which is "generic-agent" not any custom one, even when creating a new one.
Sub agents where working yesterday but they are not showing from the Claude Code CLI today, I guess for now disabling auto updates and is rolling back to previous version is best option for now
This was super helpful, thanks!
+1 on this one as well.
same here ;(
Issues with custom agents, file search, and custom slash commands on Windows should be resolved for CMD and Powershell in 1.0.63, which released today but is not yet tagged as
latest.Downgrading to 1.0.61 will also mitigate.
yep same here using ubuntu on wsl 2 in cursor terminal - tried disabling auto update and rolling back to the recommended vesion and /agents still doesn't work
Seeing this issue as well on Mac
Please update to
1.0.64to get the fixHaving this issue on 1.0.65, even after reverting to previous versions the issue hasn't been fixed.
@rodrijuarez can you please describe your issue in more detail?
you just need to go back to version 1.0.61 which is working on it, and disable the auto updates function while they fix it
@sid374 I get this even after creating an agent, I have tried creating both project and local agents and none of them show up on the list even after them being created. Tried re-installing, downgrading (currently on 1.0.65) and clearing up configs but none of them worked
<img width="705" height="213" alt="Image" src="https://github.com/user-attachments/assets/c086e35f-a463-47d8-90ca-714bd4b5033d" />
@sid374 @Lordymine I have also tried rolling back to a previous version (1.0.61) and it still does not work for me
<img width="279" height="245" alt="Image" src="https://github.com/user-attachments/assets/eb7dd55b-b476-4d27-9a8f-980b9c3187ff" />
@rodrijuarez do you see your agent files created here in
.claude/agentsor~/.claude/agents?@sid374 yes, they are there
<img width="727" height="123" alt="Image" src="https://github.com/user-attachments/assets/e10bc74d-46aa-4630-af2e-13f61e7ed804" />
An example of an agent generated (I removed some of the text in the middle to paste it here so the message isn't too long)
Have the same issue. v1.0.67 on MacOS.
agents Directory created. agent_name.md created.
'No agents found'
Still happening in the latest version from native windows user @ant-kurt
<img width="1184" height="1005" alt="Image" src="https://github.com/user-attachments/assets/05bd5691-31c3-4f38-89b5-2ac07b394956" />
<img width="500" height="722" alt="Image" src="https://github.com/user-attachments/assets/9af7e099-e4f7-4e56-8a0a-2468c73a5d2d" />
<img width="307" height="100" alt="Image" src="https://github.com/user-attachments/assets/e0173151-7992-4c47-a0b4-f02a403f1903" />
On
Claude Code v1.0.68for Windows and experiencing the same behavior. I can go through the adding agents process and once finished it still shows the screen that no agents found. However I do see the .md file created in the correct path for the project.ACK - we're aware of issues with the native Windows installer specifically, and are working to resolve it. If you're seeing this on the
npminstallation, let us know.@ant-kurt I'm on Mac OS and I'm finding this issue using npm install
/Users/rodrigojuarez/.nvm/versions/node/v18.17.0/bin/claudeHaving issue too with 1.0.70 (Claude Code) on windows and linux via npm
yeah the problem is back, it's case sensitive now. I can't find anything unless i type the filename exactly as it's cased.
the new version of claude code seems to need a header section in the subagent files:
example subagent file:
``
gui-developer.md``then the header needs to be
that worked for me
May I know any official guide on systematically resolving it? @ant-kurt , I believe this is a core feature for a lot of claude code users
I'm still having this issue on Mac OS:
And I would like to fix this as I'm paying for Claude Code max and this feature would be very useful for me. Thanks!
Why is this issue closed if so many people are still facing it? I am facing it on Mac os with v1.0.68. I am using claude code using API key.
See https://github.com/anthropics/claude-code/issues/5185 - there are some workarounds in the comments.
This issue (4623) was related to a Windows-specific issue, which has been resolved.
Ok sorry for spamming everyone on this thread, running
brew install ripgrepworked for me. mentioned here -> https://github.com/anthropics/claude-code/issues/5185. Thanks everyone.Following up on the
ripgrepsolutions posted to #5185 and #4741 ...Even after updating
ripgrep, I ran into the behavior happening again. Here's how I fixed it:TL;DR:
USE_BUILTIN_RIPGREPfromsettings.jsonandsettings.local.jsonThe Longer Explanation:
USE_BUILTIN_RIPGREP: "1"- This worked initially but then stopped working in later sessions.USE_BUILTIN_RIPGREPenv var fromsettings.jsonandsettings.local.json, which fixed some issues (e.g., Claude Code no longer needed to pipe ripgrep output when calling it via the Bash tool), but agents were still not detected.This not only caused those specific agents to fail, but silently broke ALL agent detection (including slash commands). No errors appeared even with
--debugflag.Solution:
Ensure all YAML frontmatter values are on a single line:
After converting all multi-line descriptions to single-line format, everything works perfectly!
It could also be some other YAML parsing issue. Try moving your agent definitions out (and slash command definitions, too, for good measure) and just put one, simple, agent back in. If that works, then add your other agents back in one by one until you find the one that breaks it.
Hope this helps! :)
@vmadman et al, here is the full details of the ripgrep issue and a solution: https://github.com/anthropics/claude-code/issues/4741#issuecomment-3177976916
I managed to resolve this through claude. Remove all custom agents from .claude
Create a new agent through the CLI interface. You should now have a claude generated .md file.
Copy back your custom agents. Tell claude to look at the auto generated one and compare and resolve.
Another case that fixed this for me. I had
had to change to
1.0.83 works now
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.