Build apps with AI, in your own Cloudflare account. Tell Chef what you want. It plans the work, builds every feature in its own sandbox with the whole app running there, and merges it once the checks pass.
Sign in with Cloudflare and start building →
AI can write code fast. Everything around the code is still slow: starting and tracking agent sessions, juggling branches and merge conflicts, setting up an environment to try each change, and checking that nothing broke before it ships.
Chef takes that work off your plate, so you spend your time on what to build, not on keeping the build running.
- Sessions run themselves. Each request becomes a session that Chef starts, tracks, keeps up to date and closes for you. Run many at once and none blocks another.
- No git chores. No branches, merges, rebases or conflicts to handle. Chef keeps every session in sync with
mainand merges finished work for you. - Every branch runs. Each branch gets its own sandbox where the whole app runs, any stack your compose file describes, at its own private link. Sandboxes sleep when idle and wake on the next click.
- Main is the release candidate.
mainruns the same way after every merge. Production stays yours: connect your repo to wherever you deploy. - Checked before it ships. Tests, typecheck and an AI review must pass before anything reaches
main. - Your keys stay yours. Bring an Anthropic API key or any compatible provider. Keys stay in your Cloudflare account, never in the browser or the sandbox.
- Or use your subscription. Have a Claude subscription but no API key? sub2api turns it into your own API on Cloudflare, so you can make an API key on your subscription and use it in Chef.
- GitHub when you want it. Projects live in your Cloudflare account. Connect GitHub only if you want a repo kept in sync.
Chef is a TypeScript monorepo that runs entirely on Cloudflare's developer platform.
- Engine. One Worker with Durable Objects: a
ProjectAgentper project and aSessionAgentper session hold state and drive work, so nothing stops when the browser closes. - Repos. Every project is a git repository in Cloudflare Artifacts. Each session works on its own fork, and only the merge gate can write
main. - Routing. Rules first, then Jev (TypeSafe's System One) answers typed choice questions with calibrated confidence. When it is unsure, a Claude planner writes the spec and splits the work into parallel sessions.
- Coding. The Claude Agent SDK runs inside a Cloudflare Sandbox (Containers) with role-scoped subagents for tests, code and review. The sandbox gets a read-only token, and its outbound proxy swaps in real keys only on approved hosts.
- History. Each agent turn is one commit, with its prompt, model and role stored in git notes (
refs/notes/chef). - Gate. Typecheck, lint, tests, spec lint, write-scope checks per role, locked tests, an independent AI review and a proof run against the branch's running app. Merges are serialized; if
mainmoved, the session syncs and is gated again. - Running apps. Each sandbox runs Docker and starts the branch's compose stack; a small router Worker gives it a private address. Idle sandboxes sleep and start again on the next visit.
- Memory. Lessons and feature summaries are indexed in Vectorize with Workers AI embeddings and recalled before each turn.
- Live UI. Sessions stream to a React dashboard over AG-UI with CopilotKit: coder output, tool calls, steps, running app, review and merge.
Details: docs/ARCHITECTURE.md.
Run pnpm install and pnpm run verify. Repository layout and the CLI: docs/DEVELOPMENT.md.