Moving from Tasks to Mission Control

What it is

Tasks is where most people start planning; Mission Control is the full project tool. This feature is the bridge between them. It offers Mission Control only to people who already plan in Tasks — someone who just adds and ticks off a grocery list never sees the suggestion — and it carries what they already do in Tasks into their Mission Control setup without changing Tasks at all.

Where to find it

In Tasks on desktop: the Try Mission Control button sits in the Tasks header, just before the ⋯ menu, and the suggestion card appears just under the header when it is due. Neither shows on a phone or inside a popped-out Tasks window, because the Mission Control setup is a desktop sequence of dialogs. Tasks itself is still in development and behind its own Lab switch, so the whole bridge is only reachable where Tasks is.

How it behaves

The button

Try Mission Control is always there, whatever the suggestion state — "Don't suggest again" never hides it. If Mission Control is not set up yet, it starts the full move below. If Mission Control is already set up, it opens Mission Control straight to the Your tasks step, so someone who already uses Mission Control can still bring lists over or turn on the Tasks panel.

The suggestion

The card reads Ready for bigger projects? with three choices: Try Mission Control, Not now and Don't suggest again. It appears only when one of these is true:

• Real use — at least 14 days since the first task, active in Tasks on at least 7 of the last 14 days, and at least 3 different planning features used (due dates, priority, more than one list, snooze, Plan my day / Today, waiting-on, breaking a task down, AI starter sessions, time estimates).
• Heavy agent use — 15 or more sessions the person started themselves in the last 30 days (not automations, schedules or other agents), or 5 or more AI sessions started from Tasks in that time, or 80% or more of a plan's weekly limit on any account in the last 14 days. An account with no weekly bar (an own API key) counts sessions only. Heavy use can show the suggestion early, before day 14, but only once: if it is seen and not clicked, it stays hidden until 14 days after the first task.

Each answer sticks. Don't suggest again and Try Mission Control end it for good. Not now hides it for 30 days, and after that it returns only if use has grown — more planning features, or more active days in the last 14, than when they said Not now. A card that is seen and simply left alone counts as Not now. Mission Control already set up means no suggestion at all.

The move

1. Mission Control switches on.
2. The setup checklist ("In your perfect world, what would a project management tool be able to do for you?") opens with boxes already ticked and the note Ticked from how you use Tasks: any task ticks Track my own tasks, due dates tick Set due dates, attachments or context tick Attach files to tasks, and waiting-on ticks Assign tasks to people and Share work with others. Every tick can be removed. Closing the checklist marks nothing done; Mission Control's normal first-run setup takes over.
3. The checklist picks the lane (Quick start, Guided setup, or Build with your project manager). Heavy agent use moves it up one step — Quick start becomes Guided setup, Guided setup becomes the project-manager session — and never two.
4. Your tasks offers two choices, and either, both or neither may be picked:
   • Bring my lists over — pick lists; each becomes its own Mission Control project with its open tasks in To do, finished tasks in a Done group, subtasks as sub-items and due dates in a Due date column. Up to 500 tasks come over per list. Bringing the same list again never makes a second project, and a name already used gets "(from Tasks)" added. Tasks itself is only read.
   • Keep Tasks as it is, show it beside Mission Control — turns on the Tasks side panel. If a copy cannot reach Mission Control's online service, the step says so and offers Try again or Continue without them.
5. The move lands on the first project brought over, or on Mission Control Home, and then opens the chosen lane's setup.

For agents

• Rules and types: src/shared/tasks-mc-move.ts holds the real-use rule, the early-once rule, Not now, the pre-tick map and the lane bump. The contract is tasks-to-mc-move-contract.md.
• Status over the CLI: GET /tasks-v2/mc-move returns the verdict, the pre-ticks, the heavy-use flag, whether Mission Control is already set up, the saved answer state and the raw signals behind it. POST /tasks-v2/mc-move/answer records shown, not-now, never or accepted. Both routes need the full-trust CLI token; a session's scoped token is refused.
• List copy: only lists and tasks the signed-in account owns are copied; an unowned list reports failed, the same as another account's list. Each list is created through Mission Control's online service in one POST /templates/deploy-config call (a project saved only on this computer never shows in Mission Control), then mirrored locally; the list-to-project map lives in the tasksV2McCopiedLists setting.
• Usage events (feature tasks_v2): mc_move_started, mc_suggestion_shown, mc_suggestion_answered, mc_lists_brought — counts and closed enums only, never list names.

Related

• Tasks
• Mission Control
• Mission Control setup and onboarding lanes