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

# Members

Use `.bento/members.yaml` to maintain the people, agents, and services that Bento addresses. This page describes the manual member directory for Self-Hosted deployments.

> **Bento Cloud:** Cloud-managed member directories are coming soon. Until then, maintain `.bento/members.yaml` in your Self-Hosted project.

## Create a member directory

Add one entry for each member that Bento must resolve. Use a stable member key and at least one provider identity.

```yaml
members:
  arnold:
    name: Arnold Porter
    kind: person
    identities:
      github:
        id: "42714653"
        handle: arnoldporter
      slack:
        id: U04AB12CD
```

## Maintain identities

Use the provider account `id` for routing. Keep the `id` when a person changes their provider handle.

Use `handle` as a readable alias and as a fallback for webhook payloads that contain no provider ID. A handle can change without changing the member key or provider ID.

Supported providers are `github`, `slack`, and `linear`. Each identity needs a non-empty provider `id`.

Use `kind` to describe the entry. The default is `person`.

| `kind` | Use for |
| --- | --- |
| `person` | A person who can answer an eval. |
| `agent` | An agent that Bento knows but does not ask for an eval. |
| `service` | A service identity that Bento does not ask for an eval. |

Set `status: deactivated` when a person should not receive new eval requests. Keep the entry so that historical references still resolve.

## Create groups

Use `.bento/groups.yaml` to define named sets of members.

```yaml
groups:
  reviewers:
    members: [arnold]
```

Reference member keys in groups. Do not use handles. Groups contain member keys, not other groups.

## Validate the directory

Run the configuration validator after you add, rename, deactivate, or remove a member:

```bash
bento config validate
```

The validator checks member identities, duplicate provider IDs, duplicate handles, group membership, and literal eval recipients. It also checks the result-field paths in `eval.of` and `eval.labels` against a declared `result.schema`.

## Use members in evals

An `eval.of` value can name a member key, a member handle, a provider account ID, or a group:

```yaml
eval:
  of: arnold
```

See the [pipeline eval reference](/pipelines/config#eval) for recipient and result-based routing.
