# Autopilot

Give your agent a task, follow its progress, and receive a result you can inspect.

Autopilot is the workflow of giving an agent a goal and letting it carry the work through with Indra's available tools. You provide the outcome and meaningful constraints. The agent finds the relevant context, chooses operations, handles recoverable problems, and checks the result.

## Start a task

Use the agent host in which you have [connected Indra through MCP](/docs/vision/reference/mcp-setup). Ask for a concrete result, for example:

### Agent host

> Find the current decisions about the website redesign in my connected project sources. Summarize the decisions and open questions, cite the source for each point, and leave the originals unchanged.

The agent should inspect the sources it can actually use, read the relevant evidence, and return the requested synthesis. It should recover routine context before asking you to repeat it.

For a complete example, including the terminal path you can use without an agent, follow [Run your first task](/docs/vision/autopilot/first-task).

## What runs where

Your agent host owns the conversation, plan, and any editor or terminal workspace. Indra supplies connected-source operations, stored information, browser/computer capabilities, and supported connection or sync jobs.


### Available task controls

The current operating path is the host agent plus those tools. Galaxy does not provide a working in-app task chat, and this handbook does not assume a separate Autopilot task dashboard, universal pause/resume control, or built-in coding IDE. Some Indra jobs can continue independently of a caller's wait; that does not mean every conversational task keeps running after its host stops.

[Follow long-running work](/docs/vision/autopilot/long-running-tasks) explains the status and control surfaces that are actually available.

## Choose your next guide

### [Run your first task](/docs/vision/autopilot/first-task)

See a complete research task.

### [Plan and execute a task](/docs/vision/autopilot/planning-and-execution)

Understand how a goal becomes executable steps.

### [Follow long-running work](/docs/vision/autopilot/long-running-tasks)

Check pending work or handle an interruption.

### [Continue work](/docs/vision/autopilot/context-and-continuation)

Continue in a later conversation or another host.

### [Review and deliver results](/docs/vision/autopilot/review-and-delivery)

Check and receive the output.

### [Work with an IDE agent](/docs/vision/autopilot/ide-workflows)

Use Indra alongside a coding agent.

### [Write a useful task brief](/docs/vision/autopilot/task-design)

Make the request easier to assess.

### [Evaluate task results](/docs/vision/autopilot/evaluation)

Assess whether a repeatable workflow works.

## Steer the work

You can narrow the account, change the destination, add a constraint, or ask for status while the agent works. A correction should update the affected step without discarding valid work or repeating completed writes.

If you ask the agent to stop, it should stop starting new work and explain the state of any operation already underway. The available cancellation control depends on that operation; see the long-running guide before assuming that stopping the conversation rolls back a change.

## Know when it is done

The result should let you inspect what was accomplished: cited findings, a saved file, the changed object, or a verified delivery destination. A connected account, finished tool call, or completed sync may be a prerequisite rather than the requested outcome.

If the installed capability cannot meet the intended workflow, keep the gap explicit. The handbook describes the experience Indra should support; a handbook correction can be delivered without automatically changing or releasing product code.
