YOUR AGENTS. YOUR MACHINE. ANYWHERE.

Manage your coding
agents remotely.

Desktop or phone. Chat, talk, point, or tap.
See what your agents are doing and step in when they need you.

Claude Code · Codex · Gemini CLI · OpenCode · omp

The phone session list: usage gauges above a fleet of agents, most of them running, each with a one-line summaryAn agent's live terminal on the phone: a traced test rerun, its task list, and a reply composerChat on the phone answering what the agents are doing: two panes need you, the rest are running
Watch your agents, read their terminals, and ask about the fleet, from your phone.

GET STARTED

Run it. Tunnel it. Open it.

Run the daemon where your agents live, connect your devices, and open the client.

On your agent host

LINUX / macOS

Keep your tmux sessions running. With uv and tmux installed, start the daemon:

TMUXRC_NO_LLM=1 uvx --from git+https://github.com/querystory/tmux-rc.git tmux-rc

This quick start uses basic status detection without model credentials. Enable model summaries for the richer dashboard; configure Live Mode for chat and voice.

Desktop agent manager: one agent needs attention, with working sessions and subagents below, alongside the live terminal and agent overview
Your fleet in the sidebar. The live terminal and agent overview together.

Current UI, fictional demo fleet. Your sessions stay on your host.

Drive tmux from anywhere.

Every pane, any agent, from your phone or browser: the live terminal, tappable answers, and the keys a phone keyboard lacks. A notification when an agent is waiting on you.

Talk to your fleet.

A plain-English summary of every pane. Ask in chat or by voice, relay an instruction or an image, and hear back as the work moves.

Reboot without losing your fleet.

Sessions, windows, splits and names come back, and each agent resumes its own conversation. One tap.

SEE THE WORK UNDER THE WORK

Your agents’ agents, too.

A busy parent can have several workers underneath it. See their tasks, running state, elapsed time, and reported token counts in the sidebar without opening each terminal.

  • Show or hide subagents across your fleet.
  • Keep sessions compact, or expand their activity cards.
  • Include background agents in activity charts, or count panes only.
Inside the dashboard design
Compact sessions with subagent tasks beneath e2e triage and terraform plan review

MAKE ROOM BEFORE YOU RUN OUT

Keep an eye on your limits.

Running a fleet can use a subscription window fast. Claude and Codex meters show how much you’ve used, when each window resets, and where your current pace is heading.

  • Track separate accounts and their available plan windows.
  • See usage trends and projections.
  • Amber and red warnings flag a tight window; “full in” estimates time to exhaustion.

Projections estimate your current pace; they don’t guarantee how much work remains.

How usage tracking works
Claude and Codex plan meters with usage percentages, trend lines, reset times, and a red full-in warning

KEEP YOUR FLEET MOVING

See activity over time.

The dashboard shows how many panes and background agents are working, idle, compacting, waiting, or asking for you. Set a running-agent goal and compare it with the moving average.

  • Explore a day, three days, a week, or a month of history.
  • Compare activity by tmux session or agent tool.
  • Filter the population and zoom into a stretch of work.

Activity counts show agent states, not token throughput or CPU utilization.

How activity history works
Activity dashboard with stacked state history, a moving average, a goal line, and charts grouped by session

A MAP OF YOUR WHOLE FLEET

Find every pane at a glance.

The Sessions card gives each tmux session a card of its own: how many of its panes are running, its activity over the past week, and a tile for every pane with its agent and title. A ring marks each pane that’s working, so you can spot what’s moving and what needs you across a large fleet.

  • See each session’s running count, and who needs you, in its header.
  • Compare sessions’ activity on one shared scale.
  • Choose a pane’s tile to open its live terminal and overview.
Explore the docs
Sessions card with one card per fictional tmux session, each showing its running count, a week of activity, and a tile for every pane with its agent icon and title

TALK, THEN KEEP GOING

A conversation with your fleet.

Use text chat or an active voice session from desktop or phone. Ask what your agents are doing, relay an instruction, and hear a follow-up when the work you directed changes.

  • “Which agents need me?” — get a fleet update.
  • “Show me e2e triage.” — get an Open button.
  • “Tell it to rerun with tracing.” — send an instruction.
  • “Press Escape in that pane.” — send a control key.
  • “Resume the checkout session.” — find and resume earlier work when session history is installed.

Chat offers pane-changing actions for approval. Voice follows your spoken instructions and reports back; routine fleet updates stay quiet.

Voice and chat setup
Live Mode conversation delivering an instruction and following up on the checkout rerun

AFTER A REBOOT

Your whole fleet, back in one tap.

A reboot takes every tmux session with it. tmux-rc records the layout once a minute and which conversation each agent holds, then offers the lost workspace back: every session, window and split where it was, each agent resumed into its own conversation on the account it ran on.

  • Recently active agents start ticked; long-idle agents and plain shells are yours to add.
  • An agent already running elsewhere is greyed out, with the reason.
  • Nothing comes back until you tap Restore, and Start fresh drops the offer.
How session restore works
The Restore view after a reboot: two sessions of agents with their conversations' titles, most ticked, a long-idle one unticked and one already running greyed out

GO DEEPER

The docs live here, too.

Setup, remote access, architecture, and the decisions behind the project.

Browse documentation