Subagent Discovery Failure: Agents Not Detected in Configured Directory

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

Bug Description
I cant see and use my sub agents but I have created them and they are as they should properly in the agents folder

Environment Info

  • Platform: win32
  • Terminal: cursor
  • Version: 1.0.62
  • Feedback ID:

View original on GitHub ↗

5 Comments

pguppy · 1 year ago

Yeah same issue for me, looks like they just did a release a couple of hours ago. just roll back to the previous 1.0.61 veresion from 1.0.62 which seems to have introduced a bug some how. Can confirm that resolves the issue for me.
npm install -g @anthropic-ai/claude-code@1.0.61

kroath · 1 year ago
Yeah same issue for me, looks like they just did a release a couple of hours ago. just roll back to the previous 1.0.61 veresion from 1.0.62 which seems to have introduced a bug some how. Can confirm that resolves the issue for me. npm install -g @anthropic-ai/claude-code@1.0.61

Same, can also confirm that 1.0.62 causes the directory issues and reverting back to 1.0.61 on Windows with auto updates turned off fixes it.

tarnan3751 · 1 year ago

+1, issue started in the latest update, reverting back to CC version 1.0.61 resolves any issues with subagent discovery

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.

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.