This is a feature request for the Anthropics Claude Code VS Code extension. The problem is that the extension automatically opens diff tabs for every file Claude edits, which is disruptive and clutters the editor. The proposed solution is a new VS Code setting to disable this auto-opening behavior, allowing users to review diffs manually.
A starter prompt for Claude Code, what you'll need, and how to reach them.
You are a senior VS Code extension developer. Fork the `anthropics/claude-code` GitHub repository. The goal is to implement a new VS Code setting that disables the auto-opening of diff tabs when Claude Code edits files. **Task:** 1. Identify the code section responsible for automatically opening diff tabs (likely related to file change detection and editor focus). 2. Implement a new VS Code configuration setting, for example, `claudeCode.autoOpenDiff`, which should be a boolean type with a default value of `true` (meaning auto-open is enabled by default). 3. Modify the identified diff-opening logic to check the value of `claudeCode.autoOpenDiff`. If the setting is `false`, prevent the automatic opening of the diff tab while ensuring the file is still saved and marked as modified. 4. Update the extension's `package.json` to include the new setting's schema and a clear description. 5. Add a brief note about the new setting in the extension's `README.md` if applicable, or in a specific settings documentation file. 6. Ensure all existing functionality remains intact. Provide unit tests for the new setting's behavior, if the project has existing testing infrastructure. If not, describe manual verification steps. **Stack/Services:** VS Code Extension API, TypeScript/JavaScript, GitHub. **MVP Slice:** Focus on getting the `claudeCode.autoOpenDiff` setting to successfully prevent diff tabs from opening in a basic file edit scenario. **Build/Verify Gate:** The setting `claudeCode.autoOpenDiff: false` should be configurable in `settings.json`, and after Claude Code performs an edit, no new diff tabs should automatically appear in the editor. The file should still be saved and the modification indicator should show on the existing tab.
Reach out to developers using AI coding tools, especially Claude Code, by delivering this highly requested feature, then introduce them to AI usage monitoring, agent building, and automated dev workflows.
### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement Problem: When Claude Code makes file edits in the VS Code extension, it automatically opens a [Claude Code] diff tab for every changed file. This is disruptive when working with multiple files — it steals focus and clutters the editor tab bar. The blue modified-file indicator on existing tabs is sufficient to know which files changed. I'd like to review diffs on my own terms, not have them forced open. ### Proposed Solution A VS Code extension setting (e.g., claudeCode.autoOpenDiff: false) to disable the auto-opening behavior while keeping all other functionality intact. ### Alternative Solutions _No response_ ### Priority Critical - Blocking my work ### Feature Category Configuration and settings ### Use Case Example Working in VS with multiple tabs opened and having claude open and jump to another tab is super disruptive ### Additional Context _No response_
Standard for dev work
Standard IDE
Standard for JavaScript/TypeScript projects
Core language for VS Code extensions
New: VS Code API, `package.json` contribution points, extension lifecycle – ~2-3 days
Learn it: Search getting-started ↗
Comment on GitHub issue #25018 (https://github.com/anthropics/claude-code/issues/25018), then open a draft Pull Request to the `anthropics/claude-code` repository.
“I've seen the strong demand for a setting to disable auto-opening diff tabs in Claude Code. I've built a working prototype of this exact feature, and I'm ready to submit a PR with proper tests. Would you be open to reviewing it?”
Open the original ↗