Architecture topicVS Code

FixBugs for VS Code

Start in the editor, review the investigation before code changes

FixBugs for VS Code turns an incoming bug into a reviewable triage session. The engineer can inspect the investigation, ask questions, refine hypotheses, approve a fix plan, review diffs, and validate results without leaving the editor workflow.

FixBugs for VS CodeVS Code debugging extensiondeveloper-native debuggingdiff review
VS Code workflow: the engineer stays in control from bug input through investigation review, diff review, and PR creation.

01

Local-first privacy

In local mode, source code, logs, traces, metrics, generated diffs, and validation artifacts are processed and stored on the user's machine.

02

Developer-guided triage

Run automated triage when the path is clear, or steer the workflow through chat, hypothesis selection, and fix-plan review when the bug needs human judgment.

03

Validated fixes

Reproduction tests and validation output connect each diff to the original failure, helping reviewers catch regressions before merge.

Product screenshots

Bug input: start from an issue, alert, or raw report.
Hypothesis detail: inspect the analysis before generating a fix.
Chat: steer the investigation and ask for clarification.
Diff review: accept, reject, or refine changes at review time.

Continue reading

Ready to evaluate FixBugs?

Start with the workflow surface your team already uses, then use this architecture resource for the technical review.