In release — preview. The IDE extension is under active construction and not yet generally available. What’s described here is the design it’s being built to; treat everything as preview until GA.
The IDE extension is Shipmoor’s eyes and hands in the editor: scan findings surfaced as native editor diagnostics, right where the code is, with your entitlement state tracked alongside.
A deliberately thin client
The extension reimplements neither detection nor auth. It shells out to the local, licensed shipmoor CLI for everything, consuming the same stable JSON contracts every other Shipmoor surface uses:
| What you see | Where it comes from |
|---|---|
| Findings as diagnostics | shipmoor scan --json (shipmoor.scan.v1) |
| Which features are on | shipmoor capabilities --json (shipmoor.capabilities.v1) |
| Identity and grace state | shipmoor whoami --json (shipmoor.identity.v1) |
That design has two consequences worth caring about:
- Local-first, like everything else. The scan runs on your machine via the CLI; no source leaves it, and there is no Shipmoor cloud behind the extension.
- One source of truth. The extension can never disagree with the CLI, your CI, or your agent harness about what a finding is — they all read the same engine’s output. A rule fixed in the CLI is fixed everywhere at once.
Where it fits
The same change can be checked at four moments: as the agent edits (Agent Harness, preview), inside the agent’s own loop (Agent Skills), in your editor (this extension), and at the merge gate (CI). The extension is the human-facing one — for when you are the one editing, or reviewing what an agent did.
Next
- Install & activate — Marketplace install and entitlement activation.
- Output contracts & schemas — the contracts the extension consumes.
- Plans & tiers — where the IDE extension sits in the IC plan.