Skip to main content
Use this page when you want to control how Boo Zero, the universal team leader, names itself, what it knows about your teams, and the rules it follows. Boo Zero participates in every team but belongs to none, and its identity is load-bearing: production runs showed it drifting (calling itself the wrong name, doing teammate work instead of delegating, claiming teammates “timed out”), so Clawboo gives you explicit surfaces to anchor that identity and inject durable guidance. There are two places to configure Boo Zero, split by scope:
  • Global (display name + global brief): the Brief tab on Boo Zero’s own agent view.
  • Per-team (brief + rules): the Brief & Rules sheet behind the gear in the team chat header, plus the /rule slash command in the team composer.

​
Who Boo Zero is

Boo Zero is the primary OpenClaw agent, identified at connect time. Identification priority: the Gateway’s defaultId, then the first teamless agent (teamId === null), then the first agent overall. The resolved id lives in useBooZeroStore.booZeroAgentId. Boo Zero is teamless in the database (teamId === null) but participates in every team via team-scoped sessions. In any team’s Ghost Graph, Boo Zero is pulled in as the universal leader even though it has no team membership; the TeamHaloLayer deliberately omits it from any team’s hull because its teamId stays null. Two visible signals mark Boo Zero in the UI, both driven by @clawboo/boo-avatar:
  • Reserved OpenClaw-Red tint. When isBooZero: true, the avatar’s tint is forced to TINTS[0] (#ff4d4d, OpenClaw red). Every other agent’s tint is a deterministic hash over the other nine tints, so the red ghost-lobster is Boo Zero’s alone. The accessory is also hard-locked to none; Boo Zero is the clean mascot, never wearing glasses/hat/headphones/crown.
  • A “Leadership” orbital in the graph. For every Boo flagged isUniversalLeader, useGraphData synthesizes a reserved SkillNode (skillId: 'clawboo-leadership', isLeadership: true) that orbits Boo Zero. SkillNode renders it with an amber Compass icon and hides the Install button; this skill cannot be installed on any other agent. It is a graph-layer attribute, not a real capability record, so it survives any future change to Boo Zero’s tools.
The Ghost Graph showing Boo Zero presiding over a team
The authoritative identity at runtime is the [Your Rules] anchor block built by buildBooZeroRulesBlock (lib/booZeroRules.ts), injected as the first section of every Boo-Zero-bound message: user messages, agent-to-Boo-Zero delegations, wake-ups, and the 1:1 chat path. That block is hard-coded (not editable through the UI) so the load-bearing safety rules, name, never spawn sub-agents, <delegate>-only routing, silence-on-relay, no false timeouts, no re-greeting, can never be deleted by editing a brief. Everything below is the editable context that rides alongside it.

​
Prerequisites

  • A connected runtime with Boo Zero identified (a fresh fleet hydration resolves it automatically).
  • For per-team configuration, a team must be selected; the Brief & Rules gear only renders when a team is active.

​
Set the display name and global brief

These two editors live on the Brief tab of Boo Zero’s individual agent view. The Brief tab is Boo-Zero-only: InlineEditor gates it on isBooZero, so it appears for no other agent.

​
Steps

  1. Open the Boo Zero view. Click the mascot icon at the top of the leftmost team sidebar. This selects no team (selectTeam(null)) and opens the Boo Zero agent view.
  2. Switch to the Brief tab in the inline editor.
  3. Set the display name. Type a name in the Display Name field (defaults to Boo Zero, max 80 characters) and click Save. This PUTs /api/boo-zero/display-name/:agentId with { name }, storing the override in Clawboo’s SQLite settings table under boo-zero:display-name:<agentId>. Saving also fires a best-effort sync of the new name into Boo Zero’s SOUL.md heading (syncBooZeroSoulIdentity) so the persisted identity aligns with the override.
  4. Edit the global brief. The Global Brief textarea holds Boo Zero’s overall responsibilities plus an auto-generated index of the teams it leads. Edit freely, then click Save to PUT /api/boo-zero/global-brief with { content }, stored in settings under boo-zero:global-brief. Use Regenerate from teams to rebuild a fresh draft from your current team list; this does not save until you click Save.
The Boo Zero agent view where the Brief tab lives

​
What each field does

FieldStored asEndpointWhere it goes
Display namesettings key boo-zero:display-name:<agentId>PUT /api/boo-zero/display-name/:agentId { name }Overlaid on the fleet entry at hydration; synced into SOUL.md heading (best-effort); fed into the [Your Rules] anchor as displayName
Global briefsettings key boo-zero:global-briefPUT /api/boo-zero/global-brief { content }Injected into Boo Zero’s context preamble on every interaction
The global brief seeds itself from buildGlobalBrief when nothing is stored. That generated default already embeds the same canonical rules block the LLM sees at runtime, so the maintenance UI shows you exactly what Boo Zero carries forward. The Notes section at the bottom of the brief is the freeform area for your own always-on guidance.
The display-name toast tells you to reload to apply across all views. The override is read at hydration time, so a reload re-overlays the new name everywhere. The per-turn rules anchor picks up the new name on the next message regardless.

​
Set per-team brief and rules

Per-team configuration lives in the Brief & Rules sheet (TeamSettingsSheet), opened from the gear in the team chat header (GroupChatViewHeader). The sheet stacks two editors below the team’s icon/accent/color controls: the per-team Brief and the per-team Rules.

​
Steps

  1. Open a team’s group chat and click the Brief & Rules gear in the header.
  2. Edit the per-team brief. This is what Boo Zero reads when it operates on this specific team. It is stored in the dedicated boo_zero_team_briefs table (one row per team, FK-cascaded on team delete) via PUT /api/boo-zero/team-briefs/:teamId with { content }.
  3. Edit the team rules. Type one rule per line. Save rules PUTs /api/team-rules/:teamId with { content } (capped at 4000 characters server-side), persisting to the settings key team-rules:<teamId>. These rules are injected into the preamble of every team agent’s message and every Boo Zero turn in this team.
The team space where the Brief & Rules gear lives in the header

​
Per-team surfaces at a glance

SurfaceStored asEndpoint(s)Scope of injection
Per-team briefboo_zero_team_briefs table (PK teamId, FK cascade)GET/PUT/DELETE /api/boo-zero/team-briefs/:teamIdBoo Zero, when working in this team
Team rulessettings key team-rules:<teamId>GET/PUT /api/team-rules/:teamIdEvery team agent’s preamble + every Boo Zero turn in this team
Per-team rules and briefs survive across sessions. The reason they exist: a user correction like “they are not sub-agents, delegate via <delegate>” sits only in chat history and rolls out of the last-8-messages context window within an hour. Persisting it durably means the team stops repeating the same mistake.

​
Capture a rule with /rule

The fastest way to add a team rule is the /rule slash command in the team chat composer, no need to open the sheet.
  1. In the team composer, type /rule <text> (the command requires a space after /rule and a non-empty body, so /rules or /rule: will not trigger it).
  2. Press send. Clawboo intercepts the message before routing to any agent: it fetches the team’s current rules, appends your text as a new line (deduping exact case-insensitive duplicates via appendRule), and PUTs them back through saveTeamRules. Nothing is sent to the runtime.
  3. A single confirmation entry (Rule saved for team: <text>) appears in the merged team view as a breadcrumb. On failure you get an error toast and the message is dropped.
The same rules text is wrapped in [Team Rules — set by the user, authoritative] … [End Team Rules] (buildTeamRulesBlock) before injection, so agents recognize it as authoritative user guidance.

​
Verify it worked

  • Display name: re-fetch GET /api/boo-zero/display-name/:agentId; the response { name } should match what you saved. After a reload, the new name appears in chat headers and the fleet sidebar.
  • Global brief: re-fetch GET /api/boo-zero/global-brief; { content } should be your saved markdown. A null content means nothing is stored and the UI is showing the generated default.
  • Per-team brief: re-fetch GET /api/boo-zero/team-briefs/:teamId; a non-null { content } confirms the upsert.
  • Team rules: re-fetch GET /api/team-rules/:teamId; { content } reflects your saved rules (or your /rule appends). Reopening the Brief & Rules sheet shows the same content.

​
Troubleshooting

Boo Zero still uses the wrong name in chat. The SOUL.md sync that runs on Save is best-effort; agents.files.set('SOUL.md') is documented as unreliable on older OpenClaw runtimes. This is not a problem in practice: the per-turn [Your Rules] anchor carries the authoritative displayName regardless, so Boo Zero refers to itself correctly on the next turn even when the file write does not land.
The Brief tab is missing. It only renders on Boo Zero’s own agent view, gated by isBooZero. If Boo Zero has not been identified yet (no agents hydrated, or a fresh connect mid-flight), the tab will not appear. Re-hydrate the fleet and reopen the mascot view.
Editing a brief does not change the safety rules. The ## Required behavior block you see inside the global brief is sourced from buildBooZeroRulesBlock for display parity; editing the brief textarea is documentation only. The runtime source is lib/booZeroRules.ts, which is not user-editable. To change Boo Zero’s enforced behavior you change that code, not the brief.
  • Agent model, Boo, Boo Zero, and the five runtime classes
  • Using teams, create/manage teams, leaders, and color collections
  • The Ghost Graph, where the Leadership orbital and red tint appear
  • Group chat, the team chat surface that hosts the /rule command and the Brief & Rules gear
  • Agents, the inline editor and the SOUL/IDENTITY/TOOLS/AGENTS files

​
See also