Frequently asked questions

atrium is free during early access. A paid model is planned for later, but the plan is to keep pricing affordable, predictable, and tiered by org size, not feature-set. No ambiguous “credits” system, expensive “agent”, or extra fees for features that don't carry real operating cost.

No — anyone can download from the releases page. “Early access” just means features are still shifting fast and the feedback loop is open. Bugs you find, features you request, and rough edges you flag genuinely shape the roadmap.

macOS only at launch. atrium is signed and notarized, so Gatekeeper accepts it cleanly on first launch — no “this app couldn't be verified” warnings.

On the roadmap, no committed dates. atrium is built with Tauri, which makes the cross-platform port mostly mechanical, but each platform needs its own native testing pass and has OS-specific nuances — terminal rendering, file system watchers, browser handling, window management, code signing — before we ship it. If you'd use atrium on Linux or Windows, drop a 👋 in Discord so we can prioritize.

macOS 15 (Sequoia) or later. Universal binary — runs natively on both Apple Silicon and Intel Macs. Around 100 MB installed; idle RAM use is low (terminals scale with active agents).

Cursor is an AI IDE with its own model integrations. Warp is an AI-powered terminal. Zed is a fast editor with collab features. atrium is none of those — it's the workspace around whatever AI CLIs you already use.

atrium hosts Claude Code, Codex, Gemini CLI, and others as adapters. We don't compete with the agents; we coordinate them. We save your entire workspace (locally) and restore/resume your active panes, terminals, and agent sessions and we give you the features you need to efficiently operate across many sessions and be a diligent human-in-the-loop. Autonomous orchestration is possible and we have more plans for this, but we keep you in the driver's seat.

atrium isn't an editor — it's a workspace shell. Each pane can be a terminal, browser, editor, or task view, and the layout, scrollback, and agent sessions all persist together. That model doesn't fit inside an editor extension; it needs to own the workspace shell.

The adapter SDK is MIT-licensed and lives in a public GitHub repo — that's where the community surface is. We also have a robust plugin/extension ecosystem on our roadmap. The atrium app itself is closed source for now to give the project runway. We may revisit this later.

Built-in adapters today: Claude Code, Codex CLI, Gemini CLI, and Cursor CLI. Each is wired through atrium's adapter system, which handles session detection, persistence, and resume across restarts.

Yes — that's exactly what the adapter SDK is for. An adapter is a small JSON manifest plus a few hook scripts describing how to detect and resume the agent's sessions. See the adapter docs for the full spec, or open a request in Discord and we'll help. Just about any CLI harness can be supported, but the level of integration depends on features. If it has robust hooks, it can tap into everything atrium provides.

Local-first by design. Workspaces, sessions, scrollback, agent metadata — all stored on your machine under ~/.atrium/. atrium doesn't have a server-side account, and your code never leaves your machine. If/when we offer cloud integrations, it'll be totally transparent and opt-in.

Telemetry and anonymous errors & stack-traces are opt-in. Full crash dumps stay local unless you explicitly share them. The only outbound calls atrium makes by default are: checking for app updates, and (if you've opted in) anonymous usage diagnostics. See the privacy policy for the full story.

No. atrium doesn't proxy or intercept agent traffic. When you launch Claude Code, Codex, or Gemini inside an atrium pane, that agent talks directly to its own provider — atrium just hosts the terminal and persists the session metadata.

Public issue tracker: github.com/jonnyasmar/atrium-issues. Include your atrium version (title bar or atrium > About), your macOS version, what you expected, and what happened.

For “is this expected?” sanity checks before filing, drop into #bugs on the Discord.

Best place is the Discord — #feedback for ideas, #general for everything else. We read every message.