Skip to main content

A startup inside Midcore

Vibe Coding

Legacy craft. AI coders. Your editor.

The fastest path from "what should I build?" to a signed commit. Native IDE with the agent baked in, or a CLI that drops into the editor you already love. Same memory. Same policy stack. No tab juggling, no copy-pasting, no losing the thread.

Pick a trackSee the philosophy

Why two tracks

Some craft is in your fingers. Some is in your editor. We honour both.

Half of you have an editor older than the agent ecosystem. The other half want a purpose-built cabin with the agent at the wheel. Vibe Coding is the answer for both — the same brain, two ways in. Pick the one that fits your hands, and never lose what you already know.

Two tracks

Pick the seat you actually code in.

Track A

Native Midcore IDE

A real editor with the agent in the cabin.

A purpose-built editor that ships with the agent inside it. Multi-cursor, language servers, syntax-aware diffs — everything you expect from a serious IDE. Plus an agent that already knows your projects, your preferences, the patterns you accept, and the things you have asked it never to do.

  • One installer, everything inside — no extension store hunt
  • Agent reads the same memory + policy stack as Maestro Chat
  • Inline gates: refuse a write, cite the rule, suggest the fix
  • Native multi-file diffs with rollback receipts
  • Works offline once installed — no telemetry tax for thinking
Download the IDERead the IDE pitch

Track B

Midcore CLI

Bring your editor. We bring the agent.

A single binary that drops into VS Code, JetBrains, Neovim, Helix, Zed — anywhere you already write code. Speaks the same agent protocol the IDE does, reads the same memory, enforces the same policy. The editor you love + the brain you trust, in one shell.

  • Native bindings for the four editors most teams already use
  • Same /commands as the Shell — `/agent`, `/plan`, `/policy`
  • Single binary, no Python or Node runtime on your $PATH
  • Installs in seconds; talks to the same backend the IDE does
  • Auto-updates only when you opt in — never on a deadline
~/projects/acme-landing
$ midcore install
→ Detected VS Code, Neovim. Binding both.
$ midcore /agent "refactor auth flow"
✓ Plan ready. 4 files. Open in editor? [Y/n]
Install the CLISee the editor bindings

One brain, two seats

The same memory. The same gates. Wherever you sit.

Pick the IDE or pick the CLI — the agent on the other side is the same agent. Same long-term account memory ("you usually pick pnpm"), same policy stack ("never push to main"), same evidence ledger, same approval gates. Switching tracks does not reset the relationship.

The philosophy

Vibe is not vibes. Vibe is rigour with a clean cabin.

AI coding tools that ship as a glorified chat ignore the most important thing about coding: it is craft. You have muscle memory, named patterns, a feel for what good looks like in your domain. Vibe Coding leans into all of that. The agent is a deeply capable collaborator, not a wrapper that asks you to start over every session.

AI coders. Your editor.

Pick a trackBack to all products