Your agents.
Your workspace.
Your tools, your models, your existing setup. Agent terminals, interactive plugins, documents, code, Git and live tests in a native workspace, cut to fit your craft.
Version 0.4.2 for Windows, macOS and Linux. All downloads
The AppImage needs WebKitGTK 4.1 installed. How to install it · or use the .deb or .rpm, which install it for you.
Not notarized by Apple yet: run one Terminal command before the first launch. Intel Mac? Get the Intel .dmg.
A setting for your agents.
Run your preferred CLI agents—Oh My Pi (OMP), Claude Code, Codex and more—beside your editor, with their own settings and logins. Split your workspace, or bring one facet into focus.
Refine every change.
Review changes in a file tree, stage or unstage individual files and draft a commit. Compare unified and side-by-side diffs, inspect past commits and explore branches in the searchable Git Graph—all without leaving your workspace.
Test the finer details.
Cairngorm detects the Playwright run and opens a test pane. Follow the browser and its actions, hide or show the walkthrough sidebar, then switch between detected results and terminal output.
Add another facet.
Connect your MCP-capable CLI, ask for a tldraw workflow and refine it beside your terminal. Current development builds keep plugin sessions and local canvas storage separate as you switch projects.
Give it your own finish.
Choose a light or dark theme, including gemstone presets such as Diamond and Amethyst, then fine-tune your colors, contrast and brightness. Adjust terminal and chat text size, move the sidebar and remap shortcuts. Your settings stay on your machine.
Set each connection in place.
See the MCP servers your agents already use, across personal and project configurations. Filter the list, draft a local command or remote URL and choose which agents receive it. User-wide changes keep a backup; restart your agent to pick them up.
Keep your craft close.
Bring personal skills from your agent folders into one view. Read a SKILL.md before using it, turn a skill off or back on, and draft a new one for the work you do.
Documents, in the same setting.
Open documents beside your agent, edit .xlsx values and formulas with the included spreadsheet editor, or add a file format with the document provider SDK. Cairngorm owns saving and conflict checks; installed applications use their own automation APIs. Document guide ↗ · SDK ↗
Download Cairngorm 0.4.2.
Every installer for this version. Development builds, not code-signed yet. Checksums are in Download & install.
Windowsx64
Windows 10 and 11. SmartScreen asks before the first launch: More info → Run anyway.
macOS10.15+
Not notarized yet: see how to open it.
Opening it on macOS: Open the .dmg and drag Cairngorm to Applications. Apple has not notarized this build yet, so macOS blocks the first launch and may say the app is damaged; it is not. In Terminal, run xattr -dr com.apple.quarantine /Applications/Cairngorm.app once, then open Cairngorm as usual.
Before you use the AppImage: to stay small, it uses your system’s WebKitGTK 4.1 instead of bundling it. Install it first, or Cairngorm will not start and will tell you what is missing.
- Ubuntu, Debian, Mint
sudo apt install libwebkit2gtk-4.1-0 - Fedora
sudo dnf install webkit2gtk4.1 - Arch, Manjaro
sudo pacman -S webkit2gtk-4.1 - openSUSE
sudo zypper install libwebkit2gtk-4_1-0
Then make it executable with chmod +x Cairngorm-*.AppImage and run it. The .deb and .rpm packages install WebKitGTK for you.
A few things to know.
What is Cairngorm?
Cairngorm is a native desktop workspace for AI agents and development tools. It brings agent terminals, files, a code editor, Git and test observation into the same app.
Is this a live app?
Yes and no. Every chapter runs the current Cairngorm interface itself in your browser, built from the app's own components, not a recreated mockup or a video. Each one plays a guided tour for you to watch; the demos do not respond to clicks or typing, and Replay walkthrough starts a tour over. What sits behind the interface is sample data: there is no real project, file system, account or agent. Changes stay in memory inside each demo and are gone after a reload; nothing is saved, sent or shared with the rest of the page. The workspace terminals show three conversations rendered by the original installed Claude Code, Codex CLI and Oh My Pi (OMP) TUIs, captured with local sample replies, not external model output. The testing chapter replays a genuine local Playwright run, including its terminal output and browser frames, as Cairngorm observed it. Git history and staging use a sample repository; nothing is committed or pushed. The Documents chapter runs the actual SDK Sample viewer and edits a field without saving. Plugin connection, the custom client and connection states run live on sample configuration. The terminal then replays the genuine Claude Code transcript of a recorded request to the tldraw plugin, and the app's plugin pane shows the real tldraw canvas recorded from that run: the agent's diagram, then a box moved and renamed by hand. A live canvas would need tldraw's own servers, which this page never contacts. MCP servers and skills are samples, not your configuration. No chapter runs an agent, contacts a third party or sends a model request.
Can I use my preferred tools and provider?
Run installed terminal CLIs such as Pi, Oh My Pi (OMP), OpenCode, Claude Code or Codex with their own configuration and authentication. For the native agent and API-backed commit drafts, choose a supported preset or a custom OpenAI-compatible cloud, gateway or local endpoint. Models come from that endpoint, not a fixed Cairngorm catalog; compatibility depends on its API and model features. The named CLI integrations are optional shortcuts, not an exhaustive list of terminal tools.
How do plugins work across projects?
Connect an agent through Settings → Plugins, enable a trusted plugin and run the agent inside a Cairngorm terminal. Visual tools can open an editable panel beside that terminal; the model still decides which tool to call. Current source builds isolate each plugin's MCP session and browser storage by source terminal, so switching projects does not mix their local canvases. This does not duplicate a remote document you deliberately open in both projects, or make plugin panels permanent across app restarts. See the current development changes and plugin connection guide.
Does Cairngorm copy my login or subscription?
No. Existing CLI logins stay with their tools. Cairngorm saves runtime paths and the chosen integration, not exported login tokens or transferred subscriptions. API keys are separately supplied by you or read from a configured environment variable. Detected subscriptions are not used automatically: Cairngorm asks for consent, and “Not now” leaves them unused. Codex login reuse is separate from automatic Claude integration: that requires ANTHROPIC_API_KEY, paid API billing and typing “I understand”; Claude Free, Pro and Max subscriptions are not accepted there. Manually running Claude Code in a terminal is unchanged. After you allow one, verification is a separate step. Scanning is local; verification and AI actions can make model requests and consume quota. API billing is separate from CLI subscriptions.
Does everything run locally?
The desktop app and workspace run on your machine. AI requests still go to whichever provider you configure. Local workspace execution does not mean the model itself runs locally.
Can I download it today?
Yes. Version 0.4.2 is available for Windows, for macOS on Apple silicon and Intel (.dmg), and for Linux on x86_64 and ARM64 (.deb, .rpm and AppImage). The button at the top offers the installer for your system, Download below lists every file, and Download & install adds the checksums. The Linux AppImage needs WebKitGTK 4.1 installed. These are development builds and not code-signed yet. See the changelog for what changed.