<!--
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)
-->

# Knowledge

## `bento ask <query>`

Search the wiki, blueprints, and recipes, then answer with the configured target route.

```bash
bento ask "how do I configure a tunnel?" --target claude-fast
bento ask "how do I configure a tunnel?" --target claude-haiku-low --target codex-low
```

`--target` is repeatable and gives an ordered route. The first flag is the primary target. A quota or authentication failure, or a model the provider refuses, advances to the next candidate. Any other failure stops the command and shows the error. Each target expands its own `credential_pool` before the route moves to the next target. Repeated flags replace the configured `ask.targets` route. They do not extend it.

| Flag | Description |
|------|-------------|
| `--target <name>` | Named execution target, repeatable in route order (defaults to `ask.targets` in `daemon.yaml`) |
| `--granularity <g>` | `chunks` (retrieved excerpts, default) or `docs` (whole filtered docs inlined) |
| `--tag <t>` | Only docs carrying this tag (repeatable) |
| `--category <c>` | Only docs in this category (repeatable) |
| `--top-k <n>` | Results per source |
| `--rerank` | Enable the optional retrieval reranker |
| `--instructions <text>` | Custom usage instructions — rendered in the user message, replacing the default system instruction |
| `--instance <name>` | Target daemon instance (default: cwd config, else the running instance) |

```bash
bento ask "how do we test the daemon" --granularity docs --category conventions
bento ask "branch rules" --tag git --top-k 3
```

## `bento knowledge-base`

List the knowledge docs registered with the daemon — wiki, blueprints, and recipes — grouped by URI scheme, with `category:` frontmatter as branches and `tags:` as suffixes. `bento kb` is an alias.

```bash
bento kb
bento kb --tag git # only docs carrying the tag (repeatable; all must match)
```

```
wiki:// (3)
├── conventions/
│   └── testing — Testing  [testing, vitest]
└── git-workflow — Git Workflow  [git, process]

recipe:// (1)
└── setup-knowledge-base — Setting Up the Knowledge Base  [knowledge, setup]
```

| Flag | Description |
|------|-------------|
| `--tag <t>` | Only docs carrying this tag (repeatable) |
| `--instance <name>` | Target daemon instance (default: cwd config, else the running instance) |
