Skip to main content

​
fluffbuzz agents

Manage isolated agents (workspaces + auth + routing). Related:

​
Examples

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

​
Routing bindings

Use routing bindings to pin inbound channel traffic to a specific agent. List bindings: 
fluffbuzz agents bindings
fluffbuzz agents bindings --agent work
fluffbuzz agents bindings --json
Add bindings: 
fluffbuzz agents bind --agent work --bind telegram:ops --bind discord:guild-a
If you omit accountId (--bind <channel>), FluffBuzz 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, FluffBuzz upgrades that existing binding in place instead of adding a duplicate.
Example: 
# initial channel-only binding
fluffbuzz agents bind --agent work --bind telegram

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

​
Identity files

Each agent workspace can include an IDENTITY.md at the workspace root:
  • Example path: ~/.fluffbuzz/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: 
fluffbuzz agents set-identity --workspace ~/.fluffbuzz/workspace --from-identity
Override fields explicitly: 
fluffbuzz agents set-identity --agent main --name "FluffBuzz" --emoji "🐾" --avatar avatars/fluffbuzz.png
Config sample: 
{
  agents: {
    list: [
      {
        id: "main",
        identity: {
          name: "FluffBuzz",
          theme: "space puppy",
          emoji: "🐾",
          avatar: "avatars/fluffbuzz.png",
        },
      },
    ],
  },
}