<!--
Sitemap:
- [Installation](/installation): Install the Bento daemon on macOS or Linux, then write your first pipeline to run a coding agent on a GitHub, Linear, or schedule event.
- [Upgrading](/upgrading): Version-specific steps for upgrading an existing Bento install.
- [Concepts](/concepts)
- [Build your first pipeline](/tutorials/pipeline-args)
- [Target a specific issue or PR from a URL](/tutorials/url-targeting)
- [Keep state across runs](/tutorials/pipeline-state)
- [Fire a pipeline on a schedule or on demand](/tutorials/schedule-and-fire)
- [Deploy a box to Railway](/tutorials/deploy-to-railway)
- [Operate a hosted daemon](/tutorials/operate-a-hosted-daemon)
- [Configuration](/configuration): Configure the Bento daemon with daemon.yaml: service name, port, webhooks, sandboxes, knowledge base, and environment variables.
- [Members](/members)
- [Knowledge base](/knowledge-base/)
- [Method and delivery](/knowledge-base/modes): Choose how Bento retrieves knowledge (BM25, vector, or hybrid) and how it delivers that knowledge to a coding agent.
- [Config](/knowledge-base/config)
- [MCP](/knowledge-base/mcp): Give coding agents your team knowledge over MCP. The Bento daemon serves an ask_knowledge search tool and per-file resources.
- [Pipeline configuration reference](/pipelines/config): Reference for Bento pipeline YAML: triggers, agents, skills, instructions, filters, sandboxes, structured results, and outputs.
- [Filters](/pipelines/filters): Filter GitHub, Linear, and webhook events by repository, label, and other fields so only the right Bento pipelines run.
- [Triggers](/triggers/): Start a Bento pipeline from a GitHub, Linear, webhook, schedule, or manual trigger. Compare the trigger types and when each one fires.
- [GitHub trigger](/triggers/github): Run a coding agent on GitHub pull request, issue, and other webhook events. Configure HMAC verification and event patterns.
- [Linear trigger](/triggers/linear): Run a coding agent on Linear issue and comment events. Configure the Linear webhook, signature verification, and Hookdeck relay.
- [Webhook trigger](/triggers/webhook): Fire a Bento pipeline from any HTTP POST to /webhooks/{name}, with bearer-token authentication declared in daemon.yaml.
- [Schedule trigger](/triggers/schedule)
- [Manual trigger](/triggers/manual): Fire any Bento pipeline on demand with bento trigger fire, and pass typed inputs to a pipeline that runs only on request.
- [Traces](/pipelines/traces)
- [Slack](/integrations/slack)
- [Public access](/public-access): Expose the Bento daemon to GitHub webhooks through a Cloudflare Quick Tunnel or Tailscale Funnel, and compare the two options.
- [Context engineering](/context-engineering): Assemble each coding agent prompt from personas, policies, skills, and pipeline instructions. Learn which file each instruction belongs in.
- [Best practices](/best-practices)
- [Troubleshooting](/troubleshooting)
- [Architecture](/architecture/vision)
- [Workspaces](/workspaces)
- [Authentication](/authentication)
- [Identity](/identity)
- [Security](/security)
- [References](/references)
- [Changelog](/changelog): Bento release history.
- [CLI reference](/cli/)
- [Setup](/cli/setup)
- [Secrets](/cli/secrets)
- [Lifecycle](/cli/lifecycle)
- [Sandbox image](/cli/image)
- [Sandboxes](/cli/sandbox)
- [Observability](/cli/observability)
- [Diagnostics](/cli/diagnostics)
- [Triggers](/cli/triggers)
- [Workbench](/cli/workbench)
- [Auth](/cli/auth)
- [Knowledge](/cli/knowledge)
- [Evals](/cli/evals)
- [Bento docs: run coding agents from version-controlled pipelines](/index): Bento runs coding agents from pipelines you keep in your repository. Declare the trigger, sandbox, skill, and guardrails in YAML.
- [Runtime wrapper](/architecture/runtime-wrapper)
- [Skill evolve](/architecture/skill-evolve)
-->

# CLI reference

The `bento` CLI manages the daemon lifecycle and provides operational visibility.

| Section | Commands |
|---------|----------|
| [Setup](/cli/setup) | `init`, `update`, `setup gh`, `setup linear`, `setup webhook`, `setup codex`, `setup claude` |
| [Secrets](/cli/secrets) | `secrets key --generate/--import/--rotate`, `secrets set/list/rm` |
| [Lifecycle](/cli/lifecycle) | `daemon start/stop/restart/install/uninstall`, `serve` |
| [Sandbox image](/cli/image) | `image pull` |
| [Sandbox](/cli/sandbox) | `sandbox setup/status/update/destroy`, `sandbox snapshot build/create/list/retry` |
| [Observability](/cli/observability) | `daemon status`, `daemon logs`, `trace`, `graph list/show/node`, `queue status/resume/reconcile/purge`, `ps`, `invocation list/status/show/get-run/logs` |
| [Diagnostics](/cli/diagnostics) | `config validate`, `doctor`, `probe` |
| [Triggers](/cli/triggers) | `trigger list/stats/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`) |
| [Evals](/cli/evals) | `evals list/accept/reject/scorecard` |

## Daemon endpoint

Commands resolve the daemon address in this order:

1. `BENTO_DAEMON_URL`, which accepts a full origin for a local or remote daemon.
2. `BENTO_PORT`.
3. `port:` in the project's `.bento/daemon.yaml`, including support for the legacy `webhooks.port`.
4. Port `7890`.
