Chat
- ◈ Chat with any configured AI model
- ◈ Persistent history per workspace and session
- ◈ Baker agent mode — AI that acts, not just responds
- ◈ CLI destinations — route to Claude Code, Aider, local tools
How it works
The CLI
The CLI
is the product.
baker is what you install and run. It connects to an instance — your own server or the hosted one — and talks to whatever AI models you configure. Everything else is infrastructure.
Three steps
Install baker. Run baker. It handles the rest — setup, instance, everything.
01
Install the CLI
One command. Requires Node.js 18+. Works on macOS, Linux, and Windows.
$ npm install -g @openbaker/cli ✓ baker v0.5.0 installed
02
Run baker
First run detects that nothing is configured and asks what you want to do. Pick new instance to set one up, or connect if you already have one. The CLI handles everything from there.
$ baker No instance connected. Let's get you set up. ? What do you want to do? ✓ New instance Connect
03
Work
Chat with models, manage tasks, run scheduled automations. All state lives on the instance — pick up where you left off from any machine.
$ baker chat ✓ claude-opus-4 / workspace: dev baker › summarize open tasks
What baker does
The CLI is the interface. The instance is the memory. The models are whatever you connect.
Manage
- ◈ Tasks with priority, due dates, and project grouping
- ◈ Workspaces to separate contexts (work, personal, client)
- ◈ Notes attached to workspaces
- ◈ Scheduled prompts on a cron interval
Automations
Schedule any prompt on a cron interval. The instance runs it while your terminal is closed. Results land in workspace history.
Examples
- ◈ Daily standup — summarize open tasks at 9am
- ◈ Weekly digest — compile progress across workspaces
- ◈ Monitoring — pipe log output into a prompt
- ◈ Research — same prompt against updated context
$ baker schedule create \ --prompt "Summarize open tasks" \ --every "0 9 * * 1-5" ✓ Created: standup-summary $ baker schedule list standup-summary 0 9 * * 1-5 active
Instances
An instance is a server that stores your workspaces, sessions, tasks, and encrypted API keys. The CLI connects to it. You need exactly one. Baker sets it up.
Hosted (app.openbaker.org)
We run the server. You bring your API keys. Early access is invite-only — your invite includes a token. Select New instance → Hosted and paste it in.
$ baker ? What do you want to do? New instance ? What type of instance? Hosted ? Paste your invite token: ············ ✓ Connected to app.openbaker.org
Self-hosted (your server)
Baker pulls the image, generates your config, starts the container, and creates your admin account. Requires Docker. Your data never leaves your machine.
$ baker instance new ? What type? Self-hosted ? Where? This machine ✓ Docker found ✓ Image pulled ✓ Instance started (localhost:3000) ✓ Connected
◈ See the Instances page for full options — local Docker, remote server, and a comparison table.
Models & providers
You configure providers once on the instance. After that, you pick a model per session. Keys are stored encrypted on the instance and never logged.
API providers
- ◈ OpenAI — GPT-4o, o1, o3
- ◈ Anthropic — Claude Opus 4, Sonnet 4, Haiku
- ◈ GitHub Models — via Azure endpoint
- ◈ Any OpenAI-compatible endpoint
CLI destinations
- ◈ Ollama — local models, no key needed
- ◈ Claude Code — route directly to claude CLI
- ◈ Aider — pair programming in the terminal
- ◈ GitHub Copilot CLI