Desktop IDE
Midcore Desktop is a standalone IDE with the Outcome Compiler and agent built in. Use it when you want a dedicated environment for vibe coding, multi-file edits, and proof-carrying releases without depending on VS Code or another editor.
Install
Download the installer for your OS from the official download page:
- Download page — choose Desktop / IDE and your platform (Windows, macOS, Linux).
- Run the installer and follow the steps. No separate CLI install is required for basic use.
Verify install
- On Windows, the MSI installer is signed; the User Account Control prompt should display the verified publisher name. macOS shows a notarized publisher in Gatekeeper. Linux .deb / .rpm / AppImage builds publish a SHA-256 you can verify against the checksum on the Downloads page.
- After install, the app launches and shows the Midcore welcome or project view. The desktop app offers a one-click sign-in using your existing web session — no codes to copy.
- Open a folder (File → Open Folder) and confirm the Studio panel, Intent Wizard, and modes are available.
Studio panel parity
The Desktop app ships the same Studio workspace as the web and the VS Code extension: open the Intent Wizard from the activity bar, type one or two sentences about what you want, answer a few clarifying cards, review the plan, and launch. The pipeline, gates, evidence, and release readiness all live in the same workspace.
Get started
- Launch Midcore Desktop and sign in or configure your account.
- Open a project (File → Open Folder) or create a new one.
- Use the main panel to chat with the agent. Same modes as CLI and VS Code: Agent, Plan, Debug, Ask.
- Review diffs in the built-in diff viewer, apply changes, and run gates from the UI when your project uses them.
Same concepts
When to use Desktop
Use Desktop when you want offline-first use, a full IDE with the agent and gates built in, and no dependency on an existing editor. Ideal if you don't already use VS Code or want a dedicated Midcore environment. The VS Code extension is better if you already work in VS Code; the CLI is best for CI and scripting.