Docs
A first look at flower: what it connects to, the words it uses, and what your first week with it looks like. The full docs come with early access.
What it connects to
flower works with the coding agents you already use: Claude Code, Codex and Pi. They reach it over MCP, the Model Context Protocol, so there’s nothing new to learn in the agent itself. It asks flower what it needs, and flower answers. flower itself is built on those same tools, which together are called polystrate. flower is one arrangement of them, and not the only one possible.
The words it uses
flower keeps to plain names. These are the ones you’ll meet:
| Word | What it means |
|---|---|
| session | One run of a coding agent, from start to finish. flower ingests its full transcript so it can be searched and picked up later. |
| brief | A piece of work, written down: what to build, how you’ll know it’s done, and the context around it. The full trail of what led to it travels with it. |
| epic | A brief made of briefs, for work too big to build in one go. |
| build | One attempt at a brief: the change, written on its own branch. |
| worker | The agent session doing a build. |
| seat | A long-lived agent session you work with directly, to plan and steer the work. |
| review | A model from a different lab reviews the build, then passes it or sends it back with the reason. |
| gate | The project’s own checks, such as its tests and its build, which must pass before a change lands. |
| standards | Rule sets you attach to a project. flower runs their checks on every build and on every landed commit, and the project’s Standards card lists what is new and what is fixed. Each check is set to report or to hold a land. |
| land | The change merges into the project’s main branch. |
| ship | The landed change moves to the branch the project deploys from, on its own or when a person says so. |
| deploy | The landed change goes live. |
| verify | After a deploy, flower checks the live site is healthy and running exactly the commit it shipped. |
In the meadow, a build is drawn as a flower: a seedling when it starts, a bud while it’s built and checked, and a bloom once its change has landed. Those are the meadow’s pictures, not more words to learn.
Your first week
- Connect your agents. Add flower to Claude Code, Codex or Pi as an MCP server.
- Work as you do now. Your sessions are ingested as they happen, transcripts and all. Ask “where did I leave off?” and see what comes back.
- Write your first brief. Say what you want built and how you’ll know it’s done; the trail of what led to it stays with it.
- Let it build. A worker builds it on its own branch; a model from a different lab reviews it; the gate checks it; then it lands and deploys. Afterwards flower verifies the live site is running the commit it shipped.
- Answer what’s asked. When something needs your call, it arrives as a question with a recommendation.
More to come
These docs are a teaser. The full docs, with setup, every option and worked examples, come with early access. See how it works, or join the waitlist.