Amp Guide
A coding agent spanning terminal sessions, hosted environments and shared threads.
Last verified: · How we verifySuitable workflows
Teams moving between local work and long-running tasks in hosted Orbs.
Limitations and billing
Agent usage and Orb compute have separate allowances; Windows terminal use requires WSL.
Capabilities we verified
This is an evidence-based shortlist, not an exhaustive feature inventory. Omitted capabilities have not been checked for this record.
Pricing & usage
See official pricing
Plan allowance, usage credits and separate hosted compute. The cost of metered usage or an external agent can be separate from the subscription.
Check official pricing ↗Models & access
Amp routes work across models and supports configured subscriptions or provider keys.
Verified families: Claude, GPT.
Official model information ↗Install and start the CLI
macOS, Linux or Windows through WSL.
Installation command · macOS / Linux
curl -fsSL https://ampcode.com/install.sh | bashOpen your project folder in a terminal, then run:
ampAccount and authentication
Sign in to Amp and select the workspace whose access and billing you intend to use.
Project configuration and tools
Use AGENTS.md, skills and MCP for project context; choose local execution or an Orb deliberately.
First task to try
Review a project locally before delegating a longer implementation to a hosted environment.
Official configuration reference ↗Related CLI tools
All AI CLI tools →
Project evaluation checklist
- Open a small, familiar project and confirm that your essential language tooling works.
- Give the agent one bounded change with an observable acceptance criterion.
- Review the diff, run the project’s checks and compare the result with your current workflow.
- Inspect usage after the task. Estimate a month of similar work, including any separate model or agent bill.