Developers
VS Code extension
See findings on the lines they are about, apply verified fixes to your working tree, triage and start fix runs from VS Code.
Nullgap for VS Code shows your organisation's findings inside the editor, for the repositories you have open. It uses an API key and the same records the console shows.
#What it does
| Problems on the line | Each finding becomes a problem on its file and line. Critical and high findings are errors, medium are warnings, low and info are information. A finding that a probe reproduced is tagged Proven. The problem's code links to the finding in the console. |
| Findings view | The Nullgap icon in the activity bar lists findings by severity, then by file. Select one to go to its line. Right-click for the actions below. |
| Apply verified fix | Offered in the lightbulb and the view only when the finding has a fix that passed its checks. The extension runs git apply --check and then git apply in the repository. Nothing is staged or committed. If your copy of the file has changed so that the fix no longer fits, nothing is changed and you can open the fix in the console. |
| Show proof | Opens the finding in the console, with its evidence and proof. |
| Mark as false positive, Accept risk | Asks for a reason, which is recorded with the decision and shown in the decision history. Needs a key with the write scope. |
| Start a fix run | Nullgap AI writes a fix, checks it and opens a pull request. It uses fix credits, so the editor asks you to confirm first. Needs write. |
| Status bar | How many proven findings are open in the workspace, or Nullgap: sign in. |
#Install
The extension is installed from a .vsix file. Ask your Nullgap administrator for it, or build it from the Nullgap source with pnpm --filter @nullgap/vscode package. In VS Code, open the Extensions view, choose the ... menu, then Install from VSIX.... VS Code 1.90 or later is needed.
#Sign in
- In the console, open Settings, then Access, and create an API key. Read is enough to see findings; triage and fix runs need Write.
- In VS Code, run Nullgap: Sign in from the Command Palette and paste the key.
The key is checked with your Nullgap server and then kept in VS Code's secret storage, which uses your operating system's keychain. It is not written to settings or logs. Nullgap: Sign out removes it. Keys that a connected app holds are for the MCP server only and are not accepted here.
#Settings
| Setting | Default | Meaning |
|---|---|---|
nullgap.url | https://app.nullgap.dev | The address of your Nullgap console. |
nullgap.organisation | empty | Your organisation's slug. Empty uses the organisation the key belongs to. |
nullgap.showStates | open | Which finding states to show. |
#Matching your repository
The extension reads the origin remote of each open repository and matches it to the repositories connected to your organisation. Remote addresses on GitHub, GitLab (nested groups included), Bitbucket and Azure DevOps are understood, over HTTPS and SSH. If a repository does not match, the Nullgap output channel says why.
Findings refresh when you sign in, when you run Nullgap: Refresh findings, when VS Code regains focus (at most once a minute), and when you save a file that has findings.
#For integrators
The extension asks for a repository's findings with GET /api/orgs/{org}/findings?repoId=…. To ask for the findings in one file, add file with the path relative to the repository root, for example file=src/routes/users.ts. The match is exact. The MCP tool list_findings takes the same filter as file.
Nullgap documentation