Bring your tooling

Your machine. Your tools. More workers when you need them.

New here? Install the CLI first →, then pick your tooling here.

Start local. Scale out.

• Developer computer: run bakers.build alongside your existing setup.
• Remote workers: add servers when you need more capacity.
• Just follow tickets: let your team's workers do the work.

Choose your workspace manager

Keep terminals organized and agent sessions running.

• herdr — available now. bakers.build's current workspace-manager integration.
• tuios — coming soon. Another workspace-manager integration is on the way.

Workspace setup and checks →

Bring your development environment

DDEV, Node.js, Docker or your own tooling. Your project decides.

• Use what works: keep your existing setup and scripts.
• Connect through hooks: prepare each ticket's environment with project commands.
• Local or remote: those commands can also reach a remote environment.

Connect your tooling with hooks →

Pick your agent

Claude Code, Codex, Grok, Kimi, OpenCode or Pi. Choose the agents your workers use.

Claude and Codex run in their OS sandbox; on Linux install bubblewrap and socat first (sudo apt-get install -y bubblewrap socat on Debian and Ubuntu; other platforms: Sandbox prerequisites).

Agent setup →

Get ready

• Set up Node.js for bakers.build →
• Check your chosen tools →
• Install bakers.build and sign in →

Prefer a wizard?

Install the bakers.build plugin first, then ask your AI: “Use bakers:bb-init to explain the options and walk me through setup.”

Servers

A remote worker is another machine running bakers.build. It can use local or remote development environments, just like your computer.

Set up a worker server →

Set up a Coder workspace →