Skip to content
RemoteClaw

agents

remoteclaw agents

Manage isolated agents (workspaces + auth + routing).

Related:

Examples

Terminal window
remoteclaw agents list
remoteclaw agents add work --workspace ~/.remoteclaw/workspace-work
remoteclaw agents bindings
remoteclaw agents bind --agent work --bind telegram:ops
remoteclaw agents unbind --agent work --bind telegram:ops
remoteclaw agents set-identity --workspace ~/.remoteclaw/workspace --from-identity
remoteclaw agents set-identity --agent main --avatar avatars/remoteclaw.png
remoteclaw agents delete work

Routing bindings

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

List bindings:

Terminal window
remoteclaw agents bindings
remoteclaw agents bindings --agent work
remoteclaw agents bindings --json

Add bindings:

Terminal window
remoteclaw agents bind --agent work --bind telegram:ops --bind discord:guild-a

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

Example:

Terminal window
# initial channel-only binding
remoteclaw agents bind --agent work --bind telegram


# later upgrade to account-scoped binding
remoteclaw 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:

Terminal window
remoteclaw agents unbind --agent work --bind telegram:ops
remoteclaw agents unbind --agent work --all

Identity files

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

  • Example path: ~/.remoteclaw/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:

Terminal window
remoteclaw agents set-identity --workspace ~/.remoteclaw/workspace --from-identity

Override fields explicitly:

Terminal window
remoteclaw agents set-identity --agent main --name "RemoteClaw" --emoji "🦞" --avatar avatars/remoteclaw.png

Config sample:

{
  agents: {
    list: [
      {
        id: "main",
        identity: {
          name: "RemoteClaw",
          theme: "space lobster",
          emoji: "🦞",
          avatar: "avatars/remoteclaw.png",
        },
      },
    ],
  },
}