team
4 questions
- AI
How do I enable auto mode for my team without giving Claude my prod credentials?
Auto mode reads its `autoMode` config from user, project-local, and managed scopes; the classifier ignores `<repo>/.claude/settings.json`. Roll out via enterprise managed settings (the only layer developers cannot weaken) and write rules as prose, not as `Bash(...)` patterns.
- AI
Should I use Claude Code on the web or in my terminal?
The web runs in an Anthropic-managed cloud VM cloned from your GitHub repo; the CLI runs on your laptop with full local access. Use the web for clean-VM tasks (CI fixes, code review, fresh-repo questions) and the CLI for anything that needs your local environment, secrets, or sibling repos.
- AI
How do I see what's eating my Claude Code budget?
Run /usage in any session for the local dollar estimate; the Claude Console Usage page is authoritative. For teams, an admin workspace centralizes tracking; for org-wide attribution, large deployments often add LiteLLM in front. The biggest wins come from model choice, prompt-cache hit rate, and not running an idle agent team.
- AI
How do I share my Claude Code setup as a plugin with one config file?
Plugins are how you turn `.claude/` into something a teammate installs with one slash command. Two config files (`plugin.json` + `marketplace.json`), one git repo, one `/plugin install`. Plus the namespacing rule that surprises people and the version-pinning trap that quietly stops updates.