There are two ways to build a dashboard for coding agents. You can ask people to run their agents through your wrapper, or you can read what the agents already record. Orbtile does the second, wherever it can. You keep starting sessions the way you always have, and the keypad keeps up.
Agent by agent
- Codex: nothing to install. Orbtile reads Codex's own session files and signals, so desktop chats, terminal sessions and
codex execruns all show up. Optional hooks add a compacting state and slightly earlier updates, and Codex asks you to review and trust them first. - Claude Code: a small Claude Code plugin sends session events to Orbtile on your computer. Its hook scripts never block or fail your session: if Orbtile isn't listening, Claude Code carries on as normal.
- ZCode: Orbtile reads ZCode's task databases, read-only, and adds one marked hook entry so the keypad can answer permission requests. It keeps a backup of the original settings.
- Antigravity: Orbtile reads the desktop app's own list of conversations. Nothing is installed in Antigravity.
Read-only by default
Where Orbtile opens an agent's database, such as Codex's or ZCode's, it opens it read-only. The only thing it adds, where an agent needs it, is a plugin or a hook entry, with a backup of what was there before, and removing the integration in Orbtile's settings takes it out again.
Everything stays on your computer
The events from your agents go to Orbtile on the same computer and stay there. With the phone pad, the tiles travel to your phone over your local network, never to our servers. For sessions on a server, Orbtile connects with your own SSH alias and keys and reads a bounded amount of display data; full transcripts aren't copied. Orbtile's automatic reports never upload prompts, transcripts, source code or task text.
And for everything else, an API
Not every tool records what Orbtile needs. For those, the Adapter API lets any agent or script report its own sessions. On a Mac it's a local socket with no network port, off by default, and each new adapter has to be allowed before its sessions appear. On Windows, the Adapter API listens on a loopback address instead.
The setup for each agent is in the guides: Codex, Claude Code and remote servers.