Agent Creation Fails: Saved Agents Not Detected in CLI Listing

Status Fixed / completed
Maintainer reply ✓ Yes — sid374
Activity 9 comments · opened Jul 29, 2025 · closed Jul 29, 2025
💡 Likely answer: A maintainer (sid374, contributor) responded on this thread — see the highlighted reply below.

Bug Description
When I create an agent, the file is created and saved however if I use /agents no agent is found. I have uninstalled multiple times, deleted all cluade temp and cache files, so luck. It doesn't matter if I choose project or personal

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 1.0.62
  • Feedback ID: e2cb76dd-7e16-43bb-a763-c100c7eeee78

Errors

[{"error":"Error: Command failed: tasklist | findstr /I \"Code.exe Cursor.exe Windsurf.exe idea64.exe pycharm64.exe webstorm64.exe phpstorm64.exe rubymine64.exe clion64.exe goland64.exe rider64.exe datagrip64.exe appcode.exe dataspell64.exe aqua64.exe gateway64.exe fleet.exe studio64.exe\"\nFINDSTR: Cannot open Code.exe Cursor.exe Windsurf.exe idea64.exe pycharm64.exe webstorm64.exe phpstorm64.exe rubymine64.exe clion64.exe goland64.exe rider64.exe datagrip64.exe appcode.exe dataspell64.exe aqua64.exe gateway64.exe fleet.exe studio64.exe\r\n\n    at genericNodeError (node:internal/errors:983:15)\n    at wrappedFn (node:internal/errors:537:14)\n    at checkExecSyncError (node:child_process:883:11)\n    at execSync (node:child_process:955:15)\n    at i7 (file:///C:/Users/justi/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:865:5108)\n    at Tt (file:///C:/Users/justi/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1346:1937)\n    at file:///C:/Users/justi/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1896:7279\n    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n    at async file:///C:/Users/justi/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1897:1485\n    at async Promise.all (index 12)","timestamp":"2025-07-29T15:02:51.012Z"},{"error":"Error: spawn /c/Users/justi/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:90:21)","timestamp":"2025-07-29T15:02:51.024Z"},{"error":"Error: spawn /c/Users/justi/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:90:21)","timestamp":"2025-07-29T15:03:44.991Z"}]

View original on GitHub ↗

9 Comments

0MarkB · 1 year ago

I have the same exact issue! Same thing with custom commands! also on windows and same vers
I tried everything as well.

Aaryan6 · 1 year ago

I got the same issue. One more problem I'm facing is that with the '@' command file autocomplete is not working.

sid374 contributor · 1 year ago

Thanks for the report, we're looking into it

0MarkB · 1 year ago
Thanks for the report, we're looking into it

going back to .61 fixes it. but even with auto updates off it still updates to 62 if you open a new claude session.

ant-kurt collaborator · 1 year ago

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.

0MarkB · 1 year ago
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.

did you also fix the auto update issue? setting auto update to false did not actually stop it from auto updating unless you manually create a settings.json in the .claude folder
not even the cli command for disabling or using /config to turn it off worked. only the settings.json

Thank you!

andaldanar · 1 year ago

New update 1.0.63 fixed it for me! (Windows)

ant-kurt collaborator · 1 year ago

@0MarkB would you mind opening a new issue for the auto-updater problem? We didn't make any changes on the auto-updater as part of this change, but definitely want to address that too.

Thanks!

github-actions[bot] · 1 year ago

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.