VS Code Extension · Midcore for VS Code
The Midcore agent, where your team already lives.
You don’t have to switch IDEs to get the Midcore agent. The VS Code extension brings the same multi-file agent, the same memory, and the same hash-chained audit you get in Midcore Shell — without leaving your editor.
What you get
Inline multi-file agent
Vibe Coding inside VS Code — agents that draft, refactor, and review across files with the same Conscience policy gates as the Shell.
Same memory, same projects
The extension reads your Midcore Personal KB, your Project Vault snapshots, and your account memory. Same context whether you're in Shell or in Code.
Status-bar receipts
Every cloud op produces a signed receipt visible in the status bar. Click to inspect, replay, or audit.
Offline-aware
An RSA-signed subscription snapshot caches in OS keychain. The extension keeps working through short network blips without re-auth.
Install & sign in
- Open VS Code → Extensions (Ctrl/Cmd+Shift+X) → search “Midcore”.
- Install. The first launch prompts a device-code sign-in flow that lands you back in the editor when complete.
- Open the command palette →
Midcore: Open Agent Chat. Your subscription, balance, and entitlements load from the signed snapshot.
What every install enforces
- Subscription signature verified at boot — the extension refuses to load on tampered snapshots; falls back to a re-auth prompt.
- Per-session spend cap — cloud ops respect your configured ceiling; the status bar shows live balance.
- Conscience gates apply — policy denials surface inline as diagnostics with the rule id that fired.
- Signed receipts — every cloud charge is recorded on the same hash-chained audit ledger as the Shell.
Pricing — one subscription, every Midcore app
The VS Code extension doesn’t have its own subscription. One paid Midcore account unlocks the extension along with Midcore Shell, Midcore Code, the CLI, and the Zed extension — all sharing the same balance and receipts.
Starter $19 CAD/mo is the floor. See the tier & product mapping for what each tier unlocks.
When to reach for the VS Code extension
- Your team is already standardised on VS Code and you don’t want to introduce another IDE.
- You want the lightest-weight Midcore surface — the extension adds no extra process beyond what VS Code already runs.
- You need the Midcore agent inline alongside other VS Code extensions (linters, debuggers, language servers) without conflict.
If you spend most of your day in code and want a purpose-built editor, try Midcore Code (the Native IDE) instead.
Read more
- VS Code extension docs
- One router, every app
- All Midcore apps — side-by-side comparison.