Frequently asked questions

atrium is free during public beta. 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. Public beta 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.

The desktop client runs on macOS 12 or later and is signed and notarized. It can connect over SSH to self-hosted Linux locations on Intel or ARM, including WSL2; the Mac remains the control surface while repositories and sessions stay on the selected box.

Yes. Add a Linux box under Settings → Locations and atrium pairs and provisions it over SSH. Projects, rooms, terminals, agent chats, tasks, notes, source control, and recurring runs can live there while you operate them from the Mac. It is self-hosted remote compute, not an atrium cloud workspace. See the locations docs.

Those desktop clients remain on the roadmap, with no committed dates. Linux is already supported as an SSH compute location, but the full atrium UI still runs on macOS. Each desktop platform needs its own native testing for terminals, file watchers, browser handling, windows, permissions, and signing before we ship it.

macOS 12 (Monterey) or later for the desktop client. atrium ships separate native builds for Apple Silicon and Intel Macs. Expect a roughly 350 MB download and about 700 MB installed; data grows with projects, transcripts, and captures. Optional SSH locations need a reachable Intel or ARM Linux box, including WSL2.

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, Antigravity, Cursor Agent, Kimi Code, OpenCode, Pi, Grok, Hermes, and Oh My Pi as adapters. We don't compete with the agents; we coordinate them. We save your entire workspace locally, restore and resume your active panes, terminals, and agent sessions, and give you the visibility to stay a diligent human-in-the-loop. Autonomous orchestration is possible and we have more planned, 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.

Yes — that's the Timeline. It's a chronological feed of the work in a room: your prompts and the agent's replies, commits, tasks, and notes, grouped by day. Scope it to a workspace, room, or pane, search it full-text, or turn any stretch into a one-click Brief, Update, or Recap that gets written to a note. The feed backfills itself from your git history, tasks, and transcripts, so it's already populated the first time you open it.

A navigable 3D map of every workspace you've ever opened. Each project is a galaxy, each session a star, each major commit a supernova. Click a galaxy for its stats — sessions, top files, adapter mix, recent commits — or scrub a timeline back through the year. There's an optional ambient soundscape, off by default. It's the wide-angle view of where your work has been.

Yes. atrium indexes the content of your past sessions across every adapter into a searchable Vault. Search it from the Library or the new-room picker — results come back ranked by content, with snippets, and fuzzy matching that forgives typos. From the shell, atrium edits <file> lists every past session that touched a given file. Tune indexing depth and time horizon in Settings → Vault.

Built-in adapters today: Claude Code, Codex, Antigravity, Cursor Agent, Kimi Code, OpenCode, Pi, Grok, Hermes, and Oh My Pi. 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. Local projects, sessions, scrollback, and agent metadata are stored on your Mac under ~/.atrium/; remote work is stored on the SSH location that owns it. atrium connects directly to boxes you choose and does not proxy repositories or terminal traffic through an atrium server.

Two things, and only if you choose them. Telemetry, after you make a choice during first run: the core tier contains app lifecycle, active-use heartbeat, version/OS/architecture/locale, and update outcomes; detailed usage analytics and crash stack traces are a separate opt-in. The master switch disables both. Project files, paths, commands, URLs, prompts, transcripts, and task contents are excluded. See the telemetry docs.

And if you turn on notifications in the iOS app, your phone's Apple push token, sealed notification envelopes, and a delivery pass every few days pass through atrium's push relay on their way to Apple. The relay can't read the notifications and keeps no copy. See push notifications and the privacy policy.

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

The iOS app connects directly to the machines you pair it with, too. Push notifications do pass through our relay on their way to Apple, but they're end-to-end encrypted: the relay can't read them. It sees which phone to wake, when, and how often; the push notifications docs list everything it can see.

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.