Superlogical designed its multiplexer for swarms of software users. The humans got the calmest terminal I've used, with a few beta-shaped gaps.
Sam Zoloth · A first look at Rex, in beta
Fig. 1 · Hover a partFig. 1 · Tap a part
On a normal afternoon I have a few dozen coding agents running across my projects. Most of the time none of them need me. Then one does, and the old question comes back. Which tab?
In Rex, I press cmd+j. It jumps straight to the agent that's blocked on me, then the one that errored, then the one that finished. Press it again and it cycles. The shortcut is about forty lines of Lua in my config, written against an API Rex ships for this kind of thing.
Rex is a terminal multiplexer from Superlogical, the company Mitchell Hashimoto started after Ghostty and HashiCorp. A multiplexer keeps your terminal sessions running on a server, so you can close the window, reconnect from another Mac and find everything where you left it. tmux and plenty of other tools do that. Rex is different because Superlogical designed it for agents as much as people, and building for swarms of agents is what makes it feel calm for one person.
I switched a few weeks ago from Ghostty and the desktop apps I'd been running agents in. Along the way I took Rex apart to see how it works. I read the app bundle, the docs, four of Hashimoto's talks and demos, and every public post from the team I could find. I turned that method into a Claude Code skill called /teardown, and you can download it at the end.
01 · ScaleWho Rex is for: a user that isn't human
Hashimoto has said it plainly. Agents spawn far more terminal sessions than people do, and each one attaches as its own client. So Superlogical designed the server for an absurd load.
If we design for excessive, then the low end will work really great.Mitchell Hashimoto, on Rex's server
My favorite example is what Rex does with idle terminals. After a minute with no output, it writes the terminal's whole state to disk and stops paying for it. When output arrives again, it comes back in a fraction of a millisecond, plus however long the disk takes. Most terminals sit idle most of the day, so most of them cost almost nothing.
Server memory
Live terminalParked to disk
tmux-style server
0
Rex
0
Drag the sliders. Idle terminals park after a pause, which stands in for Rex's 60 seconds. Per-terminal figures are approximate and come from Hashimoto's own benchmark of full terminals (about 4 to 5 MB for tmux, about 400 KB for Rex). I didn't measure them, and a parked terminal is drawn as near zero.
His September talk walks through three kinds of parking. Idle terminals go to disk, quiet ones give up their dedicated threads, and idle clients free their buffers. You never see any of it. Even with a few dozen agents running, Rex hasn't felt heavy yet.
02 · ArchitectureAttaching: Rex forwards bytes instead of redrawing screens
Hashimoto's July video explains the design choice underneath all of this. A traditional multiplexer like tmux sits between your terminal and your shell, reads everything, and redraws its own version of the screen. That works, but it means everything gets parsed twice, and every attached client shares one view.
Rex keeps one authoritative terminal on the server. When a client connects, the server sends a compact snapshot of the screen, then forwards the raw output stream to every client, a lot like SSH. Each client runs its own full terminal emulator, built on the same libghostty library that powers Ghostty. Scrollback streams in afterward, newest lines first.
Client A · laptop
Client B · desktop
tmux-style: scroll either client and watch the other.
Scroll one client, then flip the switch. In the tmux model every client shares one view, the complaint Hashimoto names in his video. In Rex each client owns its own viewport. A late client draws from a snapshot first, then fills in history. The build log is made up for this demo.
The payoff is small and constant. Scrolling, selection and splits feel native because they are native. And if you open the same session on two Macs, each one scrolls on its own.
03 · StatusRex knows who's waiting on you
Superlogical published a small open protocol called OSC 7501. Any program can use it to tell the terminal what it's doing. The status I care about most is "waiting on you." Rex tracks each program's status, shows it in an Activity sidebar and hands it to scripts. That status is what my cmd+j shortcut reads.
Rex · four agents
Real Rex, recorded on my Mac. Four staged demo agents. Each time one starts waiting on me, the window jumps to it and zooms in, using the same ranking as my shortcut.
Rex · three sessions
margin
claude · marginworking
shell · marginworking
site
codex · siteworking
claude · siteworking
vault
claude · vaultworking
-- my ~/.config/rex/init.lua, trimmed
RANK = blocked 1, error 2, done 3
for every terminal in every session
read its program_status
keep the lowest rank, oldest first
focus_block(best)
Wait a few seconds, then press J or the button. Tabs change state on their own, the way agents do. The ranking matches my config. The real code is about forty lines; this panel is trimmed to the steps that matter.
The spec is restrained. It shares state and leaves the presentation to the terminal. If a report includes a state the terminal doesn't recognize, the terminal ignores the whole report, so a state added later never turns into idle on an older terminal. It also explains why the existing escape codes didn't work, which is more homework than most specs show.
04 · AutomationProgrammable all the way down
Everything you can do in the Rex app, you can do from its command line, and the CLI is a client of the same API. That's what made cmd+j possible. It's also what makes Rex easy for agents to drive.
Rex installs a guide for Claude Code, Codex, OpenCode and Pi. The guide lives inside the Rex binary, so updating Rex also updates what your agents know. The guide has guardrails worth copying, like "Don't send input to your own pane, where the agent is running." That's good advice for an agent and a funny one for a person.
05 · CraftDetails you notice once, then rely on
Permission prompts name the real requester. When a program in a terminal asks for your camera, macOS shows a prompt that says a program running in Rex wants it and Rex itself doesn't use the camera. It's a small courtesy, and it keeps you from blaming the terminal for a request it didn't make.
Themes go further than the terminal. Rex ships 41 of them (I use Cathode Amber, the one every window on this page wears), and each one generates the colors for the window, sidebar and controls from the terminal's own palette. The app always matches what you're looking at.
Rex · six themes
The same session through six of Rex's 41 themes. Every color in the app, not only the terminal, comes from the theme's palette. A real recording with staged demo agents.
Automatic contrast correction checks text at runtime and shifts its color toward the theme so it stays readable, since most terminal programs are designed for dark backgrounds. An optional effect sends a small shine across a selection when you copy it. The About screen has a mascot you can throw.
06 · GapsWhere it falls short
Rex is a beta, and some of the gaps come straight from its good decisions.
You'll want Tailscale. Superlogical runs no cloud and asks for no account, so devices find each other over your Tailscale network. I like that trade. If you don't already use Tailscale, it's one more thing to set up.
Updates end your sessions. Updating restarts the server, and the app's update screen says so plainly. For a tool whose promise is persistence, that stings.
The trust model is coarse for now. Anyone who can connect to a server can do anything on it. The docs say a fuller auth system is planned. Until then, keep servers local or behind Tailscale identity.
No push notifications yet. They'd need cloud infrastructure the team hasn't built.
Mac first. The public beta is Mac only, with iOS by invite. Superlogical says Linux and Windows servers already run, but those clients aren't in the public beta yet.
Beta bugs. For a while my Rex window got stuck floating on top of everything, on every screen.
07 · VerdictUse it if, skip it if
Use Rex if you run agents in your terminal and lose track of which one needs you, you want sessions that survive closing the window or switching Macs, or you already like Ghostty and want that feel with persistence built in.
Skip it for now if you need Linux or Windows clients today, you can't add Tailscale, or you rely on tmux plugins and copy-mode habits that Rex doesn't migrate.
08 · MethodHow I took Rex apart (with agents)
I wanted to know why Rex feels the way it does, so I asked Claude Code to help me take it apart. We went in layers.
We started with the app itself. The bundle shows what it's built from (a Swift Mac app talking to a Go server), the protocols it versions, its themes and every string of interface copy. Then we ran it, watched which processes and sockets it uses, and read the API it describes about itself. Last we read everything public, including the docs, the team's posts, transcripts of four of Hashimoto's talks and demos, the update feed and the Hacker News launch thread.
The pipeline. Each stage feeds the next. A candidate principle had to clear all three tests to stay.
From that we wrote down fifteen decisions. For most we named the alternative the team turned down, and for all of them we noted how sure we were. Then we looked for the few rules underneath them. Six rules explained fourteen of the fifteen decisions.
The agents made mistakes, and the checks caught them. A summarizing model turned two paraphrases into quotes. A research agent leaned on a secondhand summary of a talk. We checked quotes against their sources and transcribed the talk ourselves before trusting it.
The last step was turning lessons into principles I could use elsewhere. A lesson from one product is a guess. So each principle had to pass three tests. It needed a second example from somewhere else, a counterexample showing where it stops working, and one concrete change to my own work. Two candidates turned out to be truisms and had to be rewritten or merged. The counterexample pass also surfaced a principle I'd missed.
I packaged the whole process as a skill for Claude Code called /teardown.
/td
The teardown skillA SKILL.md and a reference of read-only inspection commands for Mac apps, web apps, CLIs and Go binaries.
I left out anything Superlogical hasn't announced. Every claim here traces to the app itself, its docs, or something the team has said in public. Sources: Superlogical's launch page and Oct 5 beta post; Mitchell Hashimoto's Jul 30 architecture video, Sep 2 pre-alpha demo, Sep 2 server memory talk and Sep 8 remote sessions demo; posts from Hashimoto and Alasdair Monk on X; the Rex docs, including the Program Status Protocol spec.