marver

A TUI workspace for AI agent sessions — tmux orchestration, git worktree management, and repo control in one place.

Start a task, describe it, and marver opens a tmux session with an agent already working in its own worktree. Inspired by k9s, cmux, and Warp.

Status: early development. Every subsystem exists and the loop closes — describe a task, an agent runs it, review the diff, commit — but nothing has been used in anger yet. The published crate is still a name reservation.

marver                  open the interface, starting a daemon if none is running
marver status           report whether a daemon is running, and what it holds
marver restart          stop the running daemon and start this version
marver upgrade          install the newest published marver
marver daemon           run the scheduler and hook receiver in the foreground
marver scan [root]      list the git repos it can see
marver --version        print the version (-v, -V)
marver --help           print usage (-h)

Every command takes --data-dir for where the database, socket, and log live, --scan-root for the directory searched for repos, and --cap for how many agents may run at once. The interface and the daemon find each other through those paths, so a --data-dir given to one must be given to the other.

Just run marver. If no daemon is listening it starts one, detached, the way a tmux client starts the server it needs — and that daemon keeps running after you close the interface. It owns the queue: it creates a worktree per repo, opens a tmux session, starts Claude Code with hooks pointing back at itself, and notifies you when a task finishes or gets stuck. Its output goes to daemon.log beside the database.

Run marver daemon yourself to watch it in the foreground or to put it under a supervisor. Starting a second one is refused rather than allowed to displace the first.

Upgrading

marver upgrade              # cargo install marver --force
marver upgrade --restart    # and swap the daemon too

marver upgrade drives cargo, because that is how the crate is distributed. If you installed marver some other way it says so rather than guessing, and you upgrade it however you installed it.

Installing a new marver does not replace a daemon that is already running: it keeps executing the old binary, and since it still holds the socket, nothing starts a replacement. This is deliberate — that daemon is supervising live agents, and restarting it underneath them would fail every task it was watching.

marver status reports both versions and says so when they differ, and marver restart does the swap when you are ready:

marver restart

It refuses while any task is running or blocked, because that is the one thing a restart can cost. marver hook always exits 0 — marver being down must never interfere with an agent — so a hook arriving while nothing is listening is simply lost, and the task is left running behind an agent that has already finished. Wait for those tasks to reach awaiting-review, or accept it with marver restart --force.

Nothing restarts the daemon on your behalf. It is supervising live agents, and the moment to interrupt that belongs to whoever knows what they are in the middle of. Agents already running in tmux survive a restart either way.

See ARCHITECTURE.md for the design and the reasoning behind it.

Requirements

tmux 3.x, git, and Claude Code.

Name

A marver is the polished steel table a glassblower rolls hot glass across — shaping the piece and controlling its temperature between trips to the furnace. It is the surface where work takes form.

License

MIT OR Apache-2.0, at your option.