buster7
CLI (b7)

Command reference

What b7 can do, with examples of running agents from a script

Commands

CommandWhat it does
b7 statusA summary of the server and the sessions
b7 sessionsThe list of sessions
b7 new --agent shell|claude|codex [--yolo] [--cmd ...] [--cwd ...] [--name ...]Create a session
b7 kill <id...>Stop sessions (several at once, separated by spaces or commas)
b7 send <id> "text" [--key ctrl-c] [--no-enter]Type into the terminal
b7 resize <id> --cols N --rows NChange the size of the terminal
b7 read <id> [--history N] [--json] [--settle ms]Read the screen (and history) as text
b7 search <id> "text" [--from N] [--backward]Search the screen and the history
b7 chat <id> "text"Send to the chat (with no text, read the history)
b7 projects / b7 project add|rm|pin|orderWork with projects
b7 workspaces <project> / b7 worktree new|rmWork with workspaces
b7 files <session> [path] / b7 file <session> <path> [--dest f]Look at the working directory
b7 dirs [path]Suggest directories (before project add)
b7 server status / b7 server setupCheck or record the connection

b7 send --key accepts enter, tab, esc, up, down, left, right, space, bs, ctrl-c and others.

Example: run an agent and collect the result

B7=server/target/debug/b7

id=$($B7 new --agent codex --yolo --name review | jq -r .session_id)
$B7 send "$id" "Review this diff"
$B7 read "$id" --history 50       # watch the progress
$B7 search "$id" "error"          # search a long output
$B7 kill "$id"

read only looks, so it does not change the size of the terminal. Peeking from the CLI at a session open in the app does not disturb what the app shows.

Example: prepare a project and a workspace

B7=server/target/debug/b7

$B7 dirs ~/src/            # look at the candidates
$B7 project add ~/src/myapp --name myapp
$B7 projects
$B7 worktree new myapp feature-x --branch feature-x
$B7 workspaces myapp       # shows the path that was created
$B7 new --agent claude --cwd <the path above>

On this page