Glossary
The product uses a specific vocabulary. This page defines each term as it is used in the interface and in this documentation.
Project
Section titled “Project”A backend system being designed and built. A project owns its services, its system design, and every session that works on it.
Session
Section titled “Session”A unit of work on a project, seeded from the project’s merged state. A session holds one or more conversations and owns exactly one change set. It becomes read-only once that change set merges.
Conversation
Section titled “Conversation”A single chat thread inside a session, with its own mode. A session can hold several conversations — one to build, another to fix what review found — and all of them land in the same change set.
Change set
Section titled “Change set”The group of pull requests a session produced — one per service touched, plus the system design. A change set merges as one unit once every pull request is approved.
Service
Section titled “Service”One deployable unit of the backend. A service has its own repository, its own specification, its own tests, and its own container image.
System design
Section titled “System design”The whole-system architecture document: which services exist, what each owns, and how they communicate, with an overview diagram of the whole system. Produced in the architecture step.
Specification
Section titled “Specification”The document set for one service: architecture, OpenAPI contract, user stories, engineering guide, decision records, and a diagram of that service’s internals. Produced in the specification step.
Implementation
Section titled “Implementation”The source code, tests and diagram for one service, delivered as a pull request. Produced in the implementation step.
Workflow step
Section titled “Workflow step”One of the three phases every project runs: Architecture, Specification, Implementation. Architecture runs once; the other two run once per service.
Plan mode
Section titled “Plan mode”A per-step setting that pauses the workflow to present a plan for approval before the work is done.
Steering
Section titled “Steering”Sending a message to a paused run to revise its plan. Steering is how you correct intent before work happens.
Provider research
Section titled “Provider research”The agent’s investigation of external services it does not build itself — authentication, email, media — producing a comparison and a recommendation.
Credit
Section titled “Credit”The unit of billing. Each run has an estimated credit cost, shown before you commit to it. The estimate is a best-effort upper bound; actual cost is usually lower.
Credits reserved while a run is in progress. Adjusted using a data-driven analysis of comparable runs so the reservation is fair. Released in full if the run fails; converted to a charge at the actual cost if it succeeds.
Queued
Section titled “Queued”A run that is ready but cannot start because the available balance is negative — usually because holds from runs already in flight exceed what is left. Queued runs resume automatically once the balance is positive.
Todo list
Section titled “Todo list”The per-run progress list published by the agent. Items are marked done only when their acceptance criteria are supported by evidence.
Live activity
Section titled “Live activity”The real-time feed of the agent’s reasoning steps and tool calls during a run.
Thread
Section titled “Thread”The conversation view for one service, separate from the global thread. Each service’s specification and implementation can be followed in isolation.
State tab
Section titled “State tab”The workspace view showing the system design, the diagram, and the change set with its pull request links.
Code tab
Section titled “Code tab”The workspace view showing the diff for each pull request in the change set.
Abandon
Section titled “Abandon”Discarding a change set: closes every open pull request and makes the session read-only. Not reversible.
Discarding the current conversation and starting a new one in the same session. Keeps the session, its change set and any generated work. Not available once a workflow has been triggered.