> ## Documentation Index
> Fetch the complete documentation index at: https://agdiai-597e782f.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# agents

# `agdi agents`

Manage isolated agents (workspaces + auth + routing).

Related:

* Multi-agent routing: [Multi-Agent Routing](https://agdiai-597e782f.mintlify.site/concepts/multi-agent.md)
* Agent workspace: [Agent workspace](https://agdiai-597e782f.mintlify.site/concepts/agent-workspace.md)

## Examples

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

## Routing bindings

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

List bindings:

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

Add bindings:

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

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

### 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`, Agdi 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
agdi agents bind --agent work --bind telegram

# later upgrade to account-scoped binding
agdi 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"}}
agdi agents unbind --agent work --bind telegram:ops
agdi agents unbind --agent work --all
```

## Identity files

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

* Example path: `~/.agdi/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)

Load from `IDENTITY.md`:

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

Override fields explicitly:

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

Config sample:

```json5 theme={"theme":{"light":"min-light","dark":"min-dark"}}
{
  agents: {
    list: [
      {
        id: "main",
        identity: {
          name: "Agdi",
          theme: "space lobster",
          emoji: "🦞",
          avatar: "avatars/agdi.png",
        },
      },
    ],
  },
}
```


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.