> ## Documentation Index
> Fetch the complete documentation index at: https://docs.repl.it/llms.txt
> Use this file to discover all available pages before exploring further.

# Missions, Routines, and Tasks

> Choose a mission for a goal, a Routine for recurring work, or a task for a specific change to your project.

Use **Missions** to work toward a defined outcome, **Routines** to repeat work on a
schedule, and **tasks** to organize specific changes to a project.

| | Missions | Routines | Tasks |
| - | - | - | - |
| Best for | Achieving a goal with agreed success criteria | Repeating work on a schedule | Making a specific project change |
| What you define | Goal, approach, success criteria, budget, and boundaries | Instructions and a recurring schedule | The change you want and its plan |
| Where you manage it | In a chat | In a chat and the Routines sidebar | In your project's task board and task chats |
| How you review results | Review the mission's deliverable and completion report | Review the result of each scheduled run | Review and apply the task's changes |

On this page, **tasks** means Replit's project task system, not a general request
in a chat or a task in a connected service.

## Choose a mission for a goal

A mission keeps a goal attached to a chat across turns and sessions. You and
Replit agree on what success looks like before work begins. Replit uses that
agreement to guide its work and evaluate the result.

Choose a mission when the outcome matters more than a fixed sequence of steps.
The approach may need to change as Replit learns, but the agreed success criteria
provide a target.

For example:

> “Fix these 25 problems reported by my customers. Test each fix and summarize
> anything that still needs attention.”

A mission does not repeat on a schedule by default. It may wait and resume while
working toward its goal. Reaching its budget can stop work before the goal is
achieved.

See [Missions](https://docs.repl.it/features/chats-and-routines/missions.md) for setup, progress, and
completion.

## Choose a Routine for recurring work

A Routine repeats instructions on a schedule and returns each result to its
chat. Choose a Routine when you need the same kind of work done regularly,
rather than once.

For example:

> “Every Monday morning, summarize new customer feedback and group it into bugs,
> feature requests, and questions.”

Finishing one run does not finish the recurring schedule. You can review the
results, adjust the instructions, or delete the Routine when you no longer need
it.

See [Run routine tasks](https://docs.repl.it/chat/routines.md) for scheduling, budgets, and management.

## Choose a task for a project change

A task is a defined piece of work in your project. Replit can divide a larger
request into tasks so you can review each piece separately.

For example:

> “Add a confirmation message after a customer submits the feedback form.”

Background tasks work in isolated copies of your project. When a task is ready,
you review its changes and choose whether to apply them to your main version.
This makes tasks useful for organizing app changes and keeping unfinished work
separate from the version you are using.

See the [Task system](https://docs.repl.it/core-concepts/agent/task-system.md) for planning, execution,
and review.

## Use them for different parts of your work

These features answer different questions:

* **Missions:** What outcome are you trying to achieve?
* **Routine:** What work needs to happen again, and when?
* **Task:** What specific project change should be made and reviewed?

You might use a Routine to collect customer feedback each week, a mission to
address a defined set of problems, and project tasks to organize individual
changes. Each has its own setup and review process; creating one does not
automatically create the others.
