14 sessions · 4 groups · 3 need you

All your agents. One map.

Ratatosk is a terminal workspace for people who run a lot of AI agents. Every Codex, Claude, and shell session gets a sprite and a live status on one spatial Command Map, so you can tell who’s working, who’s done, and who’s stuck without opening a single tab. Click a session and you’re in a real terminal. The same map opens on your phone.

Current stable release Ratatosk for Mac Mac control station · Apple silicon · signed & notarized
Remote execution node Ratatosk for Ubuntu Ubuntu 24.04 · x86_64 · headless target
Run on the Ubuntu machine (umask 077 && installer="$(mktemp)" && trap 'rm -f "$installer"' EXIT && curl --proto '=https' --proto-redir '=https' --tlsv1.2 -fsSL https://getratatosk.com/install.sh -o "$installer" && sudo bash "$installer") View the verified installer →

local-first · macOS + web + phone · your CLIs, unchanged

01 · features

The important stuff.

Accounts, phone, lid, survival, pings. Everything else on this page is detail.

Hit a limit, switch accounts.

Keep every Codex and Claude account you own signed in at once, each with its own label, and choose which account each tab runs under. When one account hits its ceiling mid-run, point that tab at a different account and keep working. Every login stays live, so the switch is one click instead of another trip through a provider login page.

Steer it from your phone

Your workspace gets its own rata.sh URL with real authentication in front of it. From your phone you can open any session, read what the agent wrote, and answer the prompt it’s stuck on. Add it to your home screen and it opens like a native app.

The lid is not an off switch

Ratatosk holds your MacBook awake through a powerSaveBlocker and its own pmset management, so closing the lid turns off the screen and nothing else. Agents keep working while the laptop sits in your bag, and you can retire the caffeinate terminal.

Permadeath: off

Sessions live in tmux, outside the app process. You can quit Ratatosk, restart its server, or reboot the whole UI, and when you come back every terminal reattaches with its scrollback exactly where you left it.

Stop checking. Get pinged.

When an agent finishes or needs a decision, you get a desktop notification, and the Command Map keeps an unread ring on the session until you look. Nothing an agent finishes at 4pm waits until you happen to scroll past it.

02 · command map

The whole board, in one glance.

The Command Map shows every project group and every agent session in one place. Amber means working, green means ready, and a ringed marker means an agent finished while you were looking elsewhere. The ring stays until you’ve seen it.

Sessions live in project groups. The left rail carries a readiness count per project, each group has its own tab strip, and web tabs sit beside terminal tabs, so the docs, the preview, and the PR stay next to the agent that produced them.

Busy / Ready / Unread

Adapters watch Codex, Claude, and shell activity and turn it into a status you can read from across the room. When an adapter guesses wrong, set the state by hand.

Groups, not piles

The rail gives each project one line and a readiness count. Open a group when you want the detail, and collapse it when you don’t.

Web tabs in the group

Web tabs open in the same group and tab strip as the agents that made them, so the preview and the PR never drift off into a second window.

03 · the party

Your agents have faces. That’s the point.

Ratatoskr is the squirrel in Norse myth who runs the world tree, carrying messages between the eagle at the top and the serpent at the roots. If your day is spent relaying context between agent terminals, you know the job. Ratatosk puts the run on one map and gives every runner a face: each agent shows up as a pixel sprite you can recognize from across the room.

The sprites do real work. Fourteen identical tabs take effort to scan; fourteen characters with faces and status lights read like a room full of coworkers. It also makes running agents all day genuinely fun, which turns out to matter when you do it for ten hours.

04 · rata.sh

Step away. Stay in command.

Your workspace gets a personal rata.sh URL with real authentication and server-side entitlements in front of it, so leaving it reachable is safe. On your phone it’s the same board. Open the stuck session, read what the agent wrote, and send the answer that’s been blocking a merge for twenty minutes.

Add it to your home screen and it opens like an app. An agent blocked on a yes/no shouldn’t cost you a walk back to your desk.

05 · flight log

The flight log.

A day of running agents produces a record most tools throw away. Ratatosk Cloud is turning that record into something you own: stats on how you actually work with your agents, daily and weekly badges worth collecting, and a personality profile computed from your own prompts. It can tell when you intervene, what you delegate, and which agent you trust with which work.

This part is still in development in Ratatosk Cloud. Early access means you watch it arrive.

06 · execution nodes

One cockpit. Any machine.

The workspace and the machine doing the work are separate things. Point Ratatosk at your Mac and everything runs locally on your own hardware. Point it at an isolated cloud node and the same repos, agents, and terminals run there instead, on the same map, in the same groups.

Put your agents on the map.

Run the control station on your Mac, then add Ubuntu 24.04 machines as remote execution nodes. One account keeps every machine on the same map.

Need help or web access? support@getratatosk.com