Skip to content
Gulliby-developmentPublic

About

No description, website, or topics provided.

Resources

Contributing

Stars

2 stars

Watchers

0 watching

Forks

Repository files navigation

BAKED

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.

The first 22 seconds of the BAKED promo: an idea is typed into the coordinator, which splits it into two parallel runs

▶ Watch the full 88-second video with sound

Status: pre-release. Releases are published on GitHub only, not on npm.

What you can do with it

  • 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

The coordinator proposes splitting an idea into two parallel runs
Coordinator. Describe an idea; it proposes a split, launches the runs and tracks them on the right.
The Workflows screen: the sdd conveyor and the built-in workflows
Workflows. Watch how a run moves station by station, or open a workflow in the editor.
Workflow runs on their lines, two waiting for approval
Workflow runs. Every stage on one line; the run waits for you only where it has to.
The Git screen: changes, commit box, branches and the commit graph
Git. Changes, commit, push and pull, branches by kind and the commit history.
The permission menu of a chat: Manual, Auto, Full access
Permission modes. Manual asks for every edit and command, Auto asks only for risky ones, Full access asks for nothing.
The mode menu of a chat: Default, Architect, Plan first
Agent modes. Default edits and runs, Architect stays read-only, Plan first proposes a plan before acting.
An initiative split into features with their state and budget
Initiatives. A big idea as features, each with its own run, size and state.
The code graph of the BAKED repository
Code graph. Folders, key files and the links between them.
A BAKED chat: the agent explains a bug, shows its diff and the test it ran
Chat. Every edit as a diff, every tool call on its own line, and undo for any turn.
Needs you: approvals and questions from every open project
Needs you. Approvals and questions from every open project in one list.
Usage: tokens and cost by stage and by model
Usage. Tokens, cache hits and cost by stage and by model.

Screenshots show the desktop app in its dark theme with sample data.

Install

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.sh from the extracted archive installs to ~/.baked/bin. On Windows you can also extract baked-<version>-windows-x64.zip and run baked.exe.
  • Each release lists SHA256SUMS.txt for the archives.
Run from source

Use Bun 1.3.13 or newer on Windows, macOS or Linux:

bun install
bun run dev

From source, replace baked in the commands below with bun run src/boot.tsx. The desktop app has its own setup in apps/desktop.

Get started

  1. Open the desktop app and choose Open folder..., or run baked in your project folder.
  2. Connect a model provider: in the desktop app under Settings, Providers and keys; in the terminal with /keys, then Ctrl+L to pick a model.
  3. 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 tools

The getting started guide covers the essentials and shortcuts; settings are in the configuration reference.

Privacy

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.

Documentation

Contributing

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

License

MIT

About

No description, website, or topics provided.

Resources

Contributing

Stars

2 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages