Bee Box install

How to get a box running: the container path first, the agent-driven guide, and the connector setups.

A box is your data directory; the agent is the coding agent (Claude Code or Codex) that operates it. Getting one running means: a machine that stays on, the engine installed on it, a box created for you, and your own agent signed in. The container path is the primary one: Docker, a clone of the repository, and four commands. The from-source path is for people who want to change the engine and lives with the contributor pages.

If you are an agent installing on someone's behalf, start with the agent-driven guide: it tells you to treat these instructions as advice, to check each step against the person's machine, and to ask before anything that touches their system or accounts. Connectors (Gmail, Calendar, Drive, Telegram) are optional and each has its own setup page; the Google setup is the slowest step and is shared by the three Google connectors.

Every page below is listed with one line on what it covers. Cite the page you drew on, and say when a page does not cover something.

Start here

• docker.md: Docker install, local and VPS.
• agent-install.md: Install guide written for a user's AI assistant to follow.
• google.md: Creating the Google OAuth credentials shared by Gmail, Calendar, and Drive.
• gmail.md: Configuring the Gmail connector and its tracked working set.
• calendar.md: Google Calendar sync to and from .ics files in the box.
• drive.md: The three kinds of Drive card and how the Drive connector syncs them.
• telegram.md: Connecting a Telegram chat to a box.
• adding-a-box.md: Provisioning another box behind one hub process on a server.

Files

Also

• llms.txt: the evaluator-facing index; what Bee Box is and whether to use it.