FixBugs for VS CodeAn AI agent that triages alerts, detects bugs and resolves them. Current capabilities:
How FixBugs is differentFixBugs is built for debugging existing systems, not for writing isolated code from a prompt.
From report to verified fix1. Start from a bug report or a freehand description
Use the remote or a local folder as your repository. 2. Build the analysis context
3. Review root-cause hypotheses
4. Generate a plan
5. Review the diff
6. Validate the fix
7. Review and address feedback
Start in VS Code
Privacy and trustFixBugs collects only aggregated, anonymized operational metrics such as runtime health, and crash status. Telemetry does not include logs, prompts, source code, repository contents, file paths, usernames, secrets, or other user information (PII). Users can turn off telemetry from settings. For the privacy policy and data handling details, see fixbugs.ai/privacy. Windows Smart App ControlThe Windows package includes a bundled local FixBugs runtime. Some Windows 11 or enterprise application-control policies can block newly published bundled runtimes until the publisher gains https://learn.microsoft.com/en-us/answers/questions/5791210/application-signed-and-blocked-by-smart-app-contro. If Windows blocks the bundled runtime, follow your device or organization security policy. Do not weaken device security settings to run the extension. Bundled Runtime PackagingRelease VSIX packages include the compiled FixBugs runtime produced by the release pipeline for each target platform. The packaging stage builds from the private Azure source checkout for the run, stages only the downloaded binary artifact into That validator enforces the source-retention policy for compiled runtime modules. This raises the bar for casual source inspection in the shipped VSIX, but it is not cryptographic secrecy. Support
|
Start a fresh triage or load an existing debugging session.
Paste an issue URL or raw report, then choose the repository to analyze.
FixBugs gathers issue details, repository context, logs, metrics. deployment configuration and traces.
The analysis shows the supporting context including logs and code
Review the evidence behind each possible root cause.
Refine the hypothesis, or create a fix from the selected root cause.
The plan has all the tasks needed to address the bug.
Apply/Remove and refine the fix.
FixBugs verifies the fix by reproducing the bug.
Multi-model code review before opening a PR.
Address only the review comments you select.
We explain all the changes made and why.