Cipherwake — Trust Status Bar (VS Code / Cursor)

Status bar deploy gate for AI coders. Shows the latest pqcheck deploy-check verdict — PASS / REVIEW / BLOCK — inline in your editor. Green when clean, red on drift. Built for Cursor + VS Code + Copilot + Claude Code users whose deploy decisions happen in chat, not in a PR comment no one reads.

Why this exists

Cipherwake's flagship product is the pqcheck CLI + the GitHub Action. Both surface a Trust Diff comment on every PR — works great for human PR review workflows.

But a growing class of developers ship code via Claude Code, Cursor, Aider, and Zed. They never open the PR; their AI coworker deploys directly. The PR comment is a dead surface for them. This extension is the fix: the same Trust Diff data, rendered persistently in the editor status bar so you can never miss a regression.

Built around a stable on-disk interface: the pqcheck CLI writes ~/.config/cipherwake/last-scan.json on every --ai-mode scan. This extension reads that file. No network calls from the extension itself, no telemetry, no account required.

Install

1. Install pqcheck v0.15.0+: npm install -g pqcheck (or just use npx pqcheck per-scan; no global install needed).
2. Install this extension from the VS Code Marketplace (or Cursor — same extension).
3. Run a scan in your terminal: npx pqcheck cipherwake.io --ai
4. Status bar updates instantly. Goes red on ship_decision=block, yellow on review, green on pass.

What you see in the status bar

✓ cipherwake.io · PASS · DBR 2.4 A · LOW       (everything fine — green background)

⚠ cipherwake.io · REVIEW · DBR 4.1 C · HIGH     (something needs attention — yellow bg)

✗ stripe.com · BLOCK · DBR 8.2 F · CRITICAL    (revert this deploy — red bg)

🕐 Cipherwake — stale (3d ago)                  (scan is old; click to copy re-scan command)

🌐 Cipherwake — no scan yet                     (first-time user; click to copy command template)

Click the status bar item for a popup with full details + an "Open full report" button that takes you to the live /r/<domain> URL in your browser.

Commands

Available from the command palette (Cmd+Shift+P / Ctrl+Shift+P):

• Cipherwake: Show last scan details — popup with the latest scan summary + action buttons
• Cipherwake: Open full report in browser — opens cipherwake.io/r/<your-domain>
• Cipherwake: Copy 'npx pqcheck --ai' command — copies the re-scan command to your clipboard
• Cipherwake: Refresh status bar — manually re-read the state file (rarely needed; the extension watches the file automatically)

Settings

{
  "cipherwake.stateFile": "/path/to/last-scan.json",
  "cipherwake.staleThresholdHours": 24
}

• cipherwake.stateFile — Override the state file path. Default: ~/.config/cipherwake/last-scan.json. Useful if you run pqcheck under a different HOME or want a per-project state file.
• cipherwake.staleThresholdHours — How old a scan can be before the status bar shows "stale" and prompts a re-scan. Default: 24h.

Privacy + permissions

• No network calls from this extension. All data comes from a local file written by the pqcheck CLI you control.
• No telemetry. The extension does not phone home about your usage, your code, or your scan results.
• Read-only on the state file. The extension never writes to last-scan.json — only the pqcheck CLI does.
• No access to your code. The extension reads exactly one file (the state file) and nothing else.

Compatibility

• VS Code 1.75+ (released January 2023; covers virtually all current installs)
• Cursor (any recent version — Cursor is a VS Code fork using the same extension API)
• Other VS Code-API-compatible editors (VSCodium, code-server, etc.) should work but are unverified

License

MIT. Source at github.com/cipherwakelabs/pqcheck/tree/main/extension-vscode.