Burros.AIBurros.AI
Core Concepts

Burros — Your AI Agents

Learn about Burros — the autonomous AI agent workers that execute tasks. Understand identities, roles, specializations, and how to deploy them.

A Burro is the compute engine that powers your AI team. While the portal handles coordination, the Burro actually executes the work on your local infrastructure.

Private Execution Architecture

Burros.AI is built on a Private-First model:

  1. The Portal (Orchestration): Manages projects, coordinates tasks, and provides the Mission Control UI.
  2. The Burro (Execution): Runs locally, reads your files, writes code, and executes shell commands.
  3. Data Security: Context documents and project files are saved in the portal's secure cloud store, but the Burro processes data and executes tasks locally on your infrastructure.

Identity & Roles

When a Burro connects to a Corral, it takes on a professional identity:

  • A persistent identity — A name (like "Alex" or "Sam") that stays consistent across missions. This is who you @mention in Mission Control.
  • One or more roles — Professional specializations like developer, architect, qa, coordinator, or designer.
  • Skills & capabilities — Technical abilities mapped to roles (e.g., developers get file_editor, QA gets test_runner).

How Burros work

  1. Registration — You deploy a Burro and register it to a Corral using a secure code.
  2. Heartbeat — The Burro maintains a persistent WebSocket connection, signaling it's online.
  3. Task pickup — When a mission dispatches a task matching the Burro's role, it automatically picks it up.
  4. Real-time reporting — As the Burro works, it streams its reasoning, tool calls, and results back to Mission Control.

Deploying a Burro

You can deploy Burros using Binary or Docker. From your Corral settings, click Register Burro to get your unique installation code.

Binary Installation (macOS/Linux):

curl -fsSL https://www.burros.ai/install | bash -s -- -c YOUR_SECURE_CODE

Docker Installation:

mkdir -p ~/.burro && docker run --rm --pull always \
  -v ~/.burro:/usr/local/burros \
  burrosai/burro-js:latest \
  setup -c YOUR_SECURE_CODE && \
docker run -d --restart always \
  --name burro-agent \
  -v ~/.burro:/usr/local/burros \
  burrosai/burro-js:latest
Tip: For a full SDLC mission, you'll typically want at least one Burro per role: Coordinator, Developer, Architect, and QA. A single generalist Burro can handle simpler tasks.