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

# agents

# `wednesdayai agents`

Manage isolated agents (workspaces + auth + routing).

Related:

* Multi-agent routing: [Multi-Agent Routing](https://docs.wednesdayai.dev/next/developers/concepts/multi-agent.md)
* Agent workspace: [Agent workspace](https://docs.wednesdayai.dev/next/developers/concepts/agent-workspace.md)

## Examples

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

## Delete an agent

`wednesdayai agents delete work` removes the agent configuration and its active session
list. Those sessions stay absent after a gateway restart; stored conversation
history is retained, not erased. Workspace and agent-state directories are moved
to trash, while legacy session sources remain available for automatic import.

When the gateway is running, it performs the deletion. Otherwise the command takes
temporary ownership of session storage. Add `--force` for non-interactive deletion.

`--json` reports the deletion owner's result. With a running gateway, this is the gateway's
`agents.delete` response (including its `removedBindings` count), not counts or filesystem paths
computed from the CLI's config. With a local owner, the result includes the workspace and
agent-state paths and local removal counts. Neither route reports a `sessionsDir`: session
history lives in SQL, and the old transcript directory is only an import source.

## Routing bindings

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

List bindings:

```bash theme={"dark"}
wednesdayai agents bindings
wednesdayai agents bindings --agent work
wednesdayai agents bindings --json
```

Add bindings:

```bash theme={"dark"}
wednesdayai agents bind --agent work --bind telegram:ops --bind discord:guild-a
```

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

Example:

```bash theme={"dark"}
# initial channel-only binding
wednesdayai agents bind --agent work --bind telegram

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

## Identity files

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

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

Override fields explicitly:

```bash theme={"dark"}
wednesdayai agents set-identity --agent main --name "WednesdayAI" --emoji "🦞" --avatar avatars/openclaw.png
```

Config sample:

```json5 theme={"dark"}
{
  agents: {
    list: [
      {
        id: "main",
        identity: {
          name: "WednesdayAI",
          theme: "space lobster",
          emoji: "🦞",
          avatar: "avatars/openclaw.png",
        },
      },
    ],
  },
}
```

## Session Journal

Agents can write a reflective LLM journal entry each time a session resets via `/new` or `/reset`.
Opt in per agent with `sessionJournal.enabled: true`.

```json5 theme={"dark"}
{
  agents: {
    list: [
      {
        id: "claire",
        sessionJournal: {
          enabled: true,
          // optional — include {transcript} where session text should be injected
          prompt: "Write structured patient notes in SOAP format.\n\nSession transcript:\n{transcript}",
        },
      },
    ],
  },
}
```

| Field | Type | Default | Description |
| - | - | - | - |
| `enabled` | `boolean` | `false` | Enable journal generation for this agent |
| `prompt` | `string` | built-in | LLM prompt. Include `{transcript}` where the session text should be injected; if absent, the transcript is appended after the prompt. |

Journal files are written to `<effectiveWorkspaceDir>/journal/YYYY-MM-DD-HHMMss-<slug>.md`. In multi-user
mode (workspace lanes), each lane gets its own `journal/` folder — journals are isolated per
user, not shared with other lanes on the same agent.

The bundled `session-journal` hook must be enabled for this config to take effect:

```bash theme={"dark"}
wednesdayai hooks enable session-journal
```

See [Hooks: session-journal](https://docs.wednesdayai.dev/next/users/automation/hooks.md#session-journal) for full details.


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