Quickstart
Install FixBugs, sign in, and run your first triage on your own repository.
On this page
To see FixBugs work, install the extension, sign in, pick how commands and models run, and start a triage from a real bug report in your repository. You end with Investigation Insights and Possible Causes for that bug.
Before you start
- VS Code 1.85 or later.
- Windows x64, Linux x64, or macOS on Intel. Apple silicon Macs are not supported in version 0.1.0.
- Your repository open as a folder in VS Code.
- A bug report: an issue URL from GitHub, GitLab, or Jira, or the report text.
Install FixBugs
- In VS Code, open the Extensions view.
- Search for
FixBugs. - Select Install.
- Select the FixBugs icon in the Activity Bar. The FixBugs sign-in page opens.
Sign in
- Select a sign-in method: GitHub, GitLab, Jira, or Email.
- Finish signing in. FixBugs asks How should FixBugs run commands? If it does not, run
FixBugs: Change Execution Modefrom the Command Palette.
Choose an execution mode
After sign-in, FixBugs asks How should FixBugs run commands? Commands are the builds, tests, and reproductions FixBugs runs while it investigates and validates.
| Mode | Where commands run |
|---|---|
| Local, sandboxed | On this machine inside an OS sandbox. Writes stay in the workspace folder, temp, and toolchain caches; .git is read-only. |
| Local container | In a container built from your repository's Dockerfile or dev container configuration. |
| Remote sandbox | On the FixBugs sandbox service. FixBugs uploads the files git does not ignore and your full shell environment for each run. Do not use it with production secrets in your environment. |
| Local, unsandboxed | Directly on this machine with your user's permissions. No isolation. |
On Windows, Local container is offered when Docker is running and the repository has a Dockerfile or dev container configuration.
FixBugs checks your machine and marks one mode Recommended.
-
Select the Recommended mode.
If Remote sandbox is recommended and your environment holds secrets you must not upload, select another mode.
-
Select Use this mode. The mode shows Current.
-
Select Triage home (the house icon). The FixBugs home opens.
In a narrow Side Bar, select More triage actions, then Triage home.
To change the mode later, run FixBugs: Change Execution Mode from the Command Palette.
Choose model access
New accounts start on Free Trial with FixBugs plan selected. To change model access, select the Settings menu at the top right, then Settings, and choose under LLM Access:
- FixBugs plan: FixBugs managed models.
- BYOK: your own API key from a supported provider.
- Codex subscription: sign in with your ChatGPT account.
Choose your models explains each option and which models run.
Start your first triage
With FixBugs plan, each new bug you investigate counts as one fix, once per billing month (on Free Trial, one of your 5 trial fixes). More work on the same bug that month — follow-up questions, re-runs, sandbox runs — does not count again. Work on your own key or Codex never counts.
- On the FixBugs home, select Start New Triage.
- If you have an issue link, select Issue URL and paste it. If not, select Paste Text and paste the report. GitHub, GitLab, and Jira URLs are detected automatically.
- Under Repository, confirm which repository the bug belongs to.
- Select Continue.
FixBugs opens the bug report and starts investigating.
Read the results
- When the analysis is ready, select View Analysis. Investigation Insights summarizes what FixBugs learned from the report and your code.
- When the causes are ready, select View Possible Causes. Each one explains what FixBugs believes is wrong.
- To question or refine a result, select Open in Assistant.
FixBugs continues to a Plan and a Fix. Nothing changes in your workspace until you select Apply Fix.
Next steps
- What is FixBugs: the full path from signal to a validated fix.
- Choose your models: switch model access or pick different models.