HexoKit

hexokit · v3.21.1

Your tmux, in the browser and on your phone.

Cockpit for the agent era.

A remote console for the machine you actually work on. Every tmux session and pane is a live terminal, at your desk or on the couch. Nothing to configure, no database.

Install Read the docs GitHub

The HexoKit desktop app: a sidebar of tmux sessions beside two live agent panes running a build and a review.

HexoKit on an iPhone: the same session sidebar, with boards, servers and per-pane status.

install

One line, then you are in

curl -fsSL hexokit.com/install | sh

brew install sahil87/tap/hexokit

Installs shll and HexoKit. Nothing else. The six companions are one more command away.

Needs tmux 3.4 or newer. Run rk doctor if anything looks wrong.

what it does

Everything is a live terminal

A live tmux pane on a phone, with an on-screen key bar for tab, ctrl and arrow keys.

Every pane, on every device

Tap a session on your phone and you are in the shell you left at your desk. Over Tailscale from anywhere.

→ docs

The lower session sidebar with per-window status dots beside an agent pane; the status bar reads agt idle 43s.

Waiting, working, idle — at a glance

Every window running an agent says which. Claude Code, Codex, Gemini CLI and Copilot CLI report in after a one-time setup.

→ docs

The fleet view: the server grid and a sidebar list of riff worktree windows, each with its status dot.

One command per parallel agent

rk riff gives an agent its own git worktree and tmux window. rk riff -N 3 starts three.

→ docs

A HexoKit board: two pinned agent panes from the same server rendered side by side.

Watch three agents and the dev server at once

Pin panes from any machine into a board and they sit side by side. One dot per window tells you where it stands.

→ docs

The operator popover reporting on tracked changes and asking whether to start the next wave of work.

Work that starts without you

rk cron wakes an agent on a schedule. rk operator keeps watch and pings your phone.

→ docs

A HexoKit window split between a terminal pane and a web tile rendering a formatted change plan.

A window is not only a terminal

Open an editor with rk code, a web page your agent writes with rk present, or the machine’s own screen.

→ docs

The operator console slid down as a drawer over a dashboard tab, with the tab’s Ask box above it and the operator’s transcript inside.

The operator drops in from any tab

One shortcut and the operator’s console slides down over whatever you are looking at, Quake-style. Ask, get an answer, send it back up. Your pane never moves.

→ docs

the difference

Use any agent, untouched

Mostly what runs in those panes is coding agents, several at once. But HexoKit never wraps them. A pane is just as happily a build, a REPL, an ssh session, htop. The agent is one of the things you run, not the thing HexoKit is.

It is

A console for your tmux, built for the phone. Any agent, no database, nothing to keep in sync.

It isn’t

An agent wrapper. It reads no agent’s output and speaks no agent’s protocol. When the agent tools change again, this layer stays put.

the toolkit

The HexoKit toolkit

HexoKit is the cockpit. Six small tools sit on its six edges, and shll installs them all.

fab-kit wt idea tu hop desktop

fab-kit — a plan before any agent writes code.
wt — throwaway git worktrees, one per change.
idea — catch an idea without breaking flow.
tu — what your AI coding sessions cost.
hop — jump to any of your repos.
desktop — the Mac app around the dashboard.

→ See the whole toolkit

desktop

The desktop app

The dashboard in a window of its own, with the same keyboard shortcuts you are used to in a terminal — none of them swallowed by a browser tab. It connects to this Mac, to another over SSH, or to any URL, and it starts and stops nothing on its own. Your tmux sessions outlive it.

rk desktop install
rk desktop update

Install from the CLI. A downloaded DMG trips Gatekeeper; this one does not.

→ Install guide