The outcome

Learn the interaction loop using a small task with a clear outcome.

Amp is a cloud-connected AI coding agent for terminal and editor workflows. Running focused coding tasks in durable threads, applying repository guidance, reviewing changes, and using different reasoning modes from the terminal or editor. This guide narrows that broad capability into one repeatable outcome, with checkpoints that keep the source material and your judgment in the loop.

Before you begin

Set the boundary before the tool starts.

Choose one real task, identify who will use the result, and decide what evidence or test will make the result acceptable. Gather only the source material needed for that task. If the work contains confidential, personal, regulated, or client-owned information, confirm that the platform and account are approved before sharing it.

Troiana principle

AI should make the work easier to inspect. If the workflow removes the source, the owner, or the review step, redesign the workflow.

Step by step

A workflow you can repeat.

  1. 01

    Install the official CLI, sign in, and start Amp from a clean branch in the intended repository.

  2. 02

    Create one thread for one task and provide acceptance criteria, relevant files, and exact validation commands.

  3. 03

    Choose a mode that matches the task and ask Amp to inspect and explain before it changes files.

  4. 04

    Review tool actions, the complete diff, test output, thread visibility, and commit destination before shipping.

Working standard

What good use looks like.

  • State the outcome before the background.
  • Provide the real source material.
  • Review the result before expanding the task.

Amp runs tools without asking by default, and thread data can include prompts, tool results, attachments, and selected code. Work in an isolated branch or environment, add custom permission controls for untrusted inputs, keep secrets out of context despite best-effort redaction, choose thread visibility deliberately, review workspace and administrator access, inspect every diff and command, and require human approval for pushes, deployments, migrations, or destructive actions.

Official references

Check the current product documentation.

Features, plan limits, availability, and data controls change. These official pages are the starting points used for this collection.