AI Feature Source ControlOrganize your Git changes by feature, directly in VS Code. When you're working on several things at once, the Source Control panel can get messy. Files related to the same change might be spread across different folders, making it harder to see what belongs together. AI Feature Source Control adds a Changes by Feature view that groups modified files based on their purpose. It uses OpenAI Codex or GitHub Copilot to suggest the groups, and you can adjust them yourself. What it looks likeSay you've been working on an export feature and fixed an unrelated validation issue. Instead of seeing all the modified files in one list, you get something like this:
You can choose how much detail to display: features only, features with components, or features with individual tasks. The grouping is generated once and reused when you switch between detail levels. Work with your changesThe extension includes the Git actions you'd normally use in Source Control:
You can also discard changes, switch branches, and manually move files between groups when the AI gets something wrong. Everything works with your existing Git repositories. The built-in Source Control view remains available. Getting startedInstall AI Feature Source Control from the VS Code Marketplace, then open the Source Control panel. You'll find a new section called Changes by Feature. Choose your AI provider in the extension settings: GitHub Copilot uses the models available through VS Code's Language Model API. OpenAI Codex uses a Codex executable, either installed separately or bundled with the official Codex VS Code extension. Click the sparkle icon next to a repository to classify its changes. The extension will ask for permission before sending any diffs to the selected provider. Once classified, you can browse your changes, adjust the groups and stage files as usual. Using CodexStarting with v1.1.0, the extension can automatically find Codex on your machine. It checks the following locations:
If you already have Codex installed in VS Code, you may not need to install the CLI separately. To use automatic detection, set:
You can leave the executable path setting at its existing default as well. No additional configuration is needed when Codex is detected successfully. If automatic detection fails, you can still provide the full path to your Codex executable:
The executable must be authenticated and support the CLI options used by this extension. Note: The Codex binary bundled with the official VS Code extension is an implementation detail, not a public integration API. Its location or behavior may change in future Codex updates. SettingsYou can configure the model, reasoning effort (when supported), classification detail and how much context gets sent to the AI. For example:
Classification is incremental, so unchanged diffs with cached results don't need to be analyzed again. You can also disable automatic classification if you'd rather control when AI requests happen. PrivacyBefore sending diffs to your AI provider, the extension excludes common sensitive files and attempts to redact recognizable credentials. Only limited diff excerpts are submitted for classification, and you can configure additional file exclusions. These protections aren't exhaustive. Sensitive information can still appear in a diff, so avoid classifying repositories containing information you can't share with your AI provider. A local preview command lets you inspect classification data without making an AI request. Current limitationsGrouping works at the file level. If a file contains changes for two different features, it will still appear in one group. Staging a file includes all its changes. For partial staging, you can continue using VS Code's built-in Git tools. AI classifications are suggestions, so you may occasionally need to move files into a different group. FeedbackThe extension is open source. Issues, bug reports and contributions are welcome. GitHub repository · Report an issue MIT License. |