Reference
Editor extension
The Atmos extension for VS Code and Cursor runs the same scan and the same rules inside your editor. Findings appear as squiggles and in the Problems panel. A findings view groups them by rule or package and shows the full trace for each one, and dependency findings mark the affected entry in the lockfile itself.
Install#
The extension runs the atmos binary from your PATH, or from atmos.binaryPath. If the CLI is not installed yet, start with the Quickstart.
- Download the
.vsixfrom the Atmos dashboard and install it with the Extensions: Install from VSIX command. - Sign in once from a terminal with
atmos login(the install script already did this). The extension uses that sign-in and asks for it when it is missing. - Save a file, or run Atmos: Scan Workspace Now. Findings appear inline and in the Atmos view in the Activity Bar.
How it behaves#
| Behavior | Detail |
|---|---|
| Scan trigger | On save (default), as you type, or manual. Rescans after an edit recheck only what changed. See warm scans. |
| Credentials | The extension holds no credential of its own. Every scan runs the CLI, which uses the sign-in stored by atmos login, so signing out in the terminal signs the editor out too. |