Summary
Rex, the terminal from Ghostty's creator: persistent sessions, a scriptable CLI, and one command that teaches your coding agents to use it
The idea: Rex is a terminal and a multiplexer in one. A background server owns your shells and processes, and the app is just a client, so closing the app does not kill your coding agents. Its CLI can split panes, send keystrokes, capture output and wait for a command to finish, and a one-time setup command teaches your agents to use all of that. It is an invite-only beta, so this page reports what the video shows.
"Ghostty's creator made an Agent GUI & it's quite good!" by AICodeKing — Watch on YouTube → Rex is the first product of Superlogical, the company Mitchell Hashimoto announced in July 2026 (announcement). The commands below are as shown in the video: the beta has no public documentation we could check, so none is confirmed against official docs, and the captions' spellings of a few subcommands are uncertain.
How it is built
- Server and client. A background server owns all shells and processes; the app connects to it. Quit the app and your programs keep running; reopen and it reattaches.
- Vocabulary the CLI uses. Server, then sessions (roughly projects), then windows (what you would call tabs), then blocks (panes; for now a block is just a terminal, not Warp-style command blocks).
- Engine. It uses libghostty, the MIT-licensed library behind Ghostty's rendering and terminal emulation. Ghostty itself stays a nonprofit project.
- Access. Beta, invite-only, macOS only for now (the server also exists for Linux and Windows); the Mac app installs as "Rex beta", version 0.1.0 in the video. Free, no account needed.
Config
- The config is a Lua file; the video gives its path as
~/.config/rex/init.lua(the captions read "gh.config/rex/init.lua") and says it was created already, with a note that it checked for Herdr and Ghostty settings. There is no real Ghostty config import. - Bind keys with
rex.bindin that file, including tmux-style chords such as Ctrl-B then C. - After editing run
rex config checkto validate andrex config reloadto apply; it does not watch the file, so the reload is manual. - The command palette is Command-Shift-P; about 40 themes are built in, and Ghostty and iTerm colour schemes can be imported as themes.
The CLI, as shown in the video
rex ls # list sessions
rex new <name> # create a session
rex split ... -- <command> # open a new pane beside the current one (split direction and ratio flags)
rex send <text> # type text into any terminal
rex send-key <key> # press keys such as enter (captions: "rex send dash key")
rex capture # print a pane's screen and full scrollback (--format=html keeps colours)
rex run --wait <command> # open in a new tab, wait, return the exit code
rex events --json # stream everything that happens on the server
rex do # run actions or Lua scripts
Almost everything takes --json, so it is easy to script. The video ran a command that exits with 3 under rex run --wait and got "exit status three" back, which is the useful part: a terminal pane behaves like a job a script can wait on. A split took about a tenth of a second.
Agents: status reporting and the skill
- Rex has no built-in AI assistant. Instead a small protocol the creator wrote, OSC 7501, lets a program tell the terminal whether it is idle, working, done, blocked or errored, and if blocked, whether it is waiting for a permission, a question or a login. The video says Claude Code already reports this, so Rex can show which sessions need you. Read the state yourself with
rex eventsorrex block call program status(as heard). - Run
rex skill setuponce. It installs a skill into your agents plus a start hook for the ones that support hooks. Rex supports Claude Code, Codex, OpenCode and Pi.rex skill statusshowed Codex, OpenCode and Pi set up on the presenter's machine and one Claude Code profile still missing it. - After that the agent knows which Rex session and pane it is in, and can open a diff in a new tab, start a dev server in a split, run your tests and read the result back through the CLI. Telling it "open the tests in a pane below" is enough.
- Remote:
rex server tailscale onturns on the built-in Tailscale support so other devices on your tailnet can reach your sessions. It is off by default, local-only until enabled, and needs Rex at both ends, so it does not replace SSH everywhere. - Rex ships its own terminal type,
xterm-rex. The presenter had to run a terminfo setup command (captions: "rex term info setup") before programs saw it; until then they see a plain xterm-256color.
Caveats
- Beta software: commands can change and things can break. Pricing and licence were not stated (the video says "always free" comes from one source and is unofficial; it is not clear Rex itself will be open source).
- tmux users:
.tmux.confis not ported, there is no built-in copy mode yet, and some tmux options are missing. - Remote hosts added from the CLI did not show in the app yet, and a reboot still kills the processes, so one reviewer's Claude sessions did not survive a restart.
- The presenter's verdict: worth installing next to Ghostty for agent sessions if you can get an invite, not worth moving everything over yet.





