← All Docs

Features & Roadmap

Copilot & Autopilot

Copilot and Autopilot are two AI-assisted modes that help you build your app faster. Copilot gives you control with AI suggestions you approve, while Autopilot lets the AI work through your feature list independently.

Copilot Mode

In Copilot mode, the AI suggests changes and you decide whether to apply them. It is a collaborative workflow where you stay in control while benefiting from AI speed and expertise.

1

AI Proposes a Change

The AI analyzes your app and the current feature being worked on, then proposes specific code changes. You see a clear description of what it wants to do before any files are modified.

2

You Approve or Reject

Review the proposed changes. If they look good, click Approve to apply them to your source files. If not, click Reject and provide feedback so the AI can try a different approach.

3

Preview Updates Automatically

After you approve changes, the preview panel refreshes automatically. You can verify the result visually and interactively before the AI moves on to the next change.

When to use Copilot: Copilot is ideal when you want to stay closely involved in the development process, review each change before it is applied, or when working on sensitive parts of your app where you want full control.

Autopilot Mode

Autopilot mode lets the AI work through your feature list on its own. It picks up features from your backlog, implements them one by one, and moves on — all without requiring your approval at each step.

1

Enable Autopilot

Activate Autopilot mode from the Application Editor. Make sure your feature list is populated with the features you want built — the AI works through them from top to bottom.

2

AI Implements Features

For each feature, the AI reads the title, description, and acceptance criteria, then makes the necessary code changes. It updates the feature status to "in progress" while working and "done" when complete.

3

Review When Ready

Come back when the AI is done and review all the changes at once. Check the pilot history to see what was implemented, then make adjustments through chat if anything needs tweaking.

When to use Autopilot: Autopilot works best when you have a well-defined feature list with clear acceptance criteria and want to save time by letting the AI work independently. It is great for batch work on straightforward features.

Pilot History

Both Copilot and Autopilot maintain a complete history of actions taken. The pilot history shows:

  • Which features were worked on — Each entry links to the specific feature that was being implemented.
  • What changes were made — A summary of the files modified and the nature of the changes.
  • Status outcomes — Whether the feature was successfully implemented or encountered issues that need attention.
  • Timestamps — When each action was taken, so you can track the AI's progress over time.

You can access the pilot history at any time from the Application Editor to review past work or understand what changes were made to your app.

Switching Between Modes

You can switch between Copilot and Autopilot at any time, or pause Autopilot to review progress before resuming. There is no penalty for switching — your feature list and history are preserved.

Best Practices

  • Define features clearly before using Autopilot. Well-written titles, descriptions, and acceptance criteria lead to better implementations.
  • Start with Copilot on a new app to understand how the AI approaches your project before switching to Autopilot.
  • Use Autopilot for batch work when you have several straightforward features to implement quickly.
  • Review Autopilot results as a batch. Let the AI work through several features, then review everything at once for efficiency.
  • Run an evaluation after an Autopilot session to catch any quality issues across all the changes made.