# CLI Reference The `bento` CLI manages the daemon lifecycle and provides operational visibility. | Section | Commands | |---------|----------| | [Setup](/cli/setup) | `init`, `update`, `setup gh` | | [Lifecycle](/cli/lifecycle) | `daemon start/stop/restart/reload/install/uninstall`, `serve` | | [Sandbox Image](/cli/image) | `image pull` | | [Observability](/cli/observability) | `daemon status`, `daemon logs`, `trace`, `queue status/resume/reconcile/purge`, `ps`, `invocation list/status/show/logs` | | [Diagnostics](/cli/diagnostics) | `doctor`, `probe` | | [Triggers](/cli/triggers) | `trigger list/fire/inspect/replay/schedule` | | [Workbench](/cli/workbench) | `workbench open/pause/destroy/remove/sweep/diff` | | [Auth](/cli/auth) | `auth setup`, `auth login`, `token`, `connect github`, `connections list/remove` | | [Knowledge](/cli/knowledge) | `ask`, `knowledge-base` (`kb`) | ## Daemon Endpoint Commands that talk to the daemon resolve its address automatically: the `BENTO_DAEMON_URL` env var (full origin, e.g. for a remote daemon) wins, then `BENTO_PORT`, then `port:` in the project's `.bento/daemon.yaml` (legacy `webhooks.port` still honored), falling back to `7890`.