Agents
Give a goal. The factory builds, reviews, and lands it.
You talk to Contrast in plain language. Behind the chat sits a factory of agents that plan, build, review, and QA real changes to your project.
What happens to a goal
- You describe the outcome to Lux in the chat.
- Lux keeps the conversation at the product level and relays the goal to the Manager.
- The Manager writes a plan and splits it into tasks.
- Builder agents take one task each, working in parallel on their own branches.
- Reviewer and QA agents check the work against the plan before it lands.
- You watch all of it in the Factory space and review the result in the same previews you edit with.
Framing goals
State the outcome and the audience, and let the factory decide the implementation. Constraints belong in the goal; solutions usually do not.
| Avoid | Instead |
|---|---|
make it better | the recipe list feels cramped on phones, give it room to breathe |
add auth with JWT and refresh tokens | people should sign in with email and stay signed in |
fix the bug | adding a recipe with an emoji in the title crashes the save button |
build the whole app | start with browsing and saving recipes, ratings can come later |
A few habits that pay off:
- One goal per message. The factory parallelizes inside a goal, so you do not need to batch.
- Name what must not change.
keep the current color schemesaves a review round. - Answer questions fast. Agents ask when a decision genuinely needs you; runs pause until you reply.
Reviewing what lands
Every factory task ends on a branch with a diff and a live preview. Approve it to merge, or send it back with a note the same way you would to a teammate. Nothing merges to main without passing review, including QA agents exercising the app.
Next
- Run the factory, the board, the floor, and steering a run in flight.
- Quick start, if you have not handed off a goal yet.