> 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/find-and-manage-power-ups.md).

# Find and Manage Power Ups

Open **Power Ups** to discover and manage the capabilities Faros can add to your AI workflow.

## Choose a Destination

| Destination | What to look for                                          |
| ----------- | --------------------------------------------------------- |
| In use      | Capabilities already in use and skills found on this Mac. |
| Catalog     | Available Power Ups and their requirements.               |

Use the available filters to narrow the list. Click on a Power Up for its description and where it works, as well as its setup needs and controls.

## Enable a Capability

1. Find the Power Up in **Catalog** or **Recommended**.
2. Read its details and any tradeoffs.
3. Complete the offered setup or installation.
4. Choose **Turn on** or the supported mode.
5. Check the resulting status.

An installed component is not necessarily enabled, and an enabled capability may still need configuration, a compatible runtime, or sign-in. A blocked action can reflect organization policy rather than a fault.

## Review Its Effect

Use the detail panel and recorded actions to see what Faros reports. **Tokens saved**, **At API prices**, and **Possible savings** are estimates or measurements with different meanings. **Not yet** means no saving or estimate is available; it does not imply a zero-cost operation.

Grouped products can have separate components. Preparing one component does not establish that all its siblings are installed or ready.

## Related Guides

* [Autopilot and Observe](/power-ups/autopilot-and-observe.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/find-and-manage-power-ups.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.