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

# agents

# `gensparx agents`

Manage isolated agents (workspaces + auth + routing).

Related:

* Multi-agent routing: [Multi-Agent Routing](/concepts/multi-agent)
* Agent workspace: [Agent workspace](/concepts/agent-workspace)

## Examples

```bash theme={null}
gensparx agents list
gensparx agents add work --workspace ~/.gensparx/workspace-work
gensparx agents bindings
gensparx agents bind --agent work --bind telegram:ops
gensparx agents unbind --agent work --bind telegram:ops
gensparx agents set-identity --workspace ~/.gensparx/workspace --from-identity
gensparx agents set-identity --agent main --avatar avatars/gensparx.png
gensparx agents delete work
```

## Routing bindings

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

List bindings:

```bash theme={null}
gensparx agents bindings
gensparx agents bindings --agent work
gensparx agents bindings --json
```

Add bindings:

```bash theme={null}
gensparx agents bind --agent work --bind telegram:ops --bind discord:guild-a
```

If you omit `accountId` (`--bind <channel>`), gensparx 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`, gensparx upgrades that existing binding in place instead of adding a duplicate.

Example:

```bash theme={null}
# initial channel-only binding
gensparx agents bind --agent work --bind telegram

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

## Identity files

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

* Example path: `~/.gensparx/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={null}
gensparx agents set-identity --workspace ~/.gensparx/workspace --from-identity
```

Override fields explicitly:

```bash theme={null}
gensparx agents set-identity --agent main --name "Gensparx" --emoji "⚡" --avatar avatars/gensparx.png
```

Config sample:

```json5 theme={null}
{
  agents: {
    list: [
      {
        id: "main",
        identity: {
          name: "Gensparx",
          theme: "space lobster",
          emoji: "⚡",
          avatar: "avatars/gensparx.png",
        },
      },
    ],
  },
}
```