CLI reference

overhand start

run Overhand in the background (at every login) and open it in your browser

overhand stop

stop it and don't start it at login

overhand status

whether it's running: port, version, last heartbeat, agents at work, free disk

overhand logs

the daemon's log (-f keeps following it)

overhand update

update to the latest release

overhand doctor

check what Overhand needs on this machine

overhand version

print the version

overhand answer <lead> "<text>"

answer a lead's open question (--default: go with the default it gave)

overhand daemon

run in the foreground (what the login service runs)

overhand plan | work | inbox | ui

one step by hand

overhand cleanup plan | run | auto

one disk cleanup pass (Overhand's own cleanup runs these)

overhand quiet 3h | 90m | off

"I need my laptop": agents start no browsers, suites, builds, simulators or dev servers

overhand connect [<folder>]

your own Claude Code sessions in that project join the control room and follow the house rules (writes .claude/settings.local.json; --global: every project, asks first)

overhand disconnect [<folder>]

undo it

overhand ask <session> "<request>" [--by HH:MM]

a typed request, handed to that session at its next tool call

overhand ack <id> [done | refuse "why"]

answer a request handed to this session

This list is what overhand help prints. Every command exits non-zero when it fails, so scripts can rely on it. Two more, overhand guard and overhand heavy, are run by agents' hooks, never by you.