Skip to main content
In Bumblebee, an agent is not a disposable chat session. It is a digital entity: configured in YAML, backed by durable memory and soma state, and run by the same harness whether you talk on Telegram, Discord, or the CLI.

​
One brain, many surfaces

  • Identity and memory are shared. The entity remembers people, episodes, and beliefs across every channel.
  • Cognition (reflex, deliberate, tools) is the same stack for all inputs.
  • Presence is plugged in per platform: each social adapter translates that channel’s messages into a common perceive pipeline and routes replies back.
So “building an agent” usually means: define who the entity is (traits, voice, drives), wire where it appears (platform blocks in YAML), and choose where inference runs (local Ollama, or a remote gateway to your GPU).

​
Worker vs full run

ModeCommandTypical use
Full runtimebumblebee run <entity>Laptop or desktop: CLI + Telegram/Discord + daemon.
Workerbumblebee worker <entity>Servers (e.g. Railway): messaging + daemon without an interactive CLI.
The worker is the same codebase and the same entity — trimmed for headless operation. See Worker runtime.