Amp

Amp CLI support for teams already operating in Amp-centered coding loops.

Agent guide

Amp is useful when a team already has Amp in the toolchain and wants Conductor to route those repositories through a native plugin instead of a shell-level workaround.

Binary: ampAliases: amp, amp-cliBest for team-specific toolchains

Primary binary

amp

Known aliases

amp, amp-cli

Good fit

Alternate runtime choice, team-specific toolchains, and plugin-native dispatch.

​

Set up Amp in Conductor

1. Install Amp CLI

   # install Amp CLI in your environment
   
2. Complete any vendor setup

   Finish authentication or local environment setup required by the Amp CLI before launching Conductor.

3. Launch Conductor

   npx --yes --registry=https://registry.npmjs.org conductor-oss@latest
   

   Add the workspace and choose Amp as the default only for the repositories that genuinely need it.

4. Configure the project default

   projects:
     my-app:
       agent: amp
   

​

Model selection in Conductor

Amp keeps its own provider and model configuration.

• leave agentConfig.model unset when Amp should inherit its current default or profile-selected model
• add a repo-level override only if your Amp workflow supports it and the project needs one fixed target
• use Conductor to route work to Amp per repository instead of micromanaging models in every task

​

Why teams pick Amp

• keeps an Amp-heavy repo inside the same orchestration surface
• avoids shell-wrapper drift
• useful when only part of the fleet should route through Amp