[Feature Request] Turn Claude in Chrome on per project (working directory), not globally
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Domain
- cli
Research direction
Nothing here points at a file: the request is a product decision about where configuration scope lives, so the first read is how settings are layered today — ~/.claude.json versus .claude/settings.json and .claude/settings.local.json — and how the existing --chrome/--no-chrome flag and /chrome command resolve the default. Compare with how /mcp and claude mcp add --scope already offer session/project/user scope, since option 2 asks for that pattern. Done means a maintainer has picked one of the three options and the resolution order for the new per-project value is written down before any code is touched.
Written by the indexing model from the issue text.
Description
Problem
Running /chrome and turning Claude in Chrome on in one session changes claudeInChromeDefaultEnabled in ~/.claude.json. That setting is global, so every Claude Code session on the machine gets the Chrome tools, including the ones already running in other projects.
I run many sessions at once, one per project. Only one or two of them need a browser. The others then pay for the Chrome tool definitions in context, and they can drive the browser when they have no reason to.
Today the only per-session control is the --chrome / --no-chrome launch flag. It has to be typed at every start and cannot be changed in a running session without also changing the global default.
Requested
One or more of:
- A project-scoped setting, e.g.
"claudeInChrome": truein.claude/settings.jsonor.claude/settings.local.json, that overrides the global default for sessions started in that directory. - Have
/chromeask whether the change is for this session, this project or all projects (the scope choice/mcpandclaude mcp add --scopealready offer for MCP servers). - More generally: let built-in integrations and plugins be turned on or off per project (working directory) in the same way.
Environment
- Claude Code 2.1.330, Linux (KDE Plasma)
- Dominant language
- TypeScript
- Stars
- 156k
- Forks
- 25k
- Avg merge
- 16h 19m
- Merged PRs (30d)
- 5
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from anthropics/claude-code
-
area:vscode bug has repro platform:vscode platform:windows
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anthropics/claude-code#111416 ·
-
area:plugins area:tui bug platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
anthropics/claude-code#111195 ·
-
area:docs area:security documentation enhancement platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anthropics/claude-code#111180 ·
-
area:ide enhancement platform:macos platform:vscode
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anthropics/claude-code#111172 ·
-
area:mcp bug has repro platform:linux platform:wsl
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
anthropics/claude-code#111077 ·
All issues in anthropics/claude-code
Similar issues
-
The manager preset saves launch definitions without the required file and digest pairPossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
Maintainers usually reply within 1 day