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

# Tasks in Mission Control

export const AIAgents = () => <>the <strong>AI Agents</strong> icon <span style={{
  whiteSpace: "nowrap"
}}><img src="/images/global-nav/ai-agents.png" width="20" height="20" style={{
  verticalAlign: "text-bottom",
  display: "inline",
  margin: "0 1px"
}} /></span></>;

export const context_engine = "Context Engine";

export const designer = "Designer";

export const mission_control = "Mission Control";

export const maia_team = "Maia Team";

export const maia = "Maia";

Mission Control lets you create tasks for Maia Team to work on across any of your projects without needing to switch between projects. The Mission Control board provides you with an overview of all the tasks that you've given Maia Team—this allows you to track Maia Team's progress and provide additional responses to inform its work. When you're talking to Maia Team about a task in Mission Control, each task has its own chat panel. You can switch between tasks and conversations without losing the context of your existing chats with Maia Team.

This guide explains how to create, work on, and edit tasks in {mission_control}. For an overview of {mission_control}, task statuses, and the different view options, read [{mission_control} overview](/docs/guides/mission-control). To learn about using {mission_control} alongside other tools, read [{mission_control} integrations](/docs/guides/mission-control-integrations).

To access {mission_control}, in the left navigation, click <AIAgents />, then **{mission_control}**.

<Note>
  {mission_control} is only visible in the left navigation if the [**Enable AI Agents** permission](/docs/administration/manage-accounts#edit-account-details) is enabled for your account.
</Note>

***

## Creating tasks

{maia_team} creates a new [branch](/docs/guides/branches) for each task in {mission_control}. When creating a task, select any existing branch in your project from the **Branch** drop-down to tell {maia_team} to use it as the base for the new task branch. Once a branch has been created, you can see it in your {maia} project and open it in {designer} to see the work that {maia_team} has done so far.

To create a new task, either in the backlog or for immediate action:

1. Open the **New task** dialog:
   * In [List view](/docs/guides/mission-control#list-view), click the **Add** drop-down, then click **Add task**.
   * In [Kanban view](/docs/guides/mission-control#kanban-view), click **Add task** in the **Backlog** column.
2. In the **Project** drop-down, select the project in which you want to work on this task.
3. In the **Branch** drop-down, select the branch that you want {maia_team} to use as the base for this new task.
4. Select the **Create new branch** checkbox if you want {maia_team} to create a new branch for this task, based on the branch you selected. If you don't check this box, {maia_team} will work on the task in the branch you selected.
5. In the **Environment** drop-down, select the environment you want to use as your data warehouse connection.
6. In the **Label** drop-down, select up to five labels to add to this task. To create a new label and add it to this task, enter the new label name and click **Create**.
7. In the **Priority** drop-down, select a priority level for this task: **Low**, **Medium**, or **High**. This is shown on the {mission_control} board and determines when {maia_team} will start working on this task when [Auto-start](/docs/guides/mission-control#auto-start) is enabled.
8. In the **Knowledge Graph** drop-down, select the knowledge graph you want to use for this task. This is the knowledge graph that {maia_team} will use to inform its work on this task. Knowledge graphs are a way to organize and represent information about your data, projects, and workflows, and selecting the most relevant knowledge graph helps {maia_team} to work more effectively on your task. Read [{context_engine}](/docs/guides/context-engine) to learn more.
9. In **Prompt**, describe the task that you want {maia_team} to complete for you. The following controls are also available in the prompt area:
   * Click **+** to [attach an image or PDF](#attaching-images-and-pdfs) and give {maia_team} additional context.
   * Click **@** to reference an attached file in your prompt.
   * Click **Mode: Act** to select whether {maia_team} should work on this task in [plan mode](/docs/guides/maia-sessions-and-tools#plan-mode).
   * Click **Ask permission** to select a [permission level](#permission-levels). **Ask permission** is selected by default. If you select **Full access**, click **Bypass permissions** in the confirmation dialog to confirm that you do *not* want {maia_team} to ask for permission before performing actions.
10. Select one of the following options:
    * Click **Create** to add the new task to the backlog without working on it.
    * Click **Start task** to tell {maia_team} to start working on it immediately.

Your new task appears in the **Backlog** section. If you clicked **Start task**, the task automatically moves to the **In progress** section (if you don't already have 10 tasks in progress) once {maia_team} has finished creating the task and assigning it a title.

***

## Working on tasks

The process of working on a task in {mission_control} is made up of four steps:

1. Tell {maia_team} to start working on a task.
2. Monitor the task and provide any additional information that {maia_team} needs. You may need to do this multiple times, particularly for complex tasks.
3. Review {maia_team}'s work in {designer}.
4. Move the task to the **Completed** section once you're happy with the finished product.

### Starting a task

If you click **Start task** when creating a task, {maia_team} begins working on this task immediately.

To tell {maia_team} to start working on a task in the **Backlog** section, click the task. In the **Edit task** dialog, click **Start task**.

### Monitoring a task in progress

While a task is in the **In progress** section, click the task to open the {maia_team} chat panel about this task. Here, you can:

* See {maia_team}'s progress on the task
* Send a follow-up message to give {maia_team} additional information
* Switch to [plan mode](/docs/guides/maia-sessions-and-tools/#plan-mode).

<Note>
  A maximum of 10 tasks can be in progress at any time. When there are already 10 tasks in the **In progress** column, the following restrictions apply:

  * **Creating a new task:** You cannot create a new task and tell Maia Team to start working on it immediately. You can create the task, but it will be added to the **Backlog** column.
  * **Starting an existing task:** You cannot tell Maia Team to start a task in the **Backlog** column. The task will remain in the **Backlog** column.
  * **Responding to Maia Team:** Responses to questions from Maia Team about tasks in the **Needs attention** column will not be processed, because Maia Team cannot continue working on the task.

  To perform any of these actions, you need to wait until fewer than 10 tasks are in progress. You can then tell Maia Team to start a task or respond to a question. If doing this means there are 10 tasks in the **In progress** column again, the same restrictions will apply until fewer than 10 tasks are in progress.
</Note>

### Responding to Maia Team

When {maia_team} requires information from you to work on a task, the task moves to the **Needs attention** section. Click a task to open the chat panel about this task and provide the required information.

{maia_team} may ask for input in a range of situations, including:

* Asking what you'd like a new table to be called.
* Checking the authentication method you want to use when configuring a connector.
* Asking whether you want to use hardcoded values or a project or pipeline variable.

After you answer any outstanding questions, the task automatically moves back to the **In progress** section until either more information is needed or the task is completed.

### Reviewing Maia Team's work in Designer

You can review the work that {maia_team} has done when the task is in the **In progress** or **Needs attention** section.

To do this, click the task to open the {maia_team} chat panel about this task, then:

* If the task is in the **In progress** section, in the top right, click **Open in {designer}**.
* If the task is in the **Needs attention** section, at the bottom of the chat, click **Review in {designer}**.

This opens the branch created for this task in {designer}. Your conversation with {maia_team} also opens, so you can continue the conversation from {mission_control}. You can work on the branch in {designer} and then return to {mission_control}—{maia_team} is aware of any changes you've made.

### Completing a task

After you've reviewed the work and are happy with the finished product, mark the task as **Completed** in {mission_control}. To do this, click the task to open its chat panel, then click **Move to completed**.

Completed tasks stay in the **Completed** section of your {mission_control} board until you delete them, or until the **Period** drop-down filters them out. To remove a task from the **Completed** section, [delete the task](#deleting-tasks).

<Note>
  Completing a task in {mission_control} does *not* make any changes to the task branch, or make these changes visible on any other branches. To see these changes in your project, you need to commit, push, and merge the changes from the task branch to the source branch.

  First, [commit](/docs/guides/git-commit) and [push](/docs/guides/git-push) the task branch changes. You can tell {maia_team} to do this in your conversation in {mission_control} or {designer}, or you can do this yourself in {designer}.

  Next, [merge](/docs/guides/git-merge) the changes from the task branch to the source branch in {designer}. {maia_team} can't merge changes—this ensures that only reviewed, approved work is merged to your source branch.
</Note>

***

## Editing tasks

You can change the name, labels, permission level and mode (**Act** or **Plan**) of any task on your {mission_control} board, regardless of its status.

You can only edit the other configuration options of a task when that task is in the **Backlog** section of your {mission_control} board. While a task is in the **Backlog**, you can update its priority level, prompt, or knowledge graph before {maia_team} starts working on it.

### Renaming tasks

To rename a task, hover over the task on your {mission_control} board and click the pencil icon next to the task's name. Enter a new name, and then press `Enter` or click outside the name field to save your changes.

### Editing tasks in the Backlog section

To change the priority level of a task in the **Backlog** section of your {mission_control} board:

1. Click the drop-down showing the task's current priority level.
2. Select a new priority level. This change takes effect immediately.

To edit any other configuration options of a task in the **Backlog** section:

1. Click the task to open the **Edit task** dialog.
2. Make the required changes to the task, as described in [Creating tasks](#creating-tasks).
3. When you're finished, either:
   * Click **Update** to save your changes and leave the task in the **Backlog** section.
   * Click **Start task** to save these changes and tell {maia_team} to start working on the task (if 10 tasks are not already in progress).

### Editing tasks in other sections

To edit a task in any other section of your {mission_control} board:

1. Click the task to open the {maia_team} chat panel.
2. To change the task's [permission level](#permission-levels) or [mode](/docs/guides/maia-sessions-and-tools#plan-mode), click the current permission level or mode at the bottom of the chat panel and select a different permission level or mode.
3. To change the task's labels:
   1. Click the three vertical dots in the top right corner, then click **Edit task**.
   2. In the **Label** drop-down, select up to five labels for this task:
      * Select a label to add it to this task.
      * Deselect a selected label to remove it from this task.
      * Type the name of a new label and click **Create** to add a new label to this task.
   3. Click **Finish**.

Changes to a task's permission level and mode are saved immediately. Changes to a task's labels are saved when you click **Finish**.

***

## Attaching images and PDFs

When creating or editing a task, you can attach images and PDFs to the task prompt to give {maia_team} additional context. {maia_team} can read the content of your attachments directly and use them to inform its decisions.

You can attach up to five files to each task, provided they meet the following conditions:

* **Images:** `JPEG`, `PNG`, `GIF` or `WebP` files
  * Maximum file size per image file: 5 MB and 8000 x 8000 px
  * Example files: Diagrams, screenshots, mockups, and whiteboard photos
* **PDFs:** Standard `PDF` files
  * Maximum upload size across all attached `PDF` files: 32 MB and 100 pages
  * Example files: Specifications, requirements documents, and reports

<Note>
  Text files (`.txt`, `.md`, etc.) aren't supported as attachments. These file types belong in the project itself, where Maia Team can already read them.
</Note>

To attach a file to a task:

* When creating a task, in the **Prompt** field, click **+**, then click **Attach to conversation**, and then select the file you want to attach.
* When chatting to {maia_team} about a task in the **Needs attention** section, click **+** in the chat panel, then click **Attach to conversation**, and then select the file you want to attach.

***

## Permission levels

In {mission_control}, you grant {maia_team} a specific permission level for each task, depending on how independently you want it to work. You can select a permission level when [creating a task](#creating-tasks) and change the permission level granted for a task by [editing the task](#editing-tasks).

Select the appropriate permission level for the task you've asked {maia_team} to perform, as described below:

* **Ask permission:** This is the default permission level for tasks in {mission_control}. When set to this level, {maia_team} pauses and asks for permission before doing anything other than reading and editing files in your project. Use this level when you want to monitor {maia_team}'s work on a task in detail.
* **Balanced:** When set to this level, {maia_team} makes read-only queries, samples data in your project, and makes reversible changes without asking you for permission. It still asks for permission before pushing any changes and running pipelines. Use this level when you're confident that {maia_team} is working on a safe task that you're happy to check less often.
* **Full access:** When set to this level, {maia_team} never asks for permission before performing an action. Only use this level for trusted, hands-off tasks such as prototyping or clearing a backlog in a sandbox environment, and make sure that you have scoped your environment accordingly.

<Note>
  If {maia_team} thinks your task is particularly complex, it will automatically suggest switching to [plan mode](/docs/guides/maia-sessions-and-tools#plan-mode), even if you select **Full access** permissions. This provides you with extra visibility and control over {maia_team}'s suggested actions when working on complex prompts, and enables you to suggest changes to {maia_team}'s approach before any work is performed.
</Note>

***

## Deleting tasks

<Warning>You can't restore a task that has been deleted.</Warning>

You can only delete tasks from the **Backlog** and **Completed** sections of your {mission_control} board. You can't delete tasks that {maia_team} has started working on.

To delete a task, hover over the task and click the **Delete** icon in the top right of the task. In the **Delete task** dialog, click **Delete**.