> For the complete documentation index, see [llms.txt](https://docs.desktop.faros.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.desktop.faros.ai/power-ups/autopilot-and-observe.md).

# Autopilot and Observe

Power Ups use controls appropriate to their capabilities. Some offer two modes - **Observe** and **Autopilot**, while others have a simpler on/off control.

## Choose a Mode

| Mode      | Meaning                                                                                                       |
| --------- | ------------------------------------------------------------------------------------------------------------- |
| Observe   | Review the observations or recommendations supported by that Power Up without granting its automatic actions. |
| Autopilot | Allow the qualified automatic actions described for that Power Up, subject to its prerequisites and policy.   |
| Off       | Disable the capability through its available control.                                                         |

Autopilot is controlled **per Power Up**. There is no app-wide Autopilot switch.

## Enable Autopilot Deliberately

1. Open the Power Up's detail panel.
2. Read what it can change, where it applies, and any prerequisites.
3. Choose Autopilot if offered and appropriate.
4. Review recorded actions and resulting measurements.

A mode selection is not proof an action has run. The Power Up may be waiting for suitable activity or a required connection. Advisory-only recommendations still need you to act.

## Understand Its Boundaries

Autopilot does not grant unrestricted permission to every installed skill or integration. Model settings changes, repository refreshes, task delegation, installation, and external collaboration have their own requirements.

Changing a mode does not erase earlier actions or retract instructions that an AI tool has already loaded. Restart the affected tool's session when setup instructions require it.

If a control is managed by your organization, its policy determines whether you can change it.

## Related Guides

* [Review Recommendations and Changes](/for-you/review-recommendations-and-changes.md)
* [Optimizations](/power-ups/optimizations.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.desktop.faros.ai/power-ups/autopilot-and-observe.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.