team.yaml (Legacy)

File location: ~/.disclaw-team/team.yaml

Two modes:

1. Legacy format — Hand-authored single file that contains all config (bots, roles, Discord, protocol)
2. Derived format — Auto-generated from bots.yaml + assignment.yaml before each start

If you’re using the new format (bots.yaml + assignment.yaml), you don’t need to edit team.yaml directly. It’s regenerated automatically.

Minimal valid legacy example:

version: 1
name: My Team
discord:
  guild_id: "123456789012345678"
  channels:
    general: "987654321098765432"

bots:
  bot-1:
    name: Orchestrator
    token_env: BOT_1_TOKEN
    role: orchestrator
    dm_policy: allowlist
    channels:
      - "987654321098765432"

Field reference (legacy format):

Field	Type	Required	Description
version	number	No	Config version (currently 1)
name	string	No	Team display name
discord.guild_id	string	Yes	Discord server ID
discord.channels.general	string	Yes	General channel ID
defaults.workspace	string	No	Working directory for bots
defaults.model	string	No	Default model: opus, sonnet, haiku
bots	object	Yes	Bot definitions (key = bot-id)
bots.<id>.name	string	Yes	Bot display name
bots.<id>.token_env	string	Yes	Environment variable name for Discord token
bots.<id>.role	string	Yes	Role type or role-id
bots.<id>.dm_policy	string	No	allowlist or pairing (see gotcha below)
bots.<id>.channels	array	No	Channel IDs this bot listens to
humans	object	No	Human team members (key = slug)
humans.<id>.name	string	Yes	Human display name
humans.<id>.discord_id	string	Yes	Human Discord user ID
humans.<id>.role	string	No	Human role (default: owner)
protocol.communication.*	object	No	Communication rules (see Protocol)
protocol.validation.*	object	No	Validation chain rules
protocol.escalation.*	object	No	Human approval rules

dm_policy: disabled is silently rewritten

Setting dm_policy: disabled on a bot does not disable DMs — it gets silently rewritten to an empty allowlist at startup. This is because disabled in the underlying plugin drops guild messages too, which would break all bot communication. If you want to restrict DMs, use dm_policy: allowlist with an empty allow_from list instead.

Missing tokens hard-abort in legacy format

In legacy format, a missing bot token is a hard error — all bots fail to start. In new format (bots.yaml), a missing token logs a warning and silently skips only that bot.

switch commands don’t persist with new format

In new-format setups, disclaw-team start regenerates team.yaml from bots.yaml and assignment.yaml on every run. Any changes you make to team.yaml directly (including those loaded via disclaw-team switch) are overwritten the next time you start. Use assignment.yaml overrides to customize behavior persistently.

Related: bots.yaml, assignment.yaml, CLI: switch