Skip to main content
Revolte runs on its own between fixed checkpoints. You define the work, approve the plan and review the result. Between those points the agent understands the codebase, plans, writes and tests code and opens the pull request, even while you work on something else.

The three checkpoints

What runs without you

  • Reading and understanding your codebase
  • Building the plan
  • Writing and testing code in an isolated sandbox
  • Opening the pull request
  • Running your build and deployment pipeline
A workflow can continue while your team is offline and pauses only where a person has to decide. When you respond, it resumes.

Oversight at every stage

Every session keeps its plan, reasoning, generated code, execution history, approvals, pull requests and deployments. You can inspect, pause, resume or step in at any stage. See Review the execution plan and Review code changes.

Where you set the controls

What always needs a person

Two things always involve a person, whatever the execution mode: you approve the plan before Revolte writes code, and you review the code and merge it. Pipelines can also require a manual approval gate before a deployment reaches a sensitive environment such as Production. See Pipelines and approvals.