Autopilot and Packs: recurring work on a schedule and a budget

Autopilot runs the recurring tasks on a schedule you set — visibility runs, score refreshes, the checks that only earn their keep when they happen regularly. You decide what runs and when; Autopilot decides nothing about content, it only keeps the clockwork turning.

The budget is a wall

Every scheduled AI task respects the monthly budget from your usage settings, and the stop is hard: when the budget is reached, Autopilot halts and says so — it does not finish "just this one run" first. A schedule you set in January cannot surprise you in March.

Packs: curated batches

Packs are curated bundles of tasks — "Add all missing meta descriptions" is the classic — that run as a batch with a preview. You see every proposed change before it lands, accept or reject per item, and nothing is published without your confirmation. A Pack turns an afternoon of repetitive edits into one reviewed batch.

When to use which

Autopilot is for measurement and upkeep — things worth repeating. Packs are for the backlog — things worth doing once, at scale. Both leave the publish button where it belongs: with you.