Tools

Amp runs tools and shell commands on your behalf to inspect code, run tests, and iterate quickly.

By default, Amp does not ask for approval before running tools.

Amp acts on content in your workspace. Untrusted repositories, MCP servers, and other external inputs can influence what Amp does. If you regularly work with untrusted sources, consider creating a custom policy plugin, or using an isolated development environment.

Built-in Tools

You can see Amp’s builtin tools by running amp tools list in the CLI.

Oracle

Amp has access to a powerful “second opinion” model that’s better suited for complex reasoning or analysis tasks, at the cost of being slightly slower, slightly more expensive, and less suited to day-to-day code editing tasks than the main agent’s model.

This model is available to Amp’s main agent through a tool called oracle. The oracle’s routing depends on the agent mode, connected model provider subscriptions, workspace restrictions, and model availability. The oracle runs with extra-high reasoning. In high mode, the main agent uses GPT-6 Astra with medium reasoning and the oracle uses Claude Fable 5.1. In low and ultra modes, the oracle uses GPT-6 Astra; in medium, GPT-5.6 Sol. When you connect a ChatGPT subscription, the high oracle uses GPT-6 Astra instead, and so does the medium oracle on plans that include GPT-6 Astra (see The Dial). See Models for the current routes. These mappings can change as Amp evaluates new models.

The main agent can autonomously decide to ask the oracle for help when debugging or reviewing a complex piece of code. We intentionally do not force the main agent to always use the oracle, due to higher costs and slower inference speed.

We recommend explicitly asking Amp’s main agent to use the oracle when you think it will be helpful. Here are some examples from our own usage of Amp:

Use the oracle to review the last commit's changes. I want to make sure that the actual logic for when an idle or requires-user-input notification sound plays has not changed.
Ask the oracle whether there isn't a better solution.
I have a bug in these files: ... It shows up when I run this command: ... Help me fix this bug. Use the oracle as much as possible, since it's smart.
Analyze how the functions `foobar` and `barfoo` are used. Then I want you to work a lot with the oracle to figure out how we can refactor the duplication between them while keeping changes backwards compatible.

See the GPT-5 oracle announcement for more information.

Librarian

Amp can search remote codebases with the use of the Librarian subagent. The Librarian can search and read all public code on GitHub as well as your private GitHub repositories.

Tell Amp to summon the Librarian when you need to do cross-repository research, or, for example, when you want it to read the code of the frameworks and libraries you’re using. The Librarian’s answers are typically longer and more detailed as we built it to provide in-depth explanations. The Librarian will only search code on the default branch of the repository.

You might need to prompt the main agent explicitly to use the Librarian. Here are some examples:

Explain how new versions of our documentation are deployed when we release. Search our docs and infra repositories to see how they get to X.Y.sourcegraph.com.
I have a bug in this validation code using Zod, it's throwing a weird error. Ask the Librarian to investigate why the error is happening and show me the logic causing it.
Use the Librarian to investigate the `foo` service - were there any recent changes to the API endpoints I am using in `bar`? If so, what are they and when were they merged?

See the Librarian announcement for more information.

GitHub

To let the Librarian read your private repositories, connect GitHub in your integration settings and include those repositories when you choose which ones Amp may access. See GitHub & Git for the details.

Painter

Amp can generate and edit images using the Painter tool, powered by GPT Image 2.5 Sunburst.

Ask Amp for UI ideas or ask it to use Painter explicitly to generate or edit an image. You can also provide up to 3 reference images for style guidance or editing by @-mentioning image files in your prompt. Say what to keep from each reference and what may change.

See Designing UI With Amp for a workflow that starts with a screenshot, compares layouts, and refines a chosen design before implementing it. Painter generates one image per call; Amp can request several variants in one image or make separate calls.

For an isolated asset that will sit over existing content, such as a logo or sprite, ask for a transparent background. Painter supports transparent PNGs for generation and editing. Amp sets the tool’s background option to transparent; requesting transparency only in the image prompt is not reliable. Amp should check the PNG’s alpha channel and inspect it on light and dark backgrounds before delivering it.

Use Painter to make a cobalt-blue paper-airplane icon with a transparent background and no shadow. Check that the PNG has transparency and show it on light and dark backgrounds.

Keep an opaque background for a complete composition, such as a UI mockup or poster. An app icon with its own designed background should also stay opaque. You can request either background type; otherwise Painter uses auto.

See the Painter announcement for more information.

Permissions

Amp does not ask for approval before running tools.

Use a custom plugin to control tool use. Workspace admins can distribute it as a global workspace plugin.