Subagent Configuration Lost After v1.0.62 Upgrade

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
When it updated to v1.0.62 then all my subagents cannot be seen in the agents list, I tried to create new subagent but it won't show. Also all slash commands are gone as well. I have to revert back to 61. That took me time to troubleshoot it.

Environment Info

  • Platform: win32
  • Terminal: windows-terminal
  • Version: 1.0.61
  • Feedback ID: 585308f4-391e-4d57-9856-dbef0f0173eb

Errors

[]

View original on GitHub ↗

5 Comments

JustMaier · 1 year ago

I believe this is affecting other customizations like Commands as well. Downgrading and disabling auto updates fixed the issue for me for a single run before Claude proceeds to update anyway...

npm un -g @anthropic-ai/claude-code   
npm i -g @anthropic-ai/claude-code@1.0.61
claude config set -g autoUpdates disabled
blackdiamond6390 · 1 year ago
claude config set -g autoUpdates disabled

thanks <3

heyagent · 1 year ago

@JustMaier for auto updates, the correct value should be false, but when you are setting it from the CLI, it passes the value as a string instead of a boolean. So until someone finds the true location of the configuration file where we can change manually we are toast.

Everyone can code nowadays. It doesn't mean that everyone should..... Amateur hour from Anthropic.

==================================

<img width="904" height="489" alt="Image" src="https://github.com/user-attachments/assets/fe32153d-e15d-4f6f-9f39-2082cb553967" />

Apparently you can disable auto updates from the actual tool.

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.