Agents

remoteclaw agents

Manage isolated agents (workspaces + auth + routing).

Related:

• Multi-agent routing
• Agent workspace
• Skills config: skill visibility configuration.

Examples

remoteclaw agents list
remoteclaw agents list --bindings
remoteclaw agents add work --workspace ~/.remoteclaw/workspace-work
remoteclaw agents add work --workspace ~/.remoteclaw/workspace-work --bind telegram:*
remoteclaw agents add ops --workspace ~/.remoteclaw/workspace-ops --bind telegram:ops --non-interactive
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.

If you also want different visible skills per agent, configure agents.defaults.skills and agents.list[].skills in remoteclaw.json. See Skills config and Configuration reference.

List bindings:

remoteclaw agents bindings
remoteclaw agents bindings --agent work
remoteclaw agents bindings --json

Add bindings:

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

You can also add bindings when creating an agent:

remoteclaw agents add work --workspace ~/.remoteclaw/workspace-work --bind telegram:* --bind discord:*

If you omit accountId (--bind <channel>), RemoteClaw resolves it from plugin setup hooks, forced account binding, or the channel’s configured account count.

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

--bind format

Format	Meaning
--bind <channel>:*	Match all accounts on the channel.
--bind <channel>:<account>	Match one account.
--bind <channel>	Match the default account only unless the CLI can safely resolve a plugin-specific account scope.

Binding scope behavior

• A stored 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.

Examples:

# match all accounts on the channel
remoteclaw agents bind --agent work --bind telegram:*

# match a specific account
remoteclaw agents bind --agent work --bind telegram:ops

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

# later upgrade to account-scoped binding
remoteclaw agents bind --agent work --bind telegram:alerts

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

Remove bindings:

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

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

Command surface

agents

Running remoteclaw agents with no subcommand is equivalent to remoteclaw 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.
• In interactive mode, auth seeding copies only portable static profiles (api_key and static token by default). OAuth refresh-token profiles remain available only by read-through inheritance from the real main agent store. If the configured default agent is not main, sign in separately for OAuth profiles on the new agent.

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.
• When the Gateway is reachable, deletion is sent through the Gateway so config and session-store cleanup share the same writer as runtime traffic. If the Gateway cannot be reached, the CLI falls back to the offline local path.
• If another agent’s workspace is the same path, inside this workspace, or contains this workspace, the workspace is retained and --json reports workspaceRetained, workspaceRetainedReason, and workspaceSharedWith.

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)

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:

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

Override fields explicitly:

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

Config sample:

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

Related

• CLI reference
• Multi-agent routing
• Agent workspace