Skip to main content
Once your specification is ready, you choose how agents execute the work. pre.dev offers three build modes that give you different levels of control. 
  Build Next Task
> Build On Autopilot
  Chat
Agents build one task at a time, then wait for your review before proceeding.
1

Task Assigned

The next task in the spec is assigned to a build agent
2

Agent Builds

The agent implements the task in a secure sandbox
3

Verification

Acceptance criteria are verified (types, lint, tests, browser)
4

PR Opened

A pull request is opened for your review
5

You Review

Review, request changes, or approve — then click “Build Next Task” to continue
Best for: Learning how pre.dev works, sensitive codebases, and teaching the agent your preferences by reviewing early tasks.

​
Choosing a Mode

ScenarioRecommended Mode
First time using pre.devBuild Next Task
Small MVP you want fastBuild on Autopilot
Complex production appBuild Next Task (at least for Milestone 1)
Quick feature additionChat
Overnight buildBuild on Autopilot
Exploratory / learningChat

​
Mixing Modes

You can switch between modes at any time:
  • Start with Build Next Task to validate the first few PRs
  • Switch to Build on Autopilot once you’re confident the agent understands the patterns
  • Drop into Chat anytime to make a quick adjustment or ask a question

​
What Happens During a Build

Regardless of mode, each task goes through the same pipeline: 
Task → Agent codes → Verification → PR opened
                          |
                     Failed? Auto-fix
                     (loops until pass)
If acceptance verification fails (types don’t compile, tests fail, linting errors), the agent automatically iterates until the checks pass. You never see broken code in a PR.