# Roadmap

> The milestones Wheems is built in, what each one brings, and where version 0.0.3 sits.

Wheems is built in milestones. Each one ends with something used every day, and what's learned from using it shapes the next. Version 0.0.3 is milestones 0 to 2.

| # | Milestone | What it brings | Status |
| --- | --- | --- | --- |
| 0 | Skeleton | The CLI, config formats, driver contracts, the Herdr driver, `wheems doctor` | Done |
| 1 | Talk to one chief of staff | `init`, a workspace and its chief of staff, Slack with one session per thread, the service under launchd | Built, in daily-use testing |
| 2 | The knowledge loop | Notes, the filer, the knowledge base, search by keyword and meaning, skills proposed by agents, `wheems review`, the nightly tidy | Built, in daily-use testing |
| 3 | Approvals and updates | Buttons in Slack, the `approvals` and `updates` channels, the `ask` command, a first version of the broker | Planned |
| 4 | Projects and leads | Any body of work as a project, with its own knowledge base, a lead in its own channel, and the chief routing questions to them | Planned |
| 5 | Tasks and a team | The hand-off between agents, evaluated in code, by a judge and by you; routines; pairs; API-key accounts; a session folder per agent | Planned |
| 6 | A second workspace, kept apart | A Claude Code config folder per workspace, permission rules so one workspace can't read another, the skill budget | Planned |
| 7 | Workflows and evals | Workflows as DAGs, triggers from email and other services, classify then act, shadow mode, creating workflows by asking | Planned |
| 8 | Data and blueprints | Small data apps such as a CRM, built from a blueprint | Planned |
| 9 | Integrations, guardrails and the vault | `connect` and `grant`, the Keychain, GitHub rules, purchases you approve | Planned |
| 10 | Always on, more channels, more machines | Running on a server, laptops collecting work, `wheems node`, Telegram and email | Planned |
| 11 | Plugins and release | `make:` commands, npm plugins, the open-source release | Planned |

The Codex and opencode engines were built early, ahead of their milestones.

## Version one

Version one is done when one person runs two workspaces on it every day, one of them with at least three projects that have leads, from Slack and Telegram, across a laptop and an always-on server, with no hand-built setup.

## Until milestone 10

The service runs on your Mac, so agents answer, and workflows run, only while it's awake.

## Later than version one

Computer use on a dedicated machine, a web interface, a Teams channel, voice, hosted embeddings, several people per workspace with roles, and runtimes other than Herdr core.

## More

The full roadmap, with what each milestone is "done when", and the design of the planned parts, are in the Wheems repository: [roadmap](https://github.com/wheems-dev/wheems/blob/main/docs/roadmap.md) and [architecture](https://github.com/wheems-dev/wheems/blob/main/docs/architecture.md). The [changelog](https://github.com/wheems-dev/wheems/blob/main/CHANGELOG.md) lists what each release added.