#073Tutorial3 min

Discover Hackaiz in VS Code

Connect the existing extension, scan local code with confirmation, and read results without leaving your editor.

Hackaiz team · updated 21/11/2026

Illustration: a developer uses an editor and a terminal.
Illustration: a developer uses an editor and a terminal. Illustrative photo, not a screenshot.

01What the editor extension actually does

Hackaiz has an editor extension, not just a website link or a suggested future integration. Its source and packaged extension files are in tools/hackaiz-editor. The extension contributes a Hackaiz shield in the Activity Bar, commands for scanning local code, and views for connected platforms. Local code scanning and a saved-platform analysis are separate workflows: the first submits eligible workspace files after confirmation, while the second requests an analysis of a platform selected from your account.

The extension is useful when you want to investigate a finding next to the source. Workspace findings appear as sidebar entries, editor underlines and entries in the Problems panel. Clicking a local finding opens its file at the indicated line. That position is a starting point for review, not an instruction to replace the line blindly: understand where the value comes from and whether the surrounding code performs the necessary validation.

02Connect your personal key

Use “Hackaiz: Connect personal key” from the Command Palette or “Connect personal key” in the Hackaiz view. The extension asks for a personal key beginning with hkz_. Create it in Hackaiz Settings, under Integrations. Reading connected information requires read access; launching analyses also needs launch. Choose the smallest platform scope that serves your work rather than sharing a broadly authorized key across a whole team.

The implementation keeps the key in VS Code SecretStorage instead of a project settings file. Do not paste it into source, screenshots, issue comments or an assistant conversation. The project setting hackaiz.projectId identifies the chosen platform; it is not a substitute for the secret key. If the platform list does not match what you expected, check which Hackaiz account created the key before assuming your repository authorization has disappeared.

  1. 1Open the Hackaiz shield in the Activity Bar.
  2. 2Connect a personal key with the permissions needed for your task.
  3. 3Use “Hackaiz: Choose platform” when working with saved-platform results.

03Run a deliberate first scan

For local sources, select “Hackaiz: Scan this workspace” or “Hackaiz: Scan current file”. Open a folder first; for a file scan, make the desired local file the active editor. Hackaiz prepares eligible content and shows information about the submission and excluded files before asking you to continue. Each confirmed scan uses account credits, and the actual charge appears with the result. Cancel if the scope is not the one you intended.

The workspace collector excludes common dependency and build directories, secret filenames, binary files, generated maps and files above its per-file limit. Review exclusions rather than moving credentials into a file that will be accepted. A local code scan is not an authorization to probe a website. Website and API analyses still require domain proof through the DNS TXT record _hackaiz, the HTTPS verification file, or that file created by your project AI.

04Read findings and keep approvals on Hackaiz

The sidebar groups findings as Danger, To fix and To watch, with technical severity suffixes where applicable. Open a finding, hover the underline for a short explanation, or use “Show details” for the workspace finding write-up. Review the observation, its impact and the next action. Evidence presented in the detail view is masked. A clean list means no finding was returned for that scan; inspect completion and file coverage before drawing a wider conclusion.

“Hackaiz: Open report and approvals” opens the web application for the selected platform. This is where you continue a review that needs the full platform context or correction approvals. The extension does not change code, create commits or merge anything. Hackaiz fixes are draft GitHub pull requests reviewed and approved by a human, never automatic merges. The refresh interval setting updates displayed information; it should not be mistaken for an automatic scan of every edit.

Frequently asked questions

Was this article helpful?

Related articles