[BUG] Agent View not enabled for Claude API users despite having required version (2.1.140)
Status Fixed / completed
Reported on v2.1.140
Maintainer reply ✓ Yes — bogini
Activity 5 comments · opened May 13, 2026 · closed May 13, 2026
💡 Likely answer: A maintainer (bogini, collaborator)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Description:
Attempting to use the new Agent View feature on Claude Code version 2.1.140.
- The
claude agentscommand outputs a list of agents (users, plugins, built-in) instead of the Agent View dashboard. - The
/bgcommand is unrecognized, suggesting the backgrounding feature is also unavailable. - My Claude Code version is 2.1.140 (displayed at bottom of terminal).
- I am a Claude API user (not a Claude Pro/Max/Team/Enterprise subscriber).
Steps to Reproduce:
- Ensure Claude Code is updated to version 2.1.140 or newer.
- In the terminal, run
claude agents. - Observe the output.
- Start a Claude Code session and type
/bg.
Expected behavior:
claude agentsshould open the new Agent View dashboard, allowing me to see and manage multiple Claude Code sessions./bgcommand should be recognized and send the current session/agent to the background.
Actual behavior:
claude agentsshows a static list of agents./bgis reported as an unknown command.
Environment:
- Claude Code Version: 2.1.140
- Authentication Method: API Key
- Account Type: Claude API User (not a Pro/Max/Team/Enterprise subscriber)
- Operating System: macOS/Linux/Windows (请根据你的实际情况填写)
- Terminal: (请根据你的实际情况填写,如 iTerm2, Terminal.app, Windows Terminal, etc.)
Screenshots / Logs:
> ➜ claude agents
9 active agents
User agents:
biz-vul-security-agent · inherit
Plugin agents:
plugin-dev:agent-creator · sonnet
plugin-dev:plugin-validator · inherit
plugin-dev:skill-reviewer · inherit
Built-in agents:
claude-code-guide · haiku
Explore · haiku
general-purpose · inherit
Plan · inherit
statusline-setup · sonnet
> ➜ claude -version
2.1.140 (Claude Code)
> /bg
Unknown command: /bg. Did you mean /bug?
What Should Happen?
- The
claude agentscommand outputs a list of agents (users, plugins, built-in) instead of the Agent View dashboard. - The
/bgcommand is unrecognized, suggesting the backgrounding feature is also unavailable. - My Claude Code version is 2.1.140 (displayed at bottom of terminal).
- I am a Claude API user (not a Claude Pro/Max/Team/Enterprise subscriber).
Error Messages/Logs
Steps to Reproduce
➜ claude agents
9 active agents
User agents:
biz-vul-security-agent · inherit
Plugin agents:
plugin-dev:agent-creator · sonnet
plugin-dev:plugin-validator · inherit
plugin-dev:skill-reviewer · inherit
Built-in agents:
claude-code-guide · haiku
Explore · haiku
general-purpose · inherit
Plan · inherit
statusline-setup · sonnet
➜ claude -version
2.1.140 (Claude Code)
/bg
Unknown command: /bg. Did you mean /bug?
Claude Model
None
Is this a regression?
No, this never worked
Last Working Version
_No response_
Claude Code Version
2.1.140
Platform
Other
Operating System
macOS
Terminal/Shell
Other
Additional Information
_No response_
5 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Thanks for reporting. This was a feature-flag delivery issue —
claude agentswas gated on a GrowthBook flag whose cache could be stale or unreachable depending on platform/network. We've removed the gate entirely;claude agentsnow opens the dashboard unconditionally (including on Bedrock/Vertex/Foundry).Ships in v2.1.141 (tomorrow).
@bogini is it possible to enable the feature flag manually so that I can use the feature? Or is a server side/account side feature flag that doesn't allow for being set form the app?
This issue was fixed as of version 2.1.141.
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.