Документация Баунс

The bounc command groups, authentication, global flags, machine-readable output, and exit codes.

The bounc CLI covers most of what the web app does: issues and projects, agents and skills, teams, autopilots, workflows, Assets tables, runtimes, and attachments. This page is the map of command groups and what applies globally; the exhaustive list of subcommands and flags is always a --help away.

Installing

The CLI is a single self-contained binary. Download it from the web app's /download page (it picks the build for your OS), make it executable, and put it on your PATH:

chmod +x bounc          # on Windows the download is bounc.exe
./bounc login

To update, run bounc self-update: it checks the release channel and replaces the binary in place.

Authentication

bounc login                     # browser sign-in
bounc login --token bnp_…       # no browser: an existing personal token
bounc auth status               # who am I, which workspace, which profile
bounc auth logout               # clear the local token

bounc login stores a personal access token (bnp_) in the local profile, and every command authenticates with it from then on. For CI and headless machines, issue a token under Settings → Tokens and pass it with --token.

BOUNC_TOKEN and BOUNC_WORKSPACE_ID in the environment take precedence over the saved login. An agent does not use your CLI: inside its turn it works through Bounc's own tools with the turn's pass, and its actions are attributed to it. See Tokens.

Multiple environments live in profiles: bounc profile switches them, bounc config reads and writes local settings, and bounc workspace switch changes the default workspace for commands.

Work and data

Command	What's inside
`bounc issue`	`create` `list` `show` `update` `status` `assign` `move` `search` `delete`, plus the `comment`, `label`, `subscriber`, `metadata`, `children`, `runs`, `run-messages` groups
`bounc project`	CRUD, status, search; the `resources` group
`bounc initiative`	CRUD and project linking
`bounc label`	CRUD for workspace labels
`bounc dataset`	Assets tables: `create` `list` `show` `update` `import` `archive` `restore` `delete`, plus the `field`, `record`, `view` groups
`bounc diagram`	Assets diagrams: `create` `list` `show` `update` `home` `archive` `restore` `delete`; `--mermaid <file>` also takes `-` (stdin)
`bounc attachment`	`list` `get` `data` `upload` `delete` for issue and comment attachments

list commands print short, copy-ready identifiers: issue keys like ACME-123 and short prefixes for everything else. Every later command accepts either the short identifier or the full UUID.

Agents and automation

Command	What's inside
`bounc agent`	`create` `create-from-template` `list` `show` `update` `archive` `restore` `templates` `template`, plus the `skills` group
`bounc skill`	`create` `list` `show` `update` `delete` `search` `import` `builtins`, plus the `files` group
`bounc team`	`create` `list` `show` `update` `members` `briefing` `archive` `restore`
`bounc autopilot`	`create` `list` `show` `update` `delete` `trigger`, plus the `triggers`, `runs`, `deliveries` groups
`bounc workflow`	`create` `list` `show` `nodes` `export` `apply` `diff` `set-draft` `validate` `plan` `publish` `start` `cancel` `rerun`

Infrastructure and profile

Command	What's inside
`bounc runtime`	`list` `show` `update` `delete` `usage`
`bounc daemon`	`connect` `start` `stop` `restart` `status` `logs` for the local daemon; `connect` links this computer to a workspace after `bounc login`
`bounc workspace`	`list` `get` `switch`, plus the `member` group
`bounc user`	Your own profile
`bounc schema`	Data-model introspection over the OpenAPI spec: `list` `describe` `search`
`bounc version` · `bounc self-update`	Version, and updating the binary

Global flags

These apply to every command:

Flag	Purpose
`--output <text\|json>`	Output format; `json` is machine-readable
`--fields <paths>`	With `--output json`: project the payload onto dot-paths — `id,title,assignee.name`
`--dry-run`	Validate the input and resolve references, then report the call instead of sending it
`--debug`	Print the full error chain (same as `BOUNC_DEBUG`)

The HTTP timeout comes from BOUNC_HTTP_TIMEOUT (45s, 2m; default 30s).

Exit codes

Code	Meaning
`0`	Success
`1`	Generic failure
`2`	Network
`3`	Authentication
`4`	Not found
`5`	Validation

That is what makes the CLI scriptable: 2 and 3 are worth retrying or fixing in the environment, while 4 and 5 mean the request itself is wrong.

The full flag list

Every command and subcommand takes --help, and the root help additionally prints the global flags, the exit codes, and the auth model:

bounc --help
bounc issue create --help
bounc dataset record patch --help

Tokens — personal, daemon, and task tokens.
API — the same contract over HTTP.
Computers and machines — what the daemon group does.

CLI reference