atrium on iPhone and iPad

The atrium mobile app lets you follow and continue work running on your computers and servers. Agents, commands, and repositories stay on their owning machine; your phone or tablet is another way to reach them.

The app requires iOS or iPadOS 26 and is currently in a private TestFlight beta. Request access from Settings → Remote access → Phones & tablets in the desktop app, or through atrium's Discord.

Pair your first machine

1. Open Settings → Remote access → Phones & tablets on the computer running atrium.
2. Choose Pair a device to show its pairing QR code or link.
3. In the mobile app, scan the code or open the pairing link and complete pairing.
4. Pick a project and open a conversation, or use New session to launch an agent on that machine.

Pairing enables the computer's listener automatically. The connection is encrypted and the pairing link pins the computer's identity. An unexpected identity change is a connection problem to resolve, rather than a reason to silently trust a replacement machine.

You can pair more than one machine. Settings → Locations on the phone shows each machine's connection state, address, name, and reconnect controls. The desktop's outbound servers and paired computers can also be shared with the phone, subject to approval on the machine granting access. See Locations.

Reach your machines away from home

atrium can use Tailscale to reach a paired machine away from your local network. The desktop configures this under Settings → Remote access → Network; the phone offers a sign-in after pairing or when it needs one to connect.

The mobile app includes its own Tailscale connection. Joining requires your consent and makes the phone a member of that Tailscale network. A reachable local-network route can still be used at home. A server the phone cannot reach directly can be reached through its paired desktop when that desktop is available and has a working link to the server.

An unreachable machine keeps its last saved project and activity view visible, with a connection explanation and repair action where available. A saved view is not a live connection: sending prompts and making changes require the machine to be reachable.

Work with agents

Use the projects and rooms sidebars to choose where you are working. Activity shows which agents are working, waiting for an answer, or put away for later. Tapping a card opens its conversation; permission prompts and questions can be answered from the phone.

The launcher lets you choose the agent, launch profile, model, effort, permission mode, and session to resume. In a conversation you can send text or photos, dictate a prompt, interrupt a turn, and inspect tool calls and file changes. / and @ open command and reference suggestions. Select transcript text to copy or quote it into a reply.

Long-press a project to start, stop, or restart its saved run commands and view their output. Commands run on that project's machine. New project binds a folder on a selected machine; it does not create a repository on the phone.

Arrange panes on iPad

An iPad can tile up to four panes from a room when space permits. Use Split right or Split down to open a launcher beside a pane, or drag a pane from the rooms sidebar onto the stage. Drag seams to resize; double-tap a seam to even the split.

Hiding a pane removes it from this device's stage while leaving it in the room. Move to new room changes its room on the owning machine; Close closes it. The layout you choose on the iPad is kept on that device, while moves between rooms change the shared project.

Projects, rooms, and Activity can be opened with the sidebar controls or sideways swipes. On iPhone, the same sections fit into a narrower navigation layout.

Browser and source control

The mobile browser follows the desktop browser pane's address and navigation. For supported pages it can carry the desktop's browser login and reach a development server bound to that computer's localhost through the paired connection.

The source-control pane shows repository changes and diffs on the owning machine. Edits reported in a conversation also open as diffs. Unsupported pane types show a desktop-only notice.

Walk Mode

Turn on Walk Mode beside the composer's microphone to talk with an agent and hear its replies. It works with the active conversation and can keep speaking while the phone is locked. Spoken progress and replies appear in the conversation so you can return to reading later.

Settings → Walk Mode controls large type, announcements when a session needs you or finishes, and whether you can talk over the voice. With Talk over the voice on, the microphone stays open during speech; on AirPods this uses call-quality audio. Turn it off for higher-quality playback and use the headset's interrupt control when needed.

Choose a voice under Settings → Walk Mode → Voice. Natural voices run on-device after an approximately 105 MB download. The download uses Wi-Fi unless you allow cellular data. The system voice works while that download is pending and serves as a fallback if the natural voice cannot run.

Notifications and Live Activities

After pairing, enable notifications on the phone to hear when an agent finishes, asks a question, or needs permission. A Live Activity can show ongoing work on the Lock Screen and Dynamic Island. Supported permission actions can be answered there after device authentication; questions that need a written answer open atrium.

Using atrium on one of your devices holds notifications to the others. The desktop's Paired phones & tablets list includes notification switches and a test action. See Push notifications for delivery, encryption, and what the relay sees.

Device preferences and removing access

The phone's This iPhone or This iPad settings control its appearance, wallpaper, voice, dictation, and haptics. A machine's own settings page controls supported defaults for new sessions on that machine. Conversation view options on the phone are local to the mobile device.

Use Forget on a machine's mobile settings page to remove it from the phone. If reachable, atrium also requests revocation there; separately paired servers remain paired. On the desktop, Revoke removes a paired phone's access and the related introductions it granted. If a phone is lost and used Tailscale, also remove its node from your Tailscale network as directed by the revocation notice.