> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fluffbuzz.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Agents

# `fluffbuzz agents`

Manage isolated agents (workspaces + auth + routing).

Related:

* Multi-agent routing: [Multi-Agent Routing](/concepts/multi-agent)
* Agent workspace: [Agent workspace](/concepts/agent-workspace)
* Skill visibility config: [Skills config](/tools/skills-config)

## Examples

```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}
fluffbuzz agents list
fluffbuzz agents list --bindings
fluffbuzz agents add work --workspace ~/.fluffbuzz/workspace-work
fluffbuzz agents add ops --workspace ~/.fluffbuzz/workspace-ops --bind telegram:ops --non-interactive
fluffbuzz agents bindings
fluffbuzz agents bind --agent work --bind telegram:ops
fluffbuzz agents unbind --agent work --bind telegram:ops
fluffbuzz agents set-identity --workspace ~/.fluffbuzz/workspace --from-identity
fluffbuzz agents set-identity --agent main --avatar avatars/fluffbuzz.png
fluffbuzz agents delete work
```

## Routing bindings

Use routing bindings to pin inbound channel traffic to a specific agent.

If you also want different visible skills per agent, configure
`agents.defaults.skills` and `agents.list[].skills` in `fluffbuzz.json`. See
[Skills config](/tools/skills-config) and
[Configuration Reference](/gateway/configuration-reference#agents-defaults-skills).

List bindings:

```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}
fluffbuzz agents bindings
fluffbuzz agents bindings --agent work
fluffbuzz agents bindings --json
```

Add bindings:

```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}
fluffbuzz agents bind --agent work --bind telegram:ops --bind discord:guild-a
```

If you omit `accountId` (`--bind <channel>`), FluffBuzz resolves it from channel defaults and plugin setup hooks when available.

If you omit `--agent` for `bind` or `unbind`, FluffBuzz targets the current default agent.

### Binding scope behavior

* A binding without `accountId` matches the channel default account only.
* `accountId: "*"` is the channel-wide fallback (all accounts) and is less specific than an explicit account binding.
* If the same agent already has a matching channel binding without `accountId`, and you later bind with an explicit or resolved `accountId`, FluffBuzz upgrades that existing binding in place instead of adding a duplicate.

Example:

```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}
# initial channel-only binding
fluffbuzz agents bind --agent work --bind telegram

# later upgrade to account-scoped binding
fluffbuzz agents bind --agent work --bind telegram:ops
```

After the upgrade, routing for that binding is scoped to `telegram:ops`. If you also want default-account routing, add it explicitly (for example `--bind telegram:default`).

Remove bindings:

```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}
fluffbuzz agents unbind --agent work --bind telegram:ops
fluffbuzz agents unbind --agent work --all
```

`unbind` accepts either `--all` or one or more `--bind` values, not both.

## Command surface

### `agents`

Running `fluffbuzz agents` with no subcommand is equivalent to `fluffbuzz agents list`.

### `agents list`

Options:

* `--json`
* `--bindings`: include full routing rules, not only per-agent counts/summaries

### `agents add [name]`

Options:

* `--workspace <dir>`
* `--model <id>`
* `--agent-dir <dir>`
* `--bind <channel[:accountId]>` (repeatable)
* `--non-interactive`
* `--json`

Notes:

* Passing any explicit add flags switches the command into the non-interactive path.
* Non-interactive mode requires both an agent name and `--workspace`.
* `main` is reserved and cannot be used as the new agent id.

### `agents bindings`

Options:

* `--agent <id>`
* `--json`

### `agents bind`

Options:

* `--agent <id>` (defaults to the current default agent)
* `--bind <channel[:accountId]>` (repeatable)
* `--json`

### `agents unbind`

Options:

* `--agent <id>` (defaults to the current default agent)
* `--bind <channel[:accountId]>` (repeatable)
* `--all`
* `--json`

### `agents delete <id>`

Options:

* `--force`
* `--json`

Notes:

* `main` cannot be deleted.
* Without `--force`, interactive confirmation is required.
* Workspace, agent state, and session transcript directories are moved to Trash, not hard-deleted.

## Identity files

Each agent workspace can include an `IDENTITY.md` at the workspace root:

* Example path: `~/.fluffbuzz/workspace/IDENTITY.md`
* `set-identity --from-identity` reads from the workspace root (or an explicit `--identity-file`)

Avatar paths resolve relative to the workspace root.

## Set identity

`set-identity` writes fields into `agents.list[].identity`:

* `name`
* `theme`
* `emoji`
* `avatar` (workspace-relative path, http(s) URL, or data URI)

Options:

* `--agent <id>`
* `--workspace <dir>`
* `--identity-file <path>`
* `--from-identity`
* `--name <name>`
* `--theme <theme>`
* `--emoji <emoji>`
* `--avatar <value>`
* `--json`

Notes:

* `--agent` or `--workspace` can be used to select the target agent.
* If you rely on `--workspace` and multiple agents share that workspace, the command fails and asks you to pass `--agent`.
* When no explicit identity fields are provided, the command reads identity data from `IDENTITY.md`.

Load from `IDENTITY.md`:

```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}
fluffbuzz agents set-identity --workspace ~/.fluffbuzz/workspace --from-identity
```

Override fields explicitly:

```bash theme={"theme":{"light":"min-light","dark":"min-dark"}}
fluffbuzz agents set-identity --agent main --name "FluffBuzz" --emoji "🐾" --avatar avatars/fluffbuzz.png
```

Config sample:

```json5 theme={"theme":{"light":"min-light","dark":"min-dark"}}
{
  agents: {
    list: [
      {
        id: "main",
        identity: {
          name: "FluffBuzz",
          theme: "space puppy",
          emoji: "🐾",
          avatar: "avatars/fluffbuzz.png",
        },
      },
    ],
  },
}
```