Changelog
Customize Your Dial
Update (2026-10-23): Tune Modes now has one role per mode, Main Agent. You can no longer pin a model for the Oracle or for subagents, so the Oracle and Subagents rows in the screenshot below are gone. Task and Read Thread subagents run the same model and reasoning effort as the thread that started them. See Tune the Modes for how it works today.
You can now choose the models behind Amp's builtin modes and put your own agents on the Dial. There are two tabs in Settings → Mode Dial.
Tune Your Modes
At launch, Tune Modes had three roles per mode. Today it has only Main Agent; see the update above.
In Tune Modes, choose the model and reasoning effort for a builtin mode's main agent, Oracle, or subagents. Use it to run those models through your own API key or ChatGPT subscription. The mode keeps its prompt and tools.

Connect your key or subscription in Model Routing, then choose models it supports. You can change just the Oracle, or all three roles. Anything left on Auto follows Amp's choices as models improve.
Billing follows your provider connections.
Build Your Own Dial
If you often find yourself using custom agents you built with plugins, like a dedicated code reviewer or a security agent, you can place them on the dial too. Build Dial lets you combine the builtin modes with your agents:

Keep medium and high for building, and add a reviewer with your team's review instructions. A plugin agent can extend a builtin mode, so you only need to describe what it should do differently.
Drag two to four modes onto the dial, put them in order, and hold to save. Use the mode picker in the app or press Ctrl+S in the CLI to switch between them. Workspace admins can set a shared dial too. Your personal choices take precedence.
Make the dial yours. The docs cover both tabs.