Skip to content

Which file owns what ​

bakers.build splits configuration by owner, so your login never lands in a repository and one laptop's settings never change a team's project.

FileLocationOwnsCommit
Machine~/.bakers/machine.config.jsHost identity, capacity, tunnel policy, agent harnesses and routesNo
Connection~/.bakers/bakers.config.js or ~/.bakers/connections/<id>.jsServer URL, sign-in, connection addonsNo
Checkout selector.bakers/connection.config.local.jsThe name of one connectionNo
Conductor config.bakers/conductor.config.jsProject identity, execution wiring, scheduling, hooksYes
Local engine inputs.bakers/conductor.config.local.jsOnly values the conductor config imports from itNo
Project rulesWORKFLOW.mdSkills, standards, checksYes

BB_HOME names the ~/.bakers directory itself and moves the machine and connection files together.

Check the result with bakers config check --scope all. Add --online to also verify sign-in and project access.

Tasks ​

I want toGo to
Choose agents and models, route states to agentsChoose agents and models
Run a command when a worktree is prepared or removedAdd lifecycle hooks
Share a running previewPorts
Browse a run's local evidenceArtifacts
Update the CLI, configuration and project filesUpdate bakers.build
Connect your own claude.ai account to bakers.buildConnect Claude.ai to bakers.build

Reference ​

Every field of the machine and connection files is in Machines and Connections. The conductor file is in Conductor configuration, and old keys are repaired as described in Configuration migration.