Benchday
▸ benchday · the command-line tool

One command for every agent on every machine.

Benchday CLI shows the coding agents and terminal sessions running across your machines — so you can see what’s running, find what needs you, read output, search past work, and diagnose connection problems, all from one terminal. The Benchday app is your visual control room; the CLI is the same view from a shell or a script.

$curl -fsSL https://benchday.zztech.io/cli.sh | sh

Installs to ~/.local/bin/benchday — per-user, no sudo. Read the docs · already run the background service? One approval covers both.

See everything, from one terminal.

Point the CLI at a machine, or at a session id like %3. You get plain tables in your terminal, and JSON when you pipe it. Today’s commands are read-only.

benchday status

List your machines, whether they’re connected, how many agents are running, and which are waiting on you.

benchday panes -m <machine>

List the terminal sessions Benchday found on one machine.

benchday pane %3

Show one session’s status, folder, summary, and recent output.

benchday pane %3 --content

Show a session’s full captured terminal output.

benchday tail %3

Follow a session’s output as it appears.

benchday agents --needs-you

List the agents that have stopped to ask for your input.

benchday search "rerank report"

Search agents and saved work across all your machines — by words or meaning.

benchday context %3

Show the recent conversation and conclusions from the agent in a session.

benchday work

Find recent work you can resume — with its machine, folder, and command.

benchday doctor -m boxB

Explain why a machine won’t connect, and what to check.

Why not just SSH and tmux?

SSH and tmux are great once you know which machine and which session to open. Benchday gives you one searchable view across all of them — what’s running, what needs you, what an agent just did, and where to pick work back up. It works alongside SSH and tmux; it doesn’t replace them.

Sign in once. Revoke the CLI anytime.

Each machine runs a small background service; the CLI signs in as you and reads the machines your account can access. Approving both together saves a step — and you can revoke either one later.

Background service

connects one machine

Runs on the machine and gives Benchday access to its sessions.

  • Limited to that machine
  • Runs through systemd or launchd
  • Remove its access by unpairing the machine

Command-line tool

uses your account access

Runs as you and reads the machines you can access — it doesn’t need the background service on the same computer.

  • Reaches your approved machines
  • Installs in ~/.local/bin, no sudo
  • Revoke this CLI without disconnecting any machine

Approve once on your phone → the machine and this CLI are authorized together.

Let one agent read another’s work.

An agent on one machine can look up what your other agents are doing — with a command, not magic.

Add --json to any command for machine-readable output with a versioned schema and documented exit codes — no interactive prompts. Or run an MCP server so compatible agents can call Benchday as a tool, with named actions for reading a session, getting agent context, and searching work.

Install the CLI on a machine and any agent there can use it — no separate integration per agent.

$benchday search "auth refactor" --json
→ pane %7 on zz-tower0
$benchday context %7 --json
→ reads the other agent’s turns
$benchday mcp # stdio MCP server

Put it on a machine in one line.

No background service needed on this machine. It drops into your home directory, signs in with one approval on your phone, and reads every machine your account can access.

$curl -fsSL https://benchday.zztech.io/cli.sh | sh
Needs a Benchday account and at least one machine running the background service (the machine you install on doesn’t). Sessions are found through tmux. · Full reference