Skip to main content
Your coding agent runs on your Mac. You don’t have to sit in front of it. Nomo Sessions puts your running Claude Code, Codex and OpenCode sessions on your iPhone — on the Lock Screen and in the Dynamic Island. When the agent stops to ask permission for something, your phone tells you, and you can answer it from there. Walk to the kitchen. The agent keeps working. It hits a command it needs approval for, your phone buzzes, you tap Allow, and it keeps going. You never went back to your desk.
A Claude Code session called Refactor the Sessions tab, shown as a Live Activity and as a row in Nomo's Sessions tab

One session in two places: live at the top of the screen, and in the Sessions tab under the computer running it.

The live card carries the model and what it’s doing right now — Fable · Editing — plus the session title, the folder, and which computer it’s on. Below it, the Sessions tab lists your paired computers; open one to see its sessions, split by agent and grouped by project folder.
Sessions is part of Nomo Pro. Status monitoring and usage widgets are free and work without any of the setup below.

What’s supported

Sessions follows the agent running on your computer, not the account behind it, so the list is shorter than Status and Usage.
Claude CodeCodexOpenCode
Codex and OpenCode hand a plugin less than Claude Code does, so a few things land differently on your phone — Using Codex and Using OpenCode are the short lists of what changes.

What you need

  • Claude Code, Codex 0.142+, or OpenCode, on a Mac
  • Either bun or node 18+ — whichever you already have
  • Your phone and your computer paired — one QR scan

How it fits together

Your Mac sends session updates to your phone through Nomo’s relay. The relay can’t read them: everything is encrypted on your Mac and only decrypted on your phone. Nomo’s servers move sealed data around without ever holding the key. That matters for what you can expect — your prompts, file paths, and commands are yours. It also means pairing is a real cryptographic step rather than a login, which is why it takes a scan or a typed code. The exact scheme — key exchange, what the relay can and can’t see, what the plugin reads — is written up in the plugin’s own README, next to the code that implements it:

Architecture and encryption

How pairing derives the key, and why the relay only ever holds ciphertext.

Get setup

Install the plugin

Two commands, for Claude Code, Codex or OpenCode.

Pair your computer

Scan a QR code, or type a one-time code.