A coding agent that knows your code's structure, asks before it writes, and keeps its work on your machine.
BAKED reads your repository through language servers and tree-sitter, so it moves through code by symbols and imports instead of grepping raw text. It edits files, runs your checks and commits, asking first whenever it is about to write. Sessions, memory and workflow state stay local in SQLite.
▶ Watch the full 88-second video with sound
Status: pre-release. Releases are published on GitHub only, not on npm.
- Start from the coordinator. Each project opens on its coordinator: describe an idea, and it suggests a workflow, splits big work into parallel runs and keeps an eye on each one.
- Chat with an agent about your code. Ask a question or a change; BAKED finds the right files, shows each edit as a diff, and you can undo any turn. Pick how much it may do on its own (Manual, Auto or Full access) and its mode (Default, Architect or Plan first) per chat.
- Hand off a whole feature. A workflow run goes through research, spec, plan, implementation, checks and review on its own, and stops only where it needs your decision.
- Keep several projects going at once. Each open folder is a project with its own chats, runs and settings; Needs you collects everything waiting for an answer.
- Plan big ideas as initiatives. An initiative splits an idea into features, each with its own workflow run, budget and progress.
- See your codebase, your Git and your spend. A live code graph shows how folders and files depend on each other; the Git screen stages, commits, pushes and switches branches over a commit graph; the usage screen shows tokens and cost per stage and model.
- Use the model you already pay for. Claude, OpenAI, Codex, GitHub Copilot and GitHub Models are supported (providers).
BAKED comes as a desktop app, a terminal app, and a headless CLI for scripts and CI. All three run the same agent.
Screenshots show the desktop app in its dark theme with sample data.
Download your platform's file from Releases. While the repository is private, sign in to GitHub first, or use the GitHub CLI (gh release download --repo Gulliby-development/baked --pattern '<file>').
| Desktop app | Terminal app and CLI | |
|---|---|---|
| Windows | baked-desktop-<version>-win-<arch>.exe |
baked-setup-<version>-x64.exe, or the .zip |
| macOS | baked-desktop-<version>-mac-<arch>.dmg |
baked-<version>-darwin-<arch>.tar.gz, then ./install.sh |
| Linux | .AppImage or .deb |
baked-<version>-linux-<arch>.tar.gz, then ./install.sh |
The desktop app bundles its own baked, so you don't need both.
Unsigned installers, checksums and install details
- The installers are not signed yet. Windows SmartScreen warns on first launch (More info, then Run anyway); macOS blocks the app until you allow it in System Settings, Privacy & Security. See Desktop app.
- On Linux and macOS,
install.shfrom the extracted archive installs to~/.baked/bin. On Windows you can also extractbaked-<version>-windows-x64.zipand runbaked.exe. - Each release lists
SHA256SUMS.txtfor the archives.
Run from source
Use Bun 1.3.13 or newer on Windows, macOS or Linux:
bun install
bun run devFrom source, replace baked in the commands below with bun run src/boot.tsx. The desktop app has its own setup in apps/desktop.
- Open the desktop app and choose Open folder..., or run
bakedin your project folder. - Connect a model provider: in the desktop app under Settings, Providers and keys; in the terminal with
/keys, thenCtrl+Lto pick a model. - Ask for something, for example "Explain how requests are routed" or "Add a --json flag to the export command".
baked # terminal app
baked --headless "Explain this project" # one prompt, no UI
baked workflow --help # spec-driven workflows
baked doctor # check keys, models and toolsThe getting started guide covers the essentials and shortcuts; settings are in the configuration reference.
Your prompts and code go only to the model provider you choose. Anonymous usage events (version, OS, surface) are written to a local file and are not sent anywhere unless you set up a receiver; turn them off with "telemetry": false or DO_NOT_TRACK=1. Details: privacy and telemetry.
- User guide and commands and keys
- Desktop app
- Headless CLI
- Spec-driven workflows
- Providers, tools and code intelligence, extensions
- Troubleshooting
- All documentation
Checks, repository layout and developer docs
Run these before opening a pull request; CI runs the same:
bun run lint
bun run typecheck
bun run test
bun run build| Path | Purpose |
|---|---|
src/boot.tsx |
Startup and CLI routing |
src/components/, src/hooks/, src/stores/ |
Terminal UI and state |
src/core/agents/, src/core/tools/ |
Agent execution and tools |
src/core/intelligence/ |
Code graph, LSP, tree-sitter, TypeScript analysis |
src/core/llm/, src/core/prompts/ |
Providers and prompt assembly |
src/core/workflows/, src/core/specs/ |
Durable workflows and artifact validation |
src/core/memory/, src/core/sessions/ |
Persistent context and conversations |
src/headless/ |
CLI automation |
src/core/api/ |
Local workflow API (baked serve) |
apps/desktop/ |
Desktop app (Electron) |
docs/ |
Documentation |
tests/ |
Bun tests |
scripts/, packaging/ |
Build, bundle and installer tooling |
- Development guide: architecture and extension points.
- Architecture and desktop API.
- Agent instructions: conventions and checks for any coding agent working on this repository.
- Telemetry receiver: optional Cloudflare Worker that collects events.











