Skip to main content
Entities are defined in YAML files under configs/entities/. Each file describes one persistent being — personality, voice, drives, cognition, platforms, and automations.

Two paths

The interactive wizard walks you through:
  1. Name your entity
  2. Pick an archetype (curious, sardonic, gentle, guardian) or start blank
  3. Tune traits — Big Five-style sliders for curiosity, warmth, assertiveness, humor, openness, neuroticism, conscientiousness
  4. Set behavioral patterns — how it handles conflict, boredom, affection, criticism
  5. Configure voice — vocabulary, style, quirks, profanity
  6. Write a backstory — one line or a paragraph
  7. Choose models and platforms — defaults from your harness config
The wizard writes a complete YAML file and suggests bumblebee talk <name> to start talking.

YAML anatomy

A minimal entity:

Key sections

Core traits (0.0–1.0), behavioral patterns, voice configuration, and backstory. The personality engine compiles these into a first-person system prompt. See Personality and voice.
Curiosity topics, attachment threshold, restlessness decay, initiative cooldown. Drives accumulate over time and trigger proactive behavior when they cross thresholds.
Per-entity model overrides, thinking mode, temperature, context window, and token budgets. These override configs/default.yaml harness defaults.
Which platforms the entity runs on, tool activity visibility, and daemon settings.
Optional merge onto harness autonomy — same keys as configs/default.yaml under autonomy: (wake timing, sustained sessions, poker prompts, wide mode, chat/log visibility). Does not replace the whole harness; only specified keys override.
To disable autonomous wake (full self-initiated perceive cycles), set enabled: false. Legacy drive-based initiative may still apply — see Disabling autonomous wake.See Autonomous wake.
Scheduled routines, emergence suggestions, and journal integration. See Automations.
External tool servers via Model Context Protocol. See Tools.

Templates

Templates live in bumblebee/genesis/templates/. The wizard loads them as starting points — you can modify everything afterward.

File locations

On Railway, canary.yaml is not in the image — the Dockerfile copies canary.example.yaml instead. Set operator IDs via BUMBLEBEE_TELEGRAM_OPERATOR_IDS env var on the Railway service.