hob CLI
Drive hob from the command line — agents use it to open panes, message each other, and link their work.
Terminals inside hob (and agents running in them) get a hob CLI that controls the surface itself. It's how an agent opens a file for you to review, hands work to another agent, or creates a commit linked back to its conversation.
Commands
| Command | What it does |
|---|---|
hob list | Inspect panels, panes, workspaces, and the caller's own pane context |
hob open | Open files (render panes), agent/terminal/web panes, tool panels, or workspaces |
hob close | Close panels, panes, or workspaces |
hob input | Type into another pane — set a draft or submit a message/command |
hob terminal | Inspect another terminal's command status, exit code, and output |
hob commit | git commit, linked to the agent conversation that made it |
hob issue | Create, comment, close, complete, or delete local and remote issues |
hob pr / hob mr | Create, comment on, or close pull requests |
hob app | Updates, relaunch, license |
Add --json for machine-readable output. Run hob <command> --help for details.
Agents driving hob
Inside hob, every pane's environment carries its identity (HOB_PANE_ID) and project context — so agents can act on the UI:
# Show the user a file in a render pane
hob open file docs/api-spec.md
# Spawn a second agent and hand it a task
hob open pane agent --backend claude
hob input pane agent_abc123 "Review the diff in ./src" --submitMessages submitted to another agent pane arrive attributed (Message from <pane-id>:), and the peer's final response is delivered back automatically — agents can collaborate without polling.
Linked commits
hob commit forwards everything to git commit, but links the resulting commit to the agent turn that created it:
hob commit -m "fix parser edge case"
hob commit --link-pane agent_abc123 -m "implement planned change"The link shows up in Activity — every commit traces back to the conversation that produced it, including other panes that contributed via --link-pane.