# Amp Amp is a coding agent for terminal and editor workflows, with leading models, threads, subagents, CLI, editor integrations, and web sharing. - Findings24: - Website: - Pricing: Freemium - Categories: AI Code Assistant ## What is Amp? Amp is a coding agent for terminal and editor workflows. It is designed to use leading models directly, with a focus on unconstrained token usage, strong model selection, and a workflow that changes with the models instead of preserving old behavior for its own sake. The product centers on threads, model modes, and subagents. You can run it from the CLI, connect it to supported editors, share threads through the web UI, and use plugins to add tools or policy inside a workspace. ## What can Amp do? ### Multi-model routing Amp can use several model families and chooses among them based on the mode or task, including GPT-5.5, Opus 4.8, and fast models. ### Task-specific modes The product is built around three modes: \`deep\` for extended reasoning, \`smart\` for broad autonomy, and \`rush\` for small well-defined tasks. ### Thread-based workflows Amp threads can be saved and shared, and the manual recommends one thread per task to keep work organized. ### CLI plus editor integrations The CLI is the main entry point, with IDE integrations for JetBrains, Neovim, VS Code-based editors, and Zed. ### Extensible plugin system The site says Amp can be extended with plugins that hook into events, add tools, standardize policy, and then be deployed into a workspace. ### Passkey-protected remote control The security reference states that teams can enforce passkey-authenticated sessions for web and mobile remote control. ## Use Cases ### Terminal-based implementation work Use Amp in a terminal session when you want an agent to make code changes, run commands, and keep working from a shared thread. ### IDE-assisted development Use the editor integrations when you want Amp alongside an existing codebase in JetBrains, Neovim, VS Code-based editors, or Zed. ### Complex tasks and analysis Use the deep mode for complex debugging, planning, or design work that needs longer reasoning and more context handling. ### Parallelized refactors Use subagents for broader refactors or repetitive transformations, such as converting several files or splitting work across focused subtasks. ### Remote thread oversight Use the web UI and mobile remote control when a team needs to follow or steer a running thread from outside the local terminal. ## Frequently Asked Questions ### How do you get started with Amp? Amp is installed through \`ampcode.com/install\`, then you run \`amp\` in the terminal. The manual also describes IDE connections and notes that Amp can be used from the CLI and web UI. ### What kinds of tasks is Amp meant for? Amp is positioned for coding tasks in a terminal or editor, including fixing errors, running tests, reviewing API designs, finding code paths, planning changes, and using subagents for larger tasks. ### What agent modes does Amp offer? Amp’s manual describes three modes: \`deep\` for extended reasoning on complex problems, \`smart\` for unconstrained state-of-the-art model use, and \`rush\` for fast, low-token tasks. It also mentions a less recommended \`large\` mode. ### Can you share work across a team? The site says Amp lets you save and share threads, and the manual says workspace thread sharing helps people in the same workspace learn from each other. ### Which platforms and editors does Amp support? Amp supports Mac, Linux, WSL, and Windows installation paths, and the manual lists JetBrains, Neovim, VS Code-based editors, and Zed for editor integration. ## Quick Facts - **Category**: Developer Tool - **Primary use**: AI coding agent - **Platforms**: Mac, Linux, WSL, Windows - **Editors**: JetBrains, Neovim, VS Code-based editors, Zed - **Source domain**: ampcode.com - **Pricing shape**: Pay as you go for individuals