The outcome

Get into the official Amp experience with the right account and a setup you understand.

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

    Start at https://ampcode.com/ and confirm the domain before entering account or payment information.

  2. 02

    For desktop use, follow the official download link. Current availability: Amp is available as a CLI with integrations for VS Code-based editors, JetBrains IDEs, Neovim, and Zed, plus web-based thread and project collaboration..

  3. 03

    An Amp account, the official CLI, a supported local development environment, and an approved policy for code context, thread visibility, model providers, and tool execution.

  4. 04

    Sign in with the account you intend to keep using, then review plan, data, notification, and permission settings.

  5. 05

    Run one low-risk test task before connecting sensitive files, repositories, or workspace data.

Working standard

What good use looks like.

  • Use official download pages.
  • Review permissions during setup.
  • Keep installers and applications updated.

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.