---
title: "Autopilot"
description: "The tenth setup step: deciding whether the Project runs on its own, and activating it if so."
updated: "2026-08-18"
verifiedAgainst:
  - apps/web/lib/server/onboarding-status.ts
  - packages/shared/src/autopilot.ts
---

The last step is the one that decides whether anything happens without you.

## What you are choosing

Whether Autopilot runs for this Project, in which mode, and on what cadence.

- **Assisted** prepares work and stops for review.
- **Full** can carry a post through to publication, but only where the Content
  Direction allows it.

The difference, and what each mode will and will not do, is in
[Assisted and Full](/autopilot/modes).

## Activation is explicit

<Callout variant="danger" title="Nothing runs until you activate it">
  Creating a Project does not start Autopilot, and finishing setup does not
  either. Activation is a separate, deliberate action, and it is limited to the
  workspace owner and admins.
</Callout>

This is also why a Project can sit finished and quiet indefinitely. If you
expected posts and there are none, the first thing to check is whether Autopilot
was ever activated. See [when a run stalls](/autopilot/troubleshooting).

## What completes the step

Reviewing it. You can finish setup with Autopilot off and turn it on weeks
later.

## Next

Setup is done. [Configuration](/autopilot/configuration) covers cadence,
scheduling and limits.