podium

Amp

51 of 51 criteria have a sourced finding; 51 were also cross-checked by a second agent. Every comparison that includes Amp links here for scope, limitations, atomic answers and sources.

Humans approve the rubric, templates and prototype; they do not review every finding. An agent source cross-check is not a hands-on product test. A missing sourced finding is not evidence that a capability is absent.

Rubric
0.3 · 51 criteria
Source checks
2026-11-07 to 2026-11-21
Agent cross-checked
51 criteria
Comparisons
1

Access and agent choice

ACC-01

Client access

Agent cross-checked partial

Amp offers Mac (macOS 26+, Apple silicon), Windows (10 1809+ or 11, x64 and Arm) and native Linux desktop apps (Debian 12+, Ubuntu 22.04+, Fedora, Arch; x86-64 or ARM64); Linux includes a local systemd runner. iPhone and iPad (iOS 26+) use a public TestFlight beta and Android 13+ a direct APK; no store release is documented. Web threads run in Orbs at ampcode.com, and the CLI runs locally or in scripts. Windows notifications report ready threads, mentions and access requests. No dedicated editor extension: the CLI connects to VS Code, Cursor, Windsurf, Zed and Neovim through ide connect (Neovim needs the Amp plugin). The JetBrains integration is deprecated and gets no updates.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Amp docs and chronicle rechecked 2026-11-21 (Windows release noted November 17, 2026) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: mobile_browser. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Desktop os [supported] Native Mac (macOS 26+ on Apple silicon), Windows (Windows 10 1809+ or 11, native on x64 and Arm) and Linux desktop clients (Debian 12+, Ubuntu 22.04+, Fedora and Arch on x86-64 or ARM64) are documented. Linux has installation, tray and local-runner instructions. Sources: amp:gap35-linux, amp:b152-apps, amp:b152-windows, amp:b152-help.
  • Mobile apps [partial] iPhone and iPad (iOS or iPadOS 26+) through a public TestFlight beta, with an App Store release promised later, and Android 13+ through a direct APK rather than Google Play. Sources: amp:b152-apps, amp:b152-help.
  • Browser [supported] Web threads run in Orbs at ampcode.com. Sources: amp:nov07-intro.
  • Mobile browser [unknown] Not established for mobile browser in the named first-party source pass. Product access and scenario tests were not run.
  • Cli [supported] The CLI runs locally or in scripts. Sources: amp:nov07-intro.
  • Editor extensions [partial] No dedicated editor extension: the CLI connects to VS Code, Cursor, Windsurf, Zed and Neovim through ide connect (Neovim needs the Amp plugin). The JetBrains integration is deprecated and gets no updates. Sources: amp:b02-cli, amp:b02-help.
  • Task actions [supported] The Windows page says everything on ampcode.com works in the app: threads start in orbs or on runners, the app can run a local runner per account, and Share to Puck sends files or text to Puck. Sources: amp:b152-windows.
  • Notifications [supported] Windows notifications report a thread ready for input, mentions and access requests; share, multiplayer and contributor requests can be answered from the notification. Sources: amp:b152-windows.
  • Cross device continuity [supported] The guide describes starting an Orb on iPhone and continuing from Mac or terminal; this was not tested. Sources: amp:nov07-intro.

Sources: amp:nov07-intro, amp:gap35-linux, amp:nov12-chronicle, amp:b02-cli, amp:b02-help, amp:b152-apps, amp:b152-windows, amp:b152-help, amp:b152-chronicle

Agent cross-checked partial

Amp supplies its own coding-agent harness across clients and builds prompts and tools around the selected model; custom agent modes and subagents remain Amp agents. With a linked Claude subscription, Amp also offers a Claude Code agent under Your Agents that runs Claude Code with Amp's tools, and Claude models served by that plan run through Claude Code via the Claude Agent SDK on Amp's servers. The agent is fixed per thread once started on Claude Code or a plugin agent. Other third-party coding CLIs are not documented as selectable harnesses in the checked pages.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; Model Selector rechecked 2026-11-21; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Agent and model choice: first-party sources in this pass did not establish custom_adapters beyond Amp plugin agents. Claude Code is documented only with a linked Claude subscription; other third-party coding CLIs are not documented. No install timing or external-tool fixture was run.
5 atomic answers
  • Harnesses [supported] The Amp agent with its Task and Read Thread subagents, and, with a linked Claude subscription, a Claude Code agent picked under Your Agents in the model selector; plugins can add their own agents there. Support for Codex CLI, Cursor Agent, Gemini CLI, OpenCode, Pi, Grok CLI, Aider or Antigravity as harnesses is not documented in the checked pages (Model Selector, Models & Subagents, Model Routing). Sources: amp:b152-model-selector, amp:gap35-agent-architecture.
  • Model providers [supported] Amp routes work across provider models; model routing changes over time. Sources: amp:nov07-models.
  • Custom adapters [partial] Plugins define custom Amp agent modes through amp.createAgent with a model; these remain inside the Amp agent API. Sources: amp:gap35-agent-architecture.
  • Session integration [supported] Embedded: Amp builds the agent around the selected model and owns threads, tools and subagents. Claude models served by a linked Claude subscription run through Claude Code via the Claude Agent SDK on Amp's servers. The separate Claude Code agent runs Claude Code with Amp's tools and also requires a linked Claude subscription. Sources: amp:b02-models, amp:b152-model-selector, amp:b02-threads.
  • Mixed harness operation [partial] The agent is chosen per thread: a thread started on Claude Code or a plugin agent keeps that agent and cannot switch to another model, while other threads can switch models. Mixing agents inside one thread is not documented. Sources: amp:b152-model-selector.

Sources: amp:nov07-models, amp:gap35-agent-architecture, amp:b02-models, amp:b02-model-selector, amp:b02-threads, amp:b152-model-selector

Agent cross-checked partial

The pricing guide supports linking ChatGPT and Claude subscriptions. BYOK is a separate inference route. Further scoped facts are recorded in the atomic answers. Fable BYOK needs an Anthropic workspace with data retention; Sign in with ChatGPT connects each ChatGPT account to only one Amp account, while ChatGPT Subscription (Legacy) lets one ChatGPT account serve several Amp accounts; Copilot needs Copilot CLI enabled and *.ghe.com hosts are unsupported; Gemini image generation needs an AI Studio key; one active connection per subscription type. An Amp account is required; Hobby has no monthly fee.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Amp docs and chronicle retrieved 2026-11-12 (news through Nov 10, 2026) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Subscriptions, API keys and vendor credits: first-party sources in this pass did not establish local_models. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.
7 atomic answers
  • Agent subscriptions [supported] The pricing guide supports linking ChatGPT and Claude subscriptions. Sources: amp:nov07-pricing.
  • Api accounts [supported] BYOK is a separate inference route. Sources: amp:nov07-pricing.
  • Vendor credits [supported] Paid credits cover model and non-model tool usage; non-enterprise inference uses provider API rates without markup. Sources: amp:nov07-pricing.
  • Local models [unknown] Not established for local models in the named first-party source pass. Product access and scenario tests were not run.
  • Account switching [supported] The apps keep up to five signed-in accounts per device. Sources: amp:b152-apps.
  • Vendor account requirement [supported] An Amp account is required; Hobby has no monthly fee. Sources: amp:b02-intro, amp:b02-pricing.
  • Provider restrictions [supported] Fable BYOK needs an Anthropic workspace with data retention; Sign in with ChatGPT connects each ChatGPT account to only one Amp account, while ChatGPT Subscription (Legacy) lets one ChatGPT account serve several Amp accounts; Copilot needs Copilot CLI enabled and *.ghe.com hosts are unsupported; Gemini image generation needs an AI Studio key; one active connection per subscription type. Sources: amp:b02-models, amp:b02-routing, amp:b152-routing.

Sources: amp:nov07-pricing, amp:b02-models, amp:b02-routing, amp:b02-intro, amp:b02-pricing, amp:b152-routing, amp:b152-apps

Agent cross-checked partial

The quickstart permits a project without a Git repository. Orbs support GitHub and other HTTPS Git hosts; GitHub private access uses an installed GitHub App. Runners start with amp --no-tui on a user machine; self-hosted orbs use amp orb provider with a user dispatch program or the Helm chart for GKE, EKS and AKS. Quickstart: sign up, create a project from a Git repository or start without one, then run an agent in an orb; apps and CLI are optional. Amp prepares project orbs with setup scripts and saves a snapshot per orb size, which later threads restore. Docs cover pre-clone and pre-setup scripts, .agents/setup, .agents/resume and a Setup Log for failed repository setup.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Onboarding and project prerequisites: first-party sources in this pass did not establish local_git_without_remote. Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.
7 atomic answers
  • First task setup [supported] Quickstart: sign up, create a project from a Git repository or start without one, then run an agent in an orb; apps and CLI are optional. Sources: amp:b02-intro.
  • No git [supported] The quickstart permits a project without a Git repository. Sources: amp:nov07-intro.
  • Local git without remote [unknown] Not established for local git without remote in the named first-party source pass. Product access and scenario tests were not run.
  • Hosted git [supported] Orbs support GitHub and other HTTPS Git hosts; GitHub private access uses an installed GitHub App. Sources: amp:nov07-github.
  • Prerequisite guidance [supported] Docs cover pre-clone and pre-setup scripts, .agents/setup, .agents/resume and a Setup Log for failed repository setup. Sources: amp:b02-customizing.
  • Managed cloud setup [supported] Amp prepares project orbs with setup scripts and saves a snapshot per orb size, which later threads restore. Sources: amp:b02-customizing.
  • Byo vps onboarding [supported] Runners start with amp --no-tui on a user machine; self-hosted orbs use amp orb provider with a user dispatch program or the Helm chart for GKE, EKS and AKS. Sources: amp:b02-runners, amp:b02-selfhosted.

Sources: amp:nov07-intro, amp:nov07-github, amp:b02-runners, amp:b02-selfhosted, amp:b02-intro, amp:b02-customizing

Agent cross-checked partial

A public External API v2 covers workspace thread data, members, projects and repository search, groups, entitlements, model-provider keys and usage analytics through machine-to-machine OAuth apps; it can delete but not create threads. Non-interactive use sets AMP_API_KEY to an sgamp_ access token; service-account keys run as the workspace. amp -x runs one prompt, -ox runs it in an orb, --executor runner:<id> uses a runner; thread, space and sync subcommands exist. Puck is exposed as a remote MCP server at https://ampcode.com/mcp for Claude, ChatGPT and other MCP clients. CLI and SDK start and continue threads, spawn orbs and runner threads, create Spaces, and list, search, label, archive, delete and export threads. TypeScript and Python SDKs run the agent and continue threads by ID; the TypeScript SDK needs an Amp CLI at least as new as its pinned version, a legacy SDK release serves pre-Amp Neo use, and the docs say Amp keeps no backward compatibility. GitHub events continue or spawn threads; plugin webhooks wake orb threads with at-least-once delivery; Amp-hosted repositories offer a post-receive webhook.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public first-party sources checked 2026-11-21; no installed release tested · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Partial or unsupported atomic answers carry their stated limits; no hands-on test was run.
8 atomic answers
  • Cli [supported] amp -x runs one prompt, -ox runs it in an orb, --executor runner:<id> uses a runner; thread, space and sync subcommands exist. Sources: amp:b02-execute, amp:b02-threads.
  • Api [supported] A public External API v2 reference (ampcode.com/api/external, linked as API in the docs) covers threads (list, metadata, messages, usage, delete), workspace members, projects and repository search, groups, entitlements, workspace model-provider keys, usage analytics and the caller. Workspace admins create machine-to-machine OAuth apps with scopes; such tokens can delete but not create threads, and Amp points product automation to the CLI or SDK. Sources: amp:b152-external-api, amp:b02-security.
  • Sdk [supported] TypeScript and Python SDKs run the agent and continue threads by ID. Sources: amp:b02-sdk.
  • Mcp server [supported] Puck's "Use Puck in Other Apps" section documents https://ampcode.com/mcp as a remote MCP server for Claude, ChatGPT and other MCP clients, with tools puck, new_puck_conversation and orbs. Clients with Client ID Metadata Documents connect automatically; dynamic client registration is not supported, and other clients need a client ID. Sources: amp:b152-puck-mcp, amp:b02-chronicle.
  • Webhooks [supported] GitHub events continue or spawn threads; plugin webhooks wake orb threads with at-least-once delivery; Amp-hosted repositories offer a post-receive webhook. Sources: amp:b02-github, amp:b02-automations, amp:b02-projects.
  • Operations [supported] CLI and SDK start and continue threads, spawn orbs and runner threads, create Spaces, and list, search, label, archive, delete and export threads. Sources: amp:b02-execute, amp:b02-threads, amp:b02-spaces, amp:b02-sdk.
  • Authentication [supported] Non-interactive use sets AMP_API_KEY to an sgamp_ access token; service-account keys run as the workspace. Sources: amp:b02-execute, amp:b02-workspaces.
  • Stability [partial] The TypeScript SDK requires an Amp CLI at least as new as the version pinned by the installed SDK release; @ampcode/sdk@0.1.0-20260528044221-ge0e19fa is a legacy release for users who need Amp from before Amp Neo. The docs' principles say Amp keeps "No backward compatibility". Sources: amp:b02-sdk, amp:b152-docs-principles.

Sources: amp:b02-security, amp:b02-execute, amp:b02-workspaces, amp:b02-threads, amp:b02-chronicle, amp:b02-spaces, amp:b02-sdk, amp:b02-intro, amp:b02-github, amp:b02-automations, amp:b02-projects, amp:b152-external-api, amp:b152-puck-mcp, amp:b152-docs-principles

Agent cross-checked supported

Local commands and remote MCP servers are supported. Remote servers can use OAuth or configured headers. Further scoped facts are recorded in the atomic answers. Plugins register custom tools with amp.registerTool. Repository, personal and workspace AGENTS.md with glob-scoped @-mentions; SKILL.md skills, including Claude-compatible skill directories. Amp provides GitHub, GitLab, Google, Linear and Slack integrations; each person connects their own account and admins install shared apps; other services connect through MCP. TypeScript or JavaScript plugins add tools, commands, event handlers, skills and UI.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Detailed client actions, provider-specific eligibility and first-run prerequisites need targeted access; no install timing or external-tool fixture was run.
7 atomic answers
  • Mcp client [supported] Local commands and remote MCP servers are supported. Sources: amp:nov07-mcp.
  • Plugins [supported] TypeScript or JavaScript plugins add tools, commands, event handlers, skills and UI. Sources: amp:b02-plugins.
  • Custom tools [supported] Plugins register custom tools with amp.registerTool. Sources: amp:b02-plugins.
  • Instructions import [supported] Repository, personal and workspace AGENTS.md with glob-scoped @-mentions; SKILL.md skills, including Claude-compatible skill directories. Sources: amp:b02-agentsmd, amp:b02-skills.
  • Authentication [supported] Remote servers can use OAuth or configured headers. Sources: amp:nov07-mcp.
  • Permission scope [supported] Remote MCP calls use the owner's credentials; Use in Multiplayer Threads defaults on and can disable a server's tools for that thread. Sources: amp:nov07-multiplayer.
  • Integration owner [supported] Amp provides GitHub, GitLab, Google, Linear and Slack integrations; each person connects their own account and admins install shared apps; other services connect through MCP. Sources: amp:b02-integrations.

Sources: amp:nov07-multiplayer, amp:nov07-mcp, amp:b02-plugins, amp:b02-agentsmd, amp:b02-skills, amp:b02-integrations

Agent cross-checked partial

Docs call the Mac, Windows and Linux apps native; Windows installs through App Installer for x64 and Arm. No UI framework is named. Only vendor documentation calling the apps native; no technical documentation or source names the framework, and no binary was inspected. Docs call the iOS and Android apps native; no framework is named.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public first-party sources checked 2026-11-21; no installed release tested · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Unknown after the 2026-11-21 backfill re-verification of first-party sources: hybrids. No configured product fixture was run; documentation does not establish successful hands-on behavior.
4 atomic answers
  • Desktop implementation [partial] Docs call the Mac, Windows and Linux apps native; Windows installs through App Installer for x64 and Arm. No UI framework is named. Sources: amp:b02-apps, amp:b02-windows.
  • Mobile implementation [partial] Docs call the iOS and Android apps native; no framework is named. Sources: amp:b02-apps.
  • Hybrids [unknown] Not established for hybrids in the named first-party source pass. Product access and scenario tests were not run.
  • Implementation evidence [partial] Only vendor documentation calling the apps native; no technical documentation or source names the framework, and no binary was inspected. Sources: amp:b02-apps.

Sources: amp:b02-apps, amp:b02-windows

Planning and context

Agent cross-checked partial

GitHub webhooks can continue threads or spawn Orbs from issues and pull requests. Linear or GitHub remain the trackers; Amp works the issue in a thread and replies there. Assigning or mentioning Amp in Linear starts a session; spawners start an orb per new GitHub issue, PR or review request. Linear sessions reply in Linear and orbs update issues through the user's connection; PR subscriptions follow reviews. Other tracker edits stay in the tracker. Prompts start work in a new thread, a Space chat or Puck. Threads have stable T-... URLs. Amp comments on Linear issues (as Amp or the user) and updates issues through the user's Linear connection; on GitHub it pushes, opens PRs and comments. Issue and PR subscriptions feed new comments, reviews and state changes into the thread; Linear sessions show Amp progress. No field-level two-way sync.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Intake and external tracker relationship: first-party sources in this pass did not establish local_creation. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.
9 atomic answers
  • Local creation [unknown] Not established for local creation in the named first-party source pass. Product access and scenario tests were not run.
  • Prompt intake [supported] Prompts start work in a new thread, a Space chat or Puck. Sources: amp:b02-threads, amp:b02-spaces, amp:b02-puck.
  • External import [supported] Assigning or mentioning Amp in Linear starts a session; spawners start an orb per new GitHub issue, PR or review request. Sources: amp:b02-integrations, amp:b02-github.
  • Chat git triggers [supported] GitHub webhooks can continue threads or spawn Orbs from issues and pull requests. Sources: amp:nov07-github.
  • Authoritative tracker [partial] Linear or GitHub remain the trackers; Amp works the issue in a thread and replies there. Sources: amp:b02-integrations, amp:b02-github.
  • Stable ids [supported] Threads have stable T-... URLs. Sources: amp:b02-threads.
  • Sync [partial] Issue and PR subscriptions feed new comments, reviews and state changes into the thread; Linear sessions show Amp progress. No field-level two-way sync. Sources: amp:b02-github, amp:b02-integrations.
  • Supported edits [partial] Amp comments on Linear issues (as Amp or the user) and updates issues through the user's Linear connection; on GitHub it pushes, opens PRs and comments. Sources: amp:b02-integrations, amp:b02-github.
  • External roundtrips [partial] Linear sessions reply in Linear and orbs update issues through the user's connection; PR subscriptions follow reviews. Other tracker edits stay in the tracker. Sources: amp:b02-integrations, amp:b02-github, amp:b02-chronicle.

Sources: amp:nov07-github, amp:b02-integrations, amp:b02-github, amp:b02-chronicle, amp:b02-threads, amp:b02-spaces, amp:b02-puck

Agent cross-checked partial

Thread artifacts can hold plans and checklists, persisted with the thread. This does not establish acceptance gates. Humans and agents edit the same artifact. Each artifact save creates a revision. Agents merge against a newer artifact revision when a concurrent save prevents their update. Threads and revisioned artifacts are stored on Amp Server and survive client restarts.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: acceptance_criteria, implementation_links. No configured product fixture was run; documentation does not establish successful hands-on behavior.
7 atomic answers
  • Plans [supported] Thread artifacts can hold plans and checklists, persisted with the thread. This does not establish acceptance gates. Sources: amp:gap07-threads.
  • Acceptance criteria [unknown] Not established for acceptance criteria in the named first-party source pass. Product access and scenario tests were not run.
  • Editors [supported] Humans and agents edit the same artifact. Sources: amp:gap07-threads.
  • Revisions [supported] Each artifact save creates a revision. Sources: amp:gap07-threads.
  • Amendment [supported] Agents merge against a newer artifact revision when a concurrent save prevents their update. Sources: amp:gap07-threads.
  • Restart persistence [supported] Threads and revisioned artifacts are stored on Amp Server and survive client restarts. Sources: amp:b02-threads, amp:b02-security.

Sources: amp:gap07-threads, amp:b02-threads, amp:b02-security

Agent cross-checked partial

A Space groups threads under an optional goal and project (since Nov 6, 2026); it is not a structured epic record. Threads started by a thread move with it into or out of a Space. Existing threads can be added to or moved between Spaces. A thread removed from a Space keeps its history and environment.

Scope
Surfaces: Amp web, Mac and iOS · Version: Amp docs and chronicle retrieved 2026-11-12 (news through Nov 10, 2026) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-12
  • Only the atoms cited here are established from documentation; the remaining atoms stay unknown and no hands-on test was run.
9 atomic answers
  • Epics [partial] A Space groups threads under an optional goal and project (since Nov 6, 2026); it is not a structured epic record. Sources: amp:nov12-spaces, amp:nov12-chronicle.
  • Hierarchy [supported] Threads started by a thread move with it into or out of a Space. Sources: amp:nov12-spaces.
  • Blockers [unknown] Not established for blockers in the named first-party source pass. Product access and scenario tests were not run.
  • Readiness [unknown] Not established for readiness in the named first-party source pass. Product access and scenario tests were not run.
  • Enforcement [unknown] Not established for enforcement in the named first-party source pass. Product access and scenario tests were not run.
  • State propagation [unknown] Not established for state propagation in the named first-party source pass. Product access and scenario tests were not run.
  • Task to epic [supported] Existing threads can be added to or moved between Spaces. Sources: amp:nov12-spaces.
  • Identity retention [supported] A thread removed from a Space keeps its history and environment. Sources: amp:nov12-spaces.
  • Workflow constraints [unknown] Not established for workflow constraints in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:nov12-spaces, amp:nov12-chronicle

Agent cross-checked partial

Amp loads AGENTS.md in the current directory, parents and relevant subtrees, plus personal and system guidance. Workspace global guidance applies to top-level agents, with explicit exclusions for subagents, Puck and raw custom agents. Ask Amp to update AGENTS.md from the thread. No memory store is documented; agents find and read earlier threads. Repository and Global AGENTS.md, and thread artifacts. Project, personal and workspace skill repositories. Handoff starts a fresh thread with the context that matters; any thread can be referenced by URL.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Shared context and memory: first-party sources in this pass did not establish provenance, deletion, freshness. No shared requirement-to-implementation, backlog evolution or authoritative-record round-trip fixture was run. Instructions and per-task plans do not prove living specifications.
10 atomic answers
  • Instructions [supported] Amp loads AGENTS.md in the current directory, parents and relevant subtrees, plus personal and system guidance. Sources: amp:nov07-instructions.
  • Skills [supported] Project, personal and workspace skill repositories. Sources: amp:b02-skills.
  • Project docs [supported] Repository and Global AGENTS.md, and thread artifacts. Sources: amp:b02-agentsmd, amp:b02-threads.
  • Memory [partial] No memory store is documented; agents find and read earlier threads. Sources: amp:b02-models, amp:b02-threads.
  • Scope [supported] Workspace global guidance applies to top-level agents, with explicit exclusions for subagents, Puck and raw custom agents. Sources: amp:nov07-instructions.
  • Provenance [unknown] Not established for provenance in the named first-party source pass. Product access and scenario tests were not run.
  • Correction [supported] Ask Amp to update AGENTS.md from the thread. Sources: amp:b02-agentsmd.
  • Deletion [unknown] Not established for deletion in the named first-party source pass. Product access and scenario tests were not run.
  • Freshness [unknown] Not established for freshness in the named first-party source pass. Product access and scenario tests were not run.
  • Takeover continuity [supported] Handoff starts a fresh thread with the context that matters; any thread can be referenced by URL. Sources: amp:b02-threads.

Sources: amp:nov07-instructions, amp:b02-agentsmd, amp:b02-models, amp:b02-threads, amp:b02-skills

Agent cross-checked partial

Finder returns file paths and line ranges; answers are not documented as citing sources. The Task subagent has a code-search skill; the finder plugin returns files and line ranges. The librarian clones and explains other repositories; Parallel powers web search. The security reference states the client and server do not store, clone or index the entire codebase. System models analyze images, PDFs, audio and video; attachments feed them.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public first-party sources checked 2026-11-21; no installed release tested · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Unknown after the 2026-11-21 backfill re-verification of first-party sources: freshness, access_scope, api_retrieval, conflict_detection, review_enforcement. No configured product fixture was run; documentation does not establish successful hands-on behavior.
10 atomic answers
  • Indexing [unsupported] The security reference states the client and server do not store, clone or index the entire codebase. Sources: amp:b02-security.
  • External knowledge [supported] The librarian clones and explains other repositories; Parallel powers web search. Sources: amp:b02-models, amp:b02-security.
  • Multimodal inputs [supported] System models analyze images, PDFs, audio and video; attachments feed them. Sources: amp:b02-models, amp:b02-files.
  • Freshness [unknown] Not established for freshness in the named first-party source pass. Product access and scenario tests were not run.
  • Access scope [unknown] Not established for access scope in the named first-party source pass. Product access and scenario tests were not run.
  • Api retrieval [unknown] Not established for api retrieval in the named first-party source pass. Product access and scenario tests were not run.
  • Citations [partial] Finder returns file paths and line ranges; answers are not documented as citing sources. Sources: amp:b02-models.
  • Conflict detection [unknown] Not established for conflict detection in the named first-party source pass. Product access and scenario tests were not run.
  • Review enforcement [unknown] Not established for review enforcement in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:b02-models, amp:b02-security, amp:b02-files

Agent cross-checked partial

Threads archive, unarchive and snooze; a separate issue entity is not documented in the checked pages. A Space starts a thread per request; storing ideas separately from threads is not documented in the checked pages. No tracker is required; prompts start work directly. Activity filters threads by time, status, author and project; a separate issue entity to filter is not documented in the checked pages (Threads, Spaces, docs overview). Threads take labels searchable with label:. Activity search and agent thread search cover threads, not issues. A thread is both the work item and the agent conversation.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public first-party sources checked 2026-11-21; no installed release tested · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Unknown after the 2026-11-21 backfill re-verification of first-party sources: create, edit, discuss, prioritize, assign, reopen, project_epic_views, idea_parking, metadata, durable_states. No configured product fixture was run; documentation does not establish successful hands-on behavior.
17 atomic answers
  • Create [unknown] Not established for create in the named first-party source pass. Product access and scenario tests were not run.
  • Edit [unknown] Not established for edit in the named first-party source pass. Product access and scenario tests were not run.
  • Discuss [unknown] Not established for discuss in the named first-party source pass. Product access and scenario tests were not run.
  • Prioritize [unknown] Not established for prioritize in the named first-party source pass. Product access and scenario tests were not run.
  • Label [partial] Threads take labels searchable with label:. Sources: amp:b02-threads.
  • Assign [unknown] Not established for assign in the named first-party source pass. Product access and scenario tests were not run.
  • Filter [partial] Activity filters threads by time, status, author and project; a separate issue entity to filter is not documented in the checked pages (Threads, Spaces, docs overview). Sources: amp:b02-threads.
  • Archive [partial] Threads archive, unarchive and snooze; a separate issue entity is not documented in the checked pages. Sources: amp:b02-threads.
  • Reopen [unknown] Not established for reopen in the named first-party source pass. Product access and scenario tests were not run.
  • Project epic views [unknown] Not established for project epic views in the named first-party source pass. Product access and scenario tests were not run.
  • Idea parking [unknown] Not established for idea parking in the named first-party source pass. Product access and scenario tests were not run.
  • Explicit dispatch [partial] A Space starts a thread per request; storing ideas separately from threads is not documented in the checked pages. Sources: amp:b02-spaces.
  • Task session separation [partial] A thread is both the work item and the agent conversation. Sources: amp:b02-threads.
  • Metadata [unknown] Not established for metadata in the named first-party source pass. Product access and scenario tests were not run.
  • Durable states [unknown] Not established for durable states in the named first-party source pass. Product access and scenario tests were not run.
  • External tracker requirement [supported] No tracker is required; prompts start work directly. Sources: amp:b02-intro, amp:b02-threads.

Sources: amp:b02-threads, amp:b02-spaces, amp:b02-intro

Agent cross-checked partial

Space cards show each thread’s live status and whether it needs someone. Agents start child threads that report results back; children nest under the parent. Agents and Puck start threads. The Read Thread subagent and @T- mentions read other threads. Delegated threads bring results back into the current thread. Agents and humans use the same T-... thread IDs across clients. Puck archives threads and agents can snooze them on request; other state fields are not documented.

Scope
Surfaces: Amp web, Mac and iOS · Version: Amp docs and chronicle retrieved 2026-11-12 (news through Nov 10, 2026) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-21
  • Only the atoms cited here are established from documentation; the remaining atoms stay unknown and no hands-on test was run.
14 atomic answers
  • Shared ids [supported] Agents and humans use the same T-... thread IDs across clients. Sources: amp:b02-threads.
  • Read [supported] The Read Thread subagent and @T- mentions read other threads. Sources: amp:b02-models, amp:b02-threads.
  • Create [supported] Agents and Puck start threads. Sources: amp:b02-a2a, amp:b02-puck.
  • Update [unknown] Not established for update in the named first-party source pass. Product access and scenario tests were not run.
  • Claim [unknown] Not established for claim in the named first-party source pass. Product access and scenario tests were not run.
  • Assign [unknown] Not established for assign in the named first-party source pass. Product access and scenario tests were not run.
  • State changes [partial] Puck archives threads and agents can snooze them on request; other state fields are not documented. Sources: amp:b02-puck, amp:b02-threads.
  • Dependencies [unknown] Not established for dependencies in the named first-party source pass. Product access and scenario tests were not run.
  • Children [supported] Agents start child threads that report results back; children nest under the parent. Sources: amp:b02-a2a, amp:b02-threads.
  • Results [supported] Delegated threads bring results back into the current thread. Sources: amp:b02-a2a.
  • Human visibility [supported] Space cards show each thread’s live status and whether it needs someone. Sources: amp:nov12-spaces.
  • Attribution [unknown] Not established for attribution in the named first-party source pass. Product access and scenario tests were not run.
  • Permissions [unknown] Not established for permissions in the named first-party source pass. Product access and scenario tests were not run.
  • Conflicts [unknown] Not established for conflicts in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:nov12-spaces, amp:b02-a2a, amp:b02-threads, amp:b02-puck, amp:b02-models

Agent cross-checked partial

Artifacts can retain a plan or requirements document with a thread; a dedicated executable requirements schema is not established. Workspace users allowed to open the thread can edit its artifacts. Every selectable agent mode can read and write artifacts using the artifact tool. Every artifact save creates a new revision. Artifacts remain accessible from the thread Artifacts view until deleted.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-07
  • Unknown after the targeted first-party documentation, release and repository pass: approvals, implementation_links, drift_detection, review_integration. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Persistent requirements [partial] Artifacts can retain a plan or requirements document with a thread; a dedicated executable requirements schema is not established. Sources: amp:gap07-threads.
  • Human edits [supported] Workspace users allowed to open the thread can edit its artifacts. Sources: amp:gap07-threads.
  • Agent edits [supported] Every selectable agent mode can read and write artifacts using the artifact tool. Sources: amp:gap07-threads.
  • Revisions [supported] Every artifact save creates a new revision. Sources: amp:gap07-threads.
  • Approvals [unknown] Not established for approvals in the named first-party source pass. Product access and scenario tests were not run.
  • Later retrieval [supported] Artifacts remain accessible from the thread Artifacts view until deleted. Sources: amp:gap07-threads.
  • Drift detection [unknown] Not established for drift detection in the named first-party source pass. Product access and scenario tests were not run.
  • Review integration [unknown] Not established for review integration in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:gap07-threads

Coordination and automation

COORD-01

Parallel work

Agent cross-checked partial

The Orb guide describes several independent tasks running at once, each with its own environment. Several independent orb threads can run at once, each in its own orb. Each user gets a burst of 20 metered orbs, then one new orb every five minutes; higher limits through support; Enterprise sets per-user spend entitlements. Activity filters threads by status; Space cards show live status; desktop tray menus mark running, unread, waiting and failed threads.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Parallel work: first-party sources in this pass did not establish observed_concurrency. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
5 atomic answers
  • Concurrent sessions [supported] Several independent orb threads can run at once, each in its own orb. Sources: amp:b02-orbs.
  • Concurrent tasks [supported] The Orb guide describes several independent tasks running at once, each with its own environment. Sources: amp:nov07-orbs.
  • Quotas [supported] Each user gets a burst of 20 metered orbs, then one new orb every five minutes; higher limits through support; Enterprise sets per-user spend entitlements. Sources: amp:b02-orbs, amp:b02-entitlements.
  • Observed concurrency [unknown] Not established for observed concurrency in the named first-party source pass. Product access and scenario tests were not run.
  • Status visibility [supported] Activity filters threads by status; Space cards show live status; desktop tray menus mark running, unread, waiting and failed threads. Sources: amp:b02-threads, amp:b02-spaces, amp:b02-windows.

Sources: amp:nov07-orbs, amp:b02-orbs, amp:b02-entitlements, amp:b02-threads, amp:b02-spaces, amp:b02-windows

Agent cross-checked partial

@Amp in a public Slack channel linked to a workspace-shared Space starts work there. Puck and Spaces start agent threads; Linear issues can be assigned or delegated to Amp, with agent routing to projects. Tagging a workspace member invites them and turns on multiplayer; assigning a thread to a human owner is not documented. Threads and Spaces have one owner: only the owner switches a thread's model, a Space's owner controls its settings, and Space transfer needs acceptance. Exclusive work claims are not documented. Orb starts beyond the pacing limit wait in line; messages can be queued until the agent finishes; webhook events queue per endpoint. A task queue for dispatching work is not documented in the checked pages (Orbs, Threads, Automations, Spaces).

Scope
Surfaces: Amp web, Mac and iOS · Version: Amp docs and chronicle retrieved 2026-11-12 (news through Nov 10, 2026) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-21
  • Only the atoms cited here are established from documentation; the remaining atoms stay unknown and no hands-on test was run.
7 atomic answers
  • Human assignment [partial] Tagging a workspace member invites them and turns on multiplayer; assigning a thread to a human owner is not documented. Sources: amp:b02-multiplayer, amp:b02-threads.
  • Agent assignment [supported] Puck and Spaces start agent threads; Linear issues can be assigned or delegated to Amp, with agent routing to projects. Sources: amp:b02-puck, amp:b02-spaces, amp:b02-integrations.
  • Claims [unknown] Not established for claims in the named first-party source pass. Product access and scenario tests were not run.
  • Queues [partial] Orb starts beyond the pacing limit wait in line; messages can be queued until the agent finishes; webhook events queue per endpoint. A task queue for dispatching work is not documented in the checked pages (Orbs, Threads, Automations, Spaces). Sources: amp:b02-orbs, amp:b02-threads, amp:b02-automations.
  • Routing [supported] @Amp in a public Slack channel linked to a workspace-shared Space starts work there. Sources: amp:nov12-spaces.
  • Duplicate prevention [unknown] Not established for duplicate prevention in the named first-party source pass. Product access and scenario tests were not run.
  • Ownership enforcement [partial] Threads and Spaces have one owner: only the owner switches a thread's model, a Space's owner controls its settings, and Space transfer needs acceptance. Exclusive work claims are not documented. Sources: amp:b02-model-selector, amp:b02-spaces.

Sources: amp:nov12-spaces, amp:b02-puck, amp:b02-spaces, amp:b02-integrations, amp:b02-multiplayer, amp:b02-threads, amp:b02-model-selector, amp:b02-orbs, amp:b02-automations

Agent cross-checked partial

Task executes delegated work and Read Thread summarizes threads. Built-in Task subagents follow the thread's model and effort; custom plugin agents can define model choices. Further scoped facts are recorded in the atomic answers. Amp uses subagents automatically for suitable tasks or when asked. The main agent can give a Task subagent another task with its earlier context; delegated threads can receive more instructions. By prompt, through Puck, from a Space, or by an agent starting another thread. The main agent receives subagent summaries only and users cannot guide subagents directly; delegated threads and Space cards are visible live. The main agent for subagents, Puck, or a Space. Subagent steps stay in the thread and delegated threads persist as their own threads.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Inspectable delegation and communication: first-party sources in this pass did not establish cross_harness, authentication. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
12 atomic answers
  • Roles [supported] Task executes delegated work and Read Thread summarizes threads. Sources: amp:nov07-models.
  • Model harness effort [supported] Built-in Task subagents follow the thread's model and effort; custom plugin agents can define model choices. Sources: amp:nov07-models.
  • Messages [unsupported] Built-in subagents cannot communicate with each other or be steered directly by the user. Sources: amp:nov07-models.
  • Results return [supported] The parent receives final summaries and can send another task with earlier child context retained. Sources: amp:nov07-models.
  • Cross harness [unknown] Not established for cross harness in the named first-party source pass. Product access and scenario tests were not run.
  • Orchestration owner [supported] The main agent for subagents, Puck, or a Space. Sources: amp:b02-models, amp:b02-puck, amp:b02-spaces.
  • Activation [supported] Amp uses subagents automatically for suitable tasks or when asked. Sources: amp:b02-models.
  • Authentication [unknown] Not established for authentication in the named first-party source pass. Product access and scenario tests were not run.
  • Live progress [partial] The main agent receives subagent summaries only and users cannot guide subagents directly; delegated threads and Space cards are visible live. Sources: amp:b02-models, amp:b02-a2a, amp:b02-spaces.
  • Retained results [supported] Subagent steps stay in the thread and delegated threads persist as their own threads. Sources: amp:b02-threads, amp:b02-models.
  • Followup [supported] The main agent can give a Task subagent another task with its earlier context; delegated threads can receive more instructions. Sources: amp:b02-models, amp:b02-a2a.
  • Invocation [supported] By prompt, through Puck, from a Space, or by an agent starting another thread. Sources: amp:b02-puck, amp:b02-spaces, amp:b02-a2a.

Sources: amp:nov07-models, amp:b02-models, amp:b02-a2a, amp:b02-puck, amp:b02-spaces, amp:b02-threads

Agent cross-checked partial

Amp saves one schedule per thread; it can run once or repeat, with pause, resume and delete controls. GitHub events can wake existing threads or start new Orbs. Further scoped facts are recorded in the atomic answers. Amp stores the schedule on the thread, wakes the agent and resumes the orb when it fires. Schedules repeat until paused, deleted, ended or a completion condition is met; one schedule per thread. Failed runs show the error; temporary delivery errors can keep a recurring schedule enabled, and Amp may pause it. Plugin webhook events retry with backoff up to 5 minutes and are dropped after 1 hour.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unattended triggers: first-party sources in this pass did not establish overlaps. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
8 atomic answers
  • Schedules [supported] Amp saves one schedule per thread; it can run once or repeat, with pause, resume and delete controls. Sources: amp:nov07-automation.
  • Events [supported] GitHub events can wake existing threads or start new Orbs. Sources: amp:nov07-github.
  • Recurring tasks [supported] Schedules repeat until paused, deleted, ended or a completion condition is met; one schedule per thread. Sources: amp:b02-automations.
  • Completion conditions [supported] Repeating schedules may end at a configured completion condition. Sources: amp:nov07-automation.
  • Scheduler location [supported] Amp wakes the saved thread and resumes its Orb as needed; this is product-owned scheduling. Sources: amp:nov07-automation.
  • Overlaps [unknown] Not established for overlaps in the named first-party source pass. Product access and scenario tests were not run.
  • Retries [supported] Failed runs show the error; temporary delivery errors can keep a recurring schedule enabled, and Amp may pause it. Plugin webhook events retry with backoff up to 5 minutes and are dropped after 1 hour. Sources: amp:b02-automations.
  • Client independence [supported] Amp stores the schedule on the thread, wakes the agent and resumes the orb when it fires. Sources: amp:b02-automations.

Sources: amp:nov07-github, amp:nov07-automation, amp:b02-automations

Agent cross-checked partial

A snoozed thread surfaces and notifies when it needs an approval or answer. The same thread opens in CLI, web and apps; the orb Terminal tab is a shared tmux session on the agent's working copy and can be embedded in a reply. A scheduled run can unsnooze a thread; snoozed threads waiting for approval reappear and notify. Archiving pauses an orb and automations can be paused; snoozing does not stop the agent. Pausing a running turn is not documented. A paused orb wakes on the next message with conversation, files and services in place. Threads keep prompts, replies, tool calls and file changes. Messages sent while the agent works steer it after the current step; Task subagents receive new tasks as steering. Pressing Esc twice interrupts the agent; archiving stops the orb before it pauses on its own; thread history remains. Failed automation runs show the error; failed repository setup links a Setup Log; tray menus mark failed threads.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Amp docs and chronicle retrieved 2026-11-12 (news through Nov 10, 2026) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
10 atomic answers
  • Pause [partial] Archiving pauses an orb and automations can be paused; snoozing does not stop the agent. Pausing a running turn is not documented. Sources: amp:b02-sizes, amp:b02-automations, amp:b02-threads.
  • Stop [supported] Pressing Esc twice interrupts the agent; archiving stops the orb before it pauses on its own; thread history remains. Sources: amp:b02-threads, amp:b02-sizes.
  • Resume [supported] A paused orb wakes on the next message with conversation, files and services in place. Sources: amp:b02-orbs.
  • Steer [supported] Messages sent while the agent works steer it after the current step; Task subagents receive new tasks as steering. Sources: amp:b02-threads, amp:b02-models.
  • Notifications [supported] A snoozed thread surfaces and notifies when it needs an approval or answer. Sources: amp:nov07-automation.
  • Pending decisions [partial] Space cards flag threads that need someone’s attention. Sources: amp:nov12-spaces.
  • Escalation [supported] A scheduled run can unsnooze a thread; snoozed threads waiting for approval reappear and notify. Sources: amp:b02-automations, amp:b02-threads.
  • Visible errors [supported] Failed automation runs show the error; failed repository setup links a Setup Log; tray menus mark failed threads. Sources: amp:b02-automations, amp:b02-customizing, amp:b02-windows.
  • Chat terminal parity [supported] The same thread opens in CLI, web and apps; the orb Terminal tab is a shared tmux session on the agent's working copy and can be embedded in a reply. Sources: amp:b02-threads, amp:b02-orbs.
  • Retained history [supported] Threads keep prompts, replies, tool calls and file changes. Sources: amp:b02-threads.

Sources: amp:nov07-automation, amp:nov12-spaces, amp:b02-threads, amp:b02-orbs, amp:b02-automations, amp:b02-sizes, amp:b02-models, amp:b02-customizing, amp:b02-windows

Agent cross-checked partial

Unread dots, taskbar or launcher counts, and tray dots for waiting threads; apps notify when a thread is ready. Activity lists every visible thread with time, status, author and project filters, including archived and snoozed. Child threads nest under their parent in the sidebar and move with it; parents can archive all children at once.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public first-party sources checked 2026-11-21; no installed release tested · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Unknown after the 2026-11-21 backfill re-verification of first-party sources: fleet_fixture, dependencies, workload, navigation_errors, fixture_mode. No configured product fixture was run; documentation does not establish successful hands-on behavior.
8 atomic answers
  • Fleet fixture [unknown] Not established for fleet fixture in the named first-party source pass. Product access and scenario tests were not run.
  • Parent child [supported] Child threads nest under their parent in the sidebar and move with it; parents can archive all children at once. Sources: amp:b02-spaces, amp:b02-threads.
  • Dependencies [unknown] Not established for dependencies in the named first-party source pass. Product access and scenario tests were not run.
  • Attention [supported] Unread dots, taskbar or launcher counts, and tray dots for waiting threads; apps notify when a thread is ready. Sources: amp:b02-threads, amp:b02-windows, amp:b02-linux.
  • History [supported] Activity lists every visible thread with time, status, author and project filters, including archived and snoozed. Sources: amp:b02-threads.
  • Workload [unknown] Not established for workload in the named first-party source pass. Product access and scenario tests were not run.
  • Navigation errors [unknown] Not established for navigation errors in the named first-party source pass. Product access and scenario tests were not run.
  • Fixture mode [unknown] Not established for fixture mode in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:b02-threads, amp:b02-windows, amp:b02-linux, amp:b02-spaces

Agent cross-checked partial

The model selector sets each thread's model, effort and speed, replacing the Dial removed on 2026-11-12; plugins can define custom agents. Spaces start a thread per piece of work and chart shipped, archived and open threads. The thread owner can switch model and effort at any time, and the transcript records the switch. Automations, Puck and Spaces take plain-language instructions. Presets include saved prompts (Ship, review, custom), plugin-defined agent modes and Space thread models. amp -x runs one prompt; a new thread starts from the sidebar. Nested child threads stay grouped with their parent; artifacts link back to the thread that wrote them.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Workflow flexibility and orchestration visibility: first-party sources in this pass did not establish live_roles, discoverability, auth_friction. No concurrent-worker, duplicate-claim, delegation-retention or twelve-state fleet fixture was run. UI labels alone do not establish enforcement.
10 atomic answers
  • Quick task [supported] amp -x runs one prompt; a new thread starts from the sidebar. Sources: amp:b02-execute, amp:b02-threads.
  • Growing epic [supported] Spaces start a thread per piece of work and chart shipped, archived and open threads. Sources: amp:b02-spaces.
  • Presets [supported] Saved prompts (Ship, review, custom), plugin-defined agent modes and Space thread models. Sources: amp:b02-puck, amp:b02-plugins, amp:b02-spaces.
  • Natural language [supported] Automations, Puck and Spaces take plain-language instructions. Sources: amp:b02-automations, amp:b02-puck, amp:b02-spaces.
  • Agent configuration [supported] The model selector sets each thread's model, effort and speed; plugins define custom agents listed under Your Agents, and a linked Claude subscription adds the Claude Code agent. The Dial was removed on 2026-11-12. Sources: amp:b152-model-selector, amp:b152-chronicle, amp:b02-plugins.
  • In run changes [supported] The thread owner can switch model and effort at any time; the transcript records the switch. Contradicts the legacy lead, which predates the 2026-11-12 Dial removal. Sources: amp:b02-model-selector, amp:b02-chronicle.
  • Live roles [unknown] Not established for live roles in the named first-party source pass. Product access and scenario tests were not run.
  • Retained relationships [supported] Nested child threads stay grouped with their parent; artifacts link back to the thread that wrote them. Sources: amp:b02-spaces, amp:b02-threads.
  • Discoverability [unknown] Not established for discoverability in the named first-party source pass. Product access and scenario tests were not run.
  • Auth friction [unknown] Not established for auth friction in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:b02-spaces, amp:b02-model-selector, amp:b02-chronicle, amp:b02-automations, amp:b02-puck, amp:b02-plugins, amp:b02-execute, amp:b02-threads, amp:b152-model-selector, amp:b152-chronicle

Execution and reliability

Agent cross-checked partial

The CLI can run Amp on the user's own machine. Users can supply their own Orb compute through amp orb provider and a dispatch program. Orb execution can be hosted on user infrastructure; this is not self-hosting the Amp control plane. Orbs are per-thread machines that continue working when the laptop closes. The size table lists per-Orb CPU, memory and 60 GB disk; default-size rules vary by project and plan. An orb agent keeps working with the laptop closed. Orbs pause after idle timeouts, not run limits; paused filesystem and memory stay encrypted until the thread is deleted. Per thread: Amp orb, a user runner, a self-hosted orb provider or a local CLI session. Open the thread from any app, the web or the CLI and keep prompting. Amp-hosted orbs bill the thread owner per minute from tier minutes or credits; runners are free; self-hosted orbs are free except on Enterprise. Amp provisions an orb per thread from the project snapshot automatically. Primary infrastructure is GCP in the US; Enterprise lists regional endpoints for BYOK providers. No orb region choice is documented.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Local [supported] The CLI can run Amp on the user's own machine. Sources: amp:nov07-intro.
  • Byo remote [supported] Users can supply their own Orb compute through amp orb provider and a dispatch program. Sources: amp:gap07-self-orbs.
  • Self hosted [partial] Orb execution can be hosted on user infrastructure; this is not self-hosting the Amp control plane. Sources: amp:gap07-self-orbs.
  • Managed cloud [supported] Orbs are per-thread machines that continue working when the laptop closes. Sources: amp:nov07-intro.
  • Hybrid [supported] Per thread: Amp orb, a user runner, a self-hosted orb provider or a local CLI session. Sources: amp:b02-threads, amp:b02-sizes.
  • Provisioning [supported] Amp provisions an orb per thread from the project snapshot automatically. Sources: amp:b02-customizing, amp:b02-orbs.
  • Payer [supported] Amp-hosted orbs bill the thread owner per minute from tier minutes or credits; runners are free; self-hosted orbs are free except on Enterprise. Sources: amp:b02-sizes, amp:b02-pricing-docs, amp:b02-multiplayer.
  • Resources [supported] The size table lists per-Orb CPU, memory and 60 GB disk; default-size rules vary by project and plan. Sources: amp:nov07-orb-costs.
  • Region [partial] Primary infrastructure is GCP in the US; Enterprise lists regional endpoints for BYOK providers. No orb region choice is documented. Sources: amp:b02-security, amp:b02-pricing.
  • Expiry [supported] Orbs pause after idle timeouts, not run limits; paused filesystem and memory stay encrypted until the thread is deleted. Sources: amp:b02-sizes, amp:b02-security.
  • Client disconnect [supported] An orb agent keeps working with the laptop closed. Sources: amp:b02-orbs.
  • Other device continuation [supported] Open the thread from any app, the web or the CLI and keep prompting. Sources: amp:b02-orbs, amp:b02-threads.

Sources: amp:nov07-intro, amp:nov07-orb-costs, amp:gap07-self-orbs, amp:b02-orbs, amp:b02-sizes, amp:b02-security, amp:b02-threads, amp:b02-pricing-docs, amp:b02-multiplayer, amp:b02-customizing, amp:b02-pricing

Agent cross-checked partial

Runner worktree creation also creates a named branch. A runner creates a Git worktree and branch for a new thread; worktrees separate files without asserting a security sandbox. A documented Docker provider example runs each Orb as a container; this is a self-hosted execution option. Each Orb thread has a fresh isolated working environment; the shared terminal uses the same filesystem as that thread's agent. Docker-backed Orbs do not preserve memory across pause; terminals and desktop processes are lost on wake. Each runner worktree has its own working files and branch. Each orb thread gets its own fresh environment and working copy cloned from the project. Orbs reach the internet and can route web traffic through a user runner; Enterprise lists network and MCP access controls. Egress restrictions inside orbs are not documented. Secrets are injected from settings, OIDC issues short-lived credentials, GitHub tokens are fetched short-lived per command, and redaction keeps detected secrets out of threads. In multiplayer, every contributor can access the orb, its secrets, files and terminal; no hostile-code containment claim is made. Orbs are sandboxed cloud machines on e2b compute; the isolation technology is not specified.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: os_sandbox. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Checkout [supported] Each orb thread gets its own fresh environment and working copy cloned from the project. Sources: amp:b02-orbs, amp:b02-customizing.
  • Branch [supported] Runner worktree creation also creates a named branch. Sources: amp:gap07-runners.
  • Worktree [supported] A runner creates a Git worktree and branch for a new thread; worktrees separate files without asserting a security sandbox. Sources: amp:gap07-runners.
  • Container [supported] A documented Docker provider example runs each Orb as a container; this is a self-hosted execution option. Sources: amp:gap07-self-orbs.
  • Vm [partial] Orbs are sandboxed cloud machines on e2b compute; the isolation technology is not specified. Sources: amp:b02-security, amp:b02-orbs.
  • Os sandbox [unknown] Not established for os sandbox in the named first-party source pass. Product access and scenario tests were not run.
  • Filesystem [supported] Each Orb thread has a fresh isolated working environment; the shared terminal uses the same filesystem as that thread's agent. Sources: amp:nov07-orbs.
  • Process [partial] Docker-backed Orbs do not preserve memory across pause; terminals and desktop processes are lost on wake. Sources: amp:gap07-self-orbs.
  • Network [partial] Orbs reach the internet and can route web traffic through a user runner; Enterprise lists network and MCP access controls. Egress restrictions inside orbs are not documented. Sources: amp:b02-runners, amp:b02-pricing.
  • Secrets [supported] Secrets are injected from settings, OIDC issues short-lived credentials, GitHub tokens are fetched short-lived per command, and redaction keeps detected secrets out of threads. Sources: amp:b02-secrets, amp:b02-github, amp:b02-security.
  • Code separation [supported] Each runner worktree has its own working files and branch. Sources: amp:gap07-runners.
  • Security boundary [partial] In multiplayer, every contributor can access the orb, its secrets, files and terminal; no hostile-code containment claim is made. Sources: amp:b02-multiplayer.

Sources: amp:nov07-orbs, amp:gap07-runners, amp:gap07-self-orbs, amp:b02-orbs, amp:b02-customizing, amp:b02-runners, amp:b02-pricing, amp:b02-secrets, amp:b02-github, amp:b02-security, amp:b02-multiplayer

Agent cross-checked partial

Docker-backed Orb services restart when a portal is reopened after wake; terminal and desktop process state is not restored. An idle Orb wakes with conversation, files and services retained; worker-crash recovery was not tested. Docker-backed Orbs retain disk but lose terminal and desktop process state when paused. The orb agent keeps working when the client disconnects. No sandbox expiry: paused orbs are kept until the thread is deleted. The orb Terminal tab gives a shell on the agent's working copy. A sleeping orb costs nothing even for weeks and wakes with conversation, files and services. Services pause with the orb and are available again when it wakes; .agents/resume reconnects after each wake. Project snapshots plus .agents/setup and .agents/resume rebuild and repair orb state. Stored threads open in any client.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: worker_crash, duplicate_actions. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Client disconnect [supported] The orb agent keeps working when the client disconnects. Sources: amp:b02-orbs.
  • Worker crash [unknown] Not established for worker crash in the named first-party source pass. Product access and scenario tests were not run.
  • Service restart [partial] Docker-backed Orb services restart when a portal is reopened after wake; terminal and desktop process state is not restored. Sources: amp:gap07-self-orbs.
  • Expiry [supported] No sandbox expiry: paused orbs are kept until the thread is deleted. Sources: amp:b02-security.
  • Transcript reload [supported] Stored threads open in any client. Sources: amp:b02-threads.
  • Process reconnect [supported] Services pause with the orb and are available again when it wakes; .agents/resume reconnects after each wake. Sources: amp:b02-sizes, amp:b02-customizing.
  • Task resume [supported] An idle Orb wakes with conversation, files and services retained; worker-crash recovery was not tested. Sources: amp:nov07-orbs.
  • State reconstruction [supported] Project snapshots plus .agents/setup and .agents/resume rebuild and repair orb state. Sources: amp:b02-customizing.
  • Context loss [partial] Docker-backed Orbs retain disk but lose terminal and desktop process state when paused. Sources: amp:gap07-self-orbs.
  • Duplicate actions [unknown] Not established for duplicate actions in the named first-party source pass. Product access and scenario tests were not run.
  • Manual repair [supported] The orb Terminal tab gives a shell on the agent's working copy. Sources: amp:b02-orbs.
  • Multi day continuity [supported] A sleeping orb costs nothing even for weeks and wakes with conversation, files and services. Sources: amp:b02-orbs.

Sources: amp:nov07-orbs, amp:gap07-self-orbs, amp:b02-orbs, amp:b02-security, amp:b02-sizes, amp:b02-customizing, amp:b02-threads

Agent cross-checked partial

Install shared dependencies in .agents/setup. A matching prepared project snapshot is reused for up to 72 hours. Snapshots capture repository and setup changes and can be deleted from settings or CLI. Long-running processes belong in .amp/services.yaml or systemd, not setup. Shared setup and runtime use different credentials; setup credentials are removed before snapshotting. A matching project snapshot skips setup; freshness is limited to 72 hours and supported Git host checks. .agents/resume runs after activation and wake for authentication, repair or reconnect; successful automatic repair is not independently tested. .amp/services.yaml declares services, Amp manages PORT, and portals expose orb web servers. Pre-clone, pre-setup, .agents/setup, snapshots and .agents/resume prepare remote environments.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: collisions. No configured product fixture was run; documentation does not establish successful hands-on behavior.
10 atomic answers
  • Dependencies [supported] Install shared dependencies in .agents/setup. Sources: amp:gap07-customizing.
  • Caches [supported] A matching prepared project snapshot is reused for up to 72 hours. Sources: amp:gap07-customizing.
  • Snapshots [supported] Snapshots capture repository and setup changes and can be deleted from settings or CLI. Sources: amp:gap07-customizing.
  • Services [supported] Long-running processes belong in .amp/services.yaml or systemd, not setup. Sources: amp:gap07-customizing.
  • Ports [supported] .amp/services.yaml declares services, Amp manages PORT, and portals expose orb web servers. Sources: amp:b02-portals, amp:b02-customizing.
  • Secrets [supported] Shared setup and runtime use different credentials; setup credentials are removed before snapshotting. Sources: amp:gap07-customizing.
  • Duplicate installs [partial] A matching project snapshot skips setup; freshness is limited to 72 hours and supported Git host checks. Sources: amp:gap07-customizing.
  • Collisions [unknown] Not established for collisions in the named first-party source pass. Product access and scenario tests were not run.
  • Remote setup [supported] Pre-clone, pre-setup, .agents/setup, snapshots and .agents/resume prepare remote environments. Sources: amp:b02-customizing.
  • Automatic repair [partial] .agents/resume runs after activation and wake for authentication, repair or reconnect; successful automatic repair is not independently tested. Sources: amp:gap07-customizing.

Sources: amp:gap07-customizing, amp:b02-portals, amp:b02-customizing

Agent cross-checked partial

Setup stops after 20 minutes; a failed or timed-out setup does not publish a refreshed snapshot. Amp checks spend against each user's effective Enterprise entitlement; whether a reached limit stops work is not stated. Enterprise per-user entitlements such as $100/day or $50/week; Enterprise lists spend limits and reporting. No run-time limit: orbs pause only after 5- and 20-minute idle timeouts. Plugin webhook handlers have 30 seconds.

Scope
Surfaces: Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: turn_limits, token_limits, retries, provider_failures. No configured product fixture was run; documentation does not establish successful hands-on behavior.
8 atomic answers
  • Time limits [partial] No run-time limit: orbs pause only after 5- and 20-minute idle timeouts. Plugin webhook handlers have 30 seconds. Sources: amp:b02-sizes, amp:b02-automations.
  • Turn limits [unknown] Not established for turn limits in the named first-party source pass. Product access and scenario tests were not run.
  • Token limits [unknown] Not established for token limits in the named first-party source pass. Product access and scenario tests were not run.
  • Spend limits [supported] Enterprise per-user entitlements such as $100/day or $50/week; Enterprise lists spend limits and reporting. Sources: amp:b02-entitlements, amp:b02-pricing.
  • Timeouts [supported] Setup stops after 20 minutes; a failed or timed-out setup does not publish a refreshed snapshot. Sources: amp:gap07-customizing.
  • Retries [unknown] Not established for retries in the named first-party source pass. Product access and scenario tests were not run.
  • Provider failures [unknown] Not established for provider failures in the named first-party source pass. Product access and scenario tests were not run.
  • Enforcement [partial] Amp checks spend against each user's effective Enterprise entitlement; whether a reached limit stops work is not stated. Sources: amp:b02-entitlements.

Sources: amp:nov07-orb-costs, amp:gap07-customizing, amp:b02-entitlements, amp:b02-pricing, amp:b02-sizes, amp:b02-automations

Agent cross-checked partial

A Space chart counts the last 30 days of threads as Shipped, Archived or Open (Done where commits cannot be seen). Threads waiting for approval surface in the sidebar, even when snoozed, and notify. Failed automation runs show the error and failed repository setup links a Setup Log. Setup logs in orbs; threads keep every tool call and result. Each thread shows its cost so far. Thread storage preserves prompts, responses, tool calls, tool results and attachments as an audit trail. Usage Breakdown exports CSV; amp usage shows balance; a data management API exposes analytics.

Scope
Surfaces: Amp web, Mac and iOS · Version: Amp docs and chronicle retrieved 2026-11-12 (news through Nov 10, 2026) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-21
  • Only the atoms cited here are established from documentation; the remaining atoms stay unknown and no hands-on test was run.
13 atomic answers
  • Logs [supported] Setup logs in orbs; threads keep every tool call and result. Sources: amp:b02-customizing, amp:b02-security.
  • Traces [supported] Thread storage preserves prompts, responses, tool calls, tool results and attachments as an audit trail. Sources: amp:b02-security.
  • Failure reasons [supported] Failed automation runs show the error and failed repository setup links a Setup Log. Sources: amp:b02-automations, amp:b02-customizing.
  • Usage export [supported] Usage Breakdown exports CSV; amp usage shows balance; a data management API exposes analytics. Sources: amp:b02-workspaces, amp:b02-pricing-docs, amp:b02-security.
  • Task stats [supported] Each thread shows its cost so far. Sources: amp:b02-pricing-docs, amp:b02-threads.
  • Agent stats [unknown] Not established for agent stats in the named first-party source pass. Product access and scenario tests were not run.
  • Project stats [partial] A Space chart counts the last 30 days of threads as Shipped, Archived or Open (Done where commits cannot be seen). Sources: amp:nov12-spaces.
  • Time stats [unknown] Not established for time stats in the named first-party source pass. Product access and scenario tests were not run.
  • Failure status [unknown] Not established for failure status in the named first-party source pass. Product access and scenario tests were not run.
  • Approval status [supported] Threads waiting for approval surface in the sidebar, even when snoozed, and notify. Sources: amp:b02-threads.
  • Reconnect consistency [unknown] Not established for reconnect consistency in the named first-party source pass. Product access and scenario tests were not run.
  • Performance method [unknown] Not established for performance method in the named first-party source pass. Product access and scenario tests were not run.
  • Responsiveness [unknown] Not established for responsiveness in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:nov12-spaces, amp:b02-threads, amp:b02-automations, amp:b02-customizing, amp:b02-security, amp:b02-pricing-docs, amp:b02-workspaces

Agent cross-checked partial

A thread's dollar indicator opens detailed usage; this is documented, not reconciled against invoices. Orb minutes are priced per size and shown separately from model spend. Usage Breakdown exports CSV totals per period and a member summary. The $ price in each thread opens its cost detail. Tier allowances cover included usage; own subscriptions carry no Amp token fee and do not count toward entitlements. Per-thread dollar cost is shown in the thread. Usage can be viewed as tokens, and Amp explains a thread's token use on request.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Per-task API and compute cost: first-party sources in this pass did not establish child_cost, epic_cost, harness_aggregation, billed_vs_estimated, provider_reconciliation, refresh_delay, alerts. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.
14 atomic answers
  • Task cost [supported] Per-thread dollar cost is shown in the thread. Sources: amp:b02-pricing-docs, amp:b02-threads.
  • Session cost [supported] The $ price in each thread opens its cost detail. Sources: amp:b02-pricing-docs.
  • Child cost [unknown] Not established for child cost in the named first-party source pass. Product access and scenario tests were not run.
  • Epic cost [unknown] Not established for epic cost in the named first-party source pass. Product access and scenario tests were not run.
  • Harness aggregation [unknown] Not established for harness aggregation in the named first-party source pass. Product access and scenario tests were not run.
  • Billed vs estimated [unknown] Not established for billed vs estimated in the named first-party source pass. Product access and scenario tests were not run.
  • Tokens [supported] Usage can be viewed as tokens, and Amp explains a thread's token use on request. Sources: amp:b02-workspaces, amp:b02-pricing-docs.
  • Subscription allowance [supported] Tier allowances cover included usage; own subscriptions carry no Amp token fee and do not count toward entitlements. Sources: amp:b02-pricing-docs, amp:b02-pricing, amp:b02-entitlements.
  • Provider reconciliation [unknown] Not established for provider reconciliation in the named first-party source pass. Product access and scenario tests were not run.
  • Compute cost [supported] Orb minutes are priced per size and shown separately from model spend. Sources: amp:b02-sizes, amp:b02-workspaces.
  • Refresh delay [unknown] Not established for refresh delay in the named first-party source pass. Product access and scenario tests were not run.
  • Alerts [unknown] Not established for alerts in the named first-party source pass. Product access and scenario tests were not run.
  • Export [supported] Usage Breakdown exports CSV totals per period and a member summary. Sources: amp:b02-workspaces.
  • Drilldown [supported] A thread's dollar indicator opens detailed usage; this is documented, not reconciled against invoices. Sources: amp:nov07-pricing.

Sources: amp:nov07-pricing, amp:b02-sizes, amp:b02-workspaces, amp:b02-pricing-docs, amp:b02-pricing, amp:b02-entitlements, amp:b02-threads

Agent cross-checked partial

After a burst of twenty metered Orb starts per user, later starts queue at one every five minutes. Orb starts beyond the pacing limit wait with an estimated wait instead of failing. Archiving stops an orb; cancelling a waiting orb start is not documented. A 20-orb burst per user, then one new orb every five minutes. Orb size sets CPU and RAM per thread. Pacing is per user; Enterprise lists higher resource quotas and rate limits without numbers.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Compute-aware scheduling and verification: first-party sources in this pass did not establish host_awareness, check_reuse, check_deduplication, bounded_tests, fairness, recovery. No client-disconnect, crash/restart, resource-pressure or invoice-reconciliation fixture was run. Documented persistence is distinct from measured recovery.
12 atomic answers
  • Concurrency [supported] A 20-orb burst per user, then one new orb every five minutes. Sources: amp:b02-orbs.
  • Queues [supported] After a burst of twenty metered Orb starts per user, later starts queue at one every five minutes. Sources: amp:nov07-orbs.
  • Cpu ram [supported] Orb size sets CPU and RAM per thread. Sources: amp:b02-sizes.
  • Backpressure [supported] Orb starts beyond the pacing limit wait with an estimated wait instead of failing. Sources: amp:b02-orbs.
  • Host awareness [unknown] Not established for host awareness in the named first-party source pass. Product access and scenario tests were not run.
  • Check reuse [unknown] Not established for check reuse in the named first-party source pass. Product access and scenario tests were not run.
  • Check deduplication [unknown] Not established for check deduplication in the named first-party source pass. Product access and scenario tests were not run.
  • Bounded tests [unknown] Not established for bounded tests in the named first-party source pass. Product access and scenario tests were not run.
  • Cancellation [partial] Archiving stops an orb; cancelling a waiting orb start is not documented. Sources: amp:b02-sizes.
  • Fairness [unknown] Not established for fairness in the named first-party source pass. Product access and scenario tests were not run.
  • Recovery [unknown] Not established for recovery in the named first-party source pass. Product access and scenario tests were not run.
  • Shared limits [partial] Pacing is per user; Enterprise lists higher resource quotas and rate limits without numbers. Sources: amp:b02-orbs, amp:b02-pricing.

Sources: amp:nov07-orbs, amp:b02-orbs, amp:b02-sizes, amp:b02-pricing

Human collaboration and control

Agent cross-checked partial

Workspace members can chat with each other in the thread. Workspace teammates can prompt together in an enabled multiplayer thread. Further scoped facts are recorded in the atomic answers. Orb multiplayer does not need the owner online; runner multiplayer ends when the owner stops sharing the runner. Multiplayer needs a non-private thread in an orb or shared runner, lasts 7 days, and bills the owner. Restricted, workspace or link sharing; Enterprise adds groups.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Amp docs and chronicle retrieved 2026-11-12 (news through Nov 10, 2026) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Live human collaboration: first-party sources in this pass did not establish presence, ordering, conflicts, attribution. No two-account permission, simultaneous steering, revocation or colleague-takeover fixture was run. Sharing and presence do not establish co-prompting.
11 atomic answers
  • Visibility [supported] Restricted, workspace or link sharing; Enterprise adds groups. Sources: amp:b02-threads, amp:b02-visibility.
  • Discussion [supported] Workspace members can chat with each other in the thread. Sources: amp:nov07-multiplayer.
  • Comments [supported] Teammates comment in a Space; Amp reads a comment only when @amp is mentioned. Sources: amp:nov12-spaces.
  • Presence [unknown] Not established for presence in the named first-party source pass. Product access and scenario tests were not run.
  • Coprompting [supported] Workspace teammates can prompt together in an enabled multiplayer thread. Sources: amp:nov07-multiplayer.
  • Ordering [unknown] Not established for ordering in the named first-party source pass. Product access and scenario tests were not run.
  • Conflicts [unknown] Not established for conflicts in the named first-party source pass. Product access and scenario tests were not run.
  • Attribution [unknown] Not established for attribution in the named first-party source pass. Product access and scenario tests were not run.
  • Permissions [supported] Multiplayer grants workspace members access to that thread, machine, secrets, files and terminal. Sources: amp:nov07-multiplayer.
  • Plan restrictions [supported] Multiplayer needs a non-private thread in an orb or shared runner, lasts 7 days, and bills the owner. Sources: amp:b02-multiplayer.
  • Owner online [supported] Orb multiplayer does not need the owner online; runner multiplayer ends when the owner stops sharing the runner. Sources: amp:b02-multiplayer.

Sources: amp:nov07-multiplayer, amp:nov12-spaces, amp:b02-multiplayer, amp:b02-threads, amp:b02-visibility

Agent cross-checked partial

Member and Admin roles are documented; Admin manages membership, billing, settings and policies and can view private threads. Admins invite members; member email-invitation rights are configurable. Teams list SAML/OIDC SSO; Enterprise adds SCIM. Enterprise supports directory sync of members and groups. A non-enterprise workspace needs a paid Megawatt or Gigawatt member for SAML/OIDC SSO; Enterprise does not require a paid member tier. Workspace admins and the project creator edit project settings; other project roles are not documented. SCIM deprovisions users; admins remove members and can disable service accounts. Thread and Space Contributor or Viewer roles. Admins open restricted threads only through passkey re-authentication with audit logging; only workspace members can be added.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Organization roles [supported] Member and Admin roles are documented; Admin manages membership, billing, settings and policies and can view private threads. Sources: amp:gap07-workspaces.
  • Project roles [partial] Workspace admins and the project creator edit project settings; other project roles are not documented. Sources: amp:b02-projects.
  • Task roles [supported] Thread and Space Contributor or Viewer roles. Sources: amp:b02-threads, amp:b02-spaces.
  • Membership [supported] Admins invite members; member email-invitation rights are configurable. Sources: amp:gap07-workspaces.
  • Sso [supported] Teams list SAML/OIDC SSO; Enterprise adds SCIM. Sources: amp:nov07-pricing.
  • Provisioning [supported] Enterprise supports directory sync of members and groups. Sources: amp:gap07-workspaces.
  • Unauthorized access [partial] Admins open restricted threads only through passkey re-authentication with audit logging; only workspace members can be added. Sources: amp:b02-threads, amp:b02-security.
  • Revocation [supported] SCIM deprovisions users; admins remove members and can disable service accounts. Sources: amp:b02-security, amp:b02-workspaces.
  • Plan scope [supported] A non-enterprise workspace needs a paid Megawatt or Gigawatt member for SAML/OIDC SSO; Enterprise does not require a paid member tier. Sources: amp:gap07-workspaces.

Sources: amp:nov07-pricing, amp:gap07-workspaces, amp:b02-projects, amp:b02-security, amp:b02-workspaces, amp:b02-threads, amp:b02-spaces

Agent cross-checked partial

Multiplayer starts with a seven-day duration, can end early and expires automatically. Stopping runner sharing ends multiplayer on threads created on it. tool.call hooks return allow; amp.mcpPermissions rules allow servers. In multiplayer, the owner or a workspace admin approves box and secret changes and the owner approves Slack posts; contributors cannot. No approval by default; a policy plugin can gate commands. By default Amp runs tools without asking. Ship is a user action; Slack posting asks first by default; making a portal public requires approval when the agent asks. tool.call returns reject-and-continue; MCP rules reject servers; amp.tools.disable removes tools. The tool.call hook runs before every tool call. tool.call hooks, amp.tools.disable and amp.mcpPermissions. Portals are limited to thread viewers; public access lasts 1 hour to 7 days and can end early; runner portals cannot be public.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Approvals and temporary access: first-party sources in this pass did not establish network, secret, safer_modes. No two-account permission, simultaneous steering, revocation or colleague-takeover fixture was run. Sharing and presence do not establish co-prompting.
14 atomic answers
  • Command [partial] No approval by default; a policy plugin can gate commands. Sources: amp:b02-tools, amp:b02-plugins.
  • Tool [supported] tool.call hooks, amp.tools.disable and amp.mcpPermissions. Sources: amp:b02-plugins, amp:b02-settings.
  • Network [unknown] Not established for network in the named first-party source pass. Product access and scenario tests were not run.
  • Secret [unknown] Not established for secret in the named first-party source pass. Product access and scenario tests were not run.
  • Delivery [supported] Ship is a user action; Slack posting asks first by default; making a portal public requires approval when the agent asks. Sources: amp:b02-shipping, amp:b02-integrations, amp:b02-portals.
  • Approver identity [supported] In multiplayer, the owner or a workspace admin approves box and secret changes and the owner approves Slack posts; contributors cannot. Sources: amp:b02-multiplayer.
  • Lifetime [supported] Multiplayer starts with a seven-day duration, can end early and expires automatically. Sources: amp:nov07-multiplayer.
  • Allow [supported] tool.call hooks return allow; amp.mcpPermissions rules allow servers. Sources: amp:b02-plugins, amp:b02-settings.
  • Deny [supported] tool.call returns reject-and-continue; MCP rules reject servers; amp.tools.disable removes tools. Sources: amp:b02-plugins, amp:b02-settings.
  • Revoke [supported] Stopping runner sharing ends multiplayer on threads created on it. Sources: amp:nov07-multiplayer.
  • Tunnels [supported] Portals are limited to thread viewers; public access lasts 1 hour to 7 days and can end early; runner portals cannot be public. Sources: amp:b02-portals, amp:b02-runners.
  • Defaults [supported] By default Amp runs tools without asking. Sources: amp:b02-tools.
  • Safer modes [unknown] Not established for safer modes in the named first-party source pass. Product access and scenario tests were not run.
  • Enforcement [supported] The tool.call hook runs before every tool call. Sources: amp:b02-plugins.

Sources: amp:nov07-multiplayer, amp:b02-plugins, amp:b02-settings, amp:b02-multiplayer, amp:b02-tools, amp:b02-shipping, amp:b02-integrations, amp:b02-portals, amp:b02-runners

Agent cross-checked partial

Enterprise admins can access authentication event audit logs; comprehensive application audit logs remain internal. Each artifact save creates a revision and Share identifies the last editing thread agent. Artifacts export to Markdown, HTML or PDF; threads export to Markdown or owner-only JSON. Artifacts are editable, with a revision made for each save. Deleting a thread deletes its artifacts. A stale agent artifact write is refused when another revision was saved; the agent must merge its changes. Threads are stored on Amp Server and reopen across sessions. Enterprise threads and author attribution remain when users leave; non-Enterprise threads go with the account.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: approvals, discussion, decisions. No configured product fixture was run; documentation does not establish successful hands-on behavior.
11 atomic answers
  • Actions [partial] Enterprise admins can access authentication event audit logs; comprehensive application audit logs remain internal. Sources: amp:gap07-security.
  • Approvals [unknown] Not established for approvals in the named first-party source pass. Product access and scenario tests were not run.
  • Edits [supported] Each artifact save creates a revision and Share identifies the last editing thread agent. Sources: amp:gap07-threads.
  • Discussion [unknown] Not established for discussion in the named first-party source pass. Product access and scenario tests were not run.
  • Decisions [unknown] Not established for decisions in the named first-party source pass. Product access and scenario tests were not run.
  • Cross user persistence [supported] Enterprise threads and author attribution remain when users leave; non-Enterprise threads go with the account. Sources: amp:b02-security.
  • Cross session persistence [supported] Threads are stored on Amp Server and reopen across sessions. Sources: amp:b02-threads, amp:b02-security.
  • Export [supported] Artifacts export to Markdown, HTML or PDF; threads export to Markdown or owner-only JSON. Sources: amp:gap07-threads.
  • Mutability [supported] Artifacts are editable, with a revision made for each save. Sources: amp:gap07-threads.
  • Retention [supported] Deleting a thread deletes its artifacts. Sources: amp:gap07-threads.
  • Integrity [supported] A stale agent artifact write is refused when another revision was saved; the agent must merge its changes. Sources: amp:gap07-threads.

Sources: amp:gap07-security, amp:gap07-threads, amp:b02-threads, amp:b02-security

Agent cross-checked partial

The Changes pane offers all changes, uncommitted changes or a selected commit. The commit picker supports the right arrow key to read a commit message. Commits carry an Amp-Thread-ID trailer linking a code change back to its conversation. The portal review widget sends element comments to the agent; Space messages take comments. The Changes pane orders files by importance and picks commits; portals and Desktop show the running app. The phone apps give the same threads, orbs and Puck as ampcode.com, plus notifications, dictation and sharing from other apps; review-specific narrow-screen guidance is not documented in the checked Apps and iPhone pages. Reviewers reply in the thread or comment on the portal; a separate request-changes state is not documented in the checked Threads and Portals pages.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: pending_reviews, shipping_guidance, effort, missed_evidence, context_switching, roles. No configured product fixture was run; documentation does not establish successful hands-on behavior.
13 atomic answers
  • Pending reviews [unknown] Not established for pending reviews in the named first-party source pass. Product access and scenario tests were not run.
  • Change understanding [supported] The Changes pane offers all changes, uncommitted changes or a selected commit. Sources: amp:gap07-threads.
  • Evidence navigation [supported] The Changes pane orders files by importance and picks commits; portals and Desktop show the running app. Sources: amp:b02-threads, amp:b02-portals.
  • Comments [supported] The portal review widget sends element comments to the agent; Space messages take comments. Sources: amp:b02-portals, amp:b02-spaces.
  • Request changes [partial] Reviewers reply in the thread or comment on the portal; a separate request-changes state is not documented in the checked Threads and Portals pages. Sources: amp:b02-threads, amp:b02-portals.
  • Shipping guidance [unknown] Not established for shipping guidance in the named first-party source pass. Product access and scenario tests were not run.
  • Effort [unknown] Not established for effort in the named first-party source pass. Product access and scenario tests were not run.
  • Missed evidence [unknown] Not established for missed evidence in the named first-party source pass. Product access and scenario tests were not run.
  • Keyboard [supported] The commit picker supports the right arrow key to read a commit message. Sources: amp:gap07-threads.
  • Narrow screen [partial] The phone apps give the same threads, orbs and Puck as ampcode.com, plus notifications, dictation and sharing from other apps; review-specific narrow-screen guidance is not documented in the checked Apps and iPhone pages. Sources: amp:b02-apps, amp:b02-ios, amp:b152-apps.
  • Context switching [unknown] Not established for context switching in the named first-party source pass. Product access and scenario tests were not run.
  • Roles [unknown] Not established for roles in the named first-party source pass. Product access and scenario tests were not run.
  • Retained context [supported] Commits carry an Amp-Thread-ID trailer linking a code change back to its conversation. Sources: amp:gap07-threads.

Sources: amp:gap07-threads, amp:b02-portals, amp:b02-spaces, amp:b02-threads, amp:b02-apps, amp:b02-ios, amp:b152-apps

Agent cross-checked partial

Colleagues use the same thread and Orb or shared runner while multiplayer is active; disconnect takeover was not tested. Teammates and agents edit thread artifacts with revisions. Multiplayer contributors prompt the same thread. Transfer of thread ownership is not documented in the checked pages (Multiplayer, Threads, Spaces), which document only Space ownership transfer. Orb threads continue without the owner; runner multiplayer ends when the owner stops sharing. Contributors get the orb, secrets, files and terminal; the agent refuses account changes in multiplayer. Contributors use the orb's terminal, files and portals. The full thread history is shared.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Amp docs and chronicle retrieved 2026-11-12 (news through Nov 10, 2026) · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Colleague takeover and continuity: first-party sources in this pass did not establish decisions, attribution, context_loss, harness_transfer. No two-account permission, simultaneous steering, revocation or colleague-takeover fixture was run. Sharing and presence do not establish co-prompting.
12 atomic answers
  • Ongoing takeover [partial] Multiplayer contributors prompt the same thread. Transfer of thread ownership is not documented in the checked pages (Multiplayer, Threads, Spaces), which document only Space ownership transfer. Sources: amp:b02-multiplayer, amp:b02-spaces.
  • Same task [supported] Colleagues use the same thread and Orb or shared runner while multiplayer is active; disconnect takeover was not tested. Sources: amp:nov07-multiplayer.
  • Session history [supported] The full thread history is shared. Sources: amp:b02-threads.
  • Decisions [unknown] Not established for decisions in the named first-party source pass. Product access and scenario tests were not run.
  • Artifacts [supported] Teammates and agents edit thread artifacts with revisions. Sources: amp:b02-threads.
  • Permissions [supported] Contributors get the orb, secrets, files and terminal; the agent refuses account changes in multiplayer. Sources: amp:b02-multiplayer.
  • Runtime context [supported] Contributors use the orb's terminal, files and portals. Sources: amp:b02-multiplayer.
  • Owner disconnect [supported] Orb threads continue without the owner; runner multiplayer ends when the owner stops sharing. Sources: amp:b02-multiplayer.
  • Ownership [partial] A Space owner can transfer ownership once the recipient accepts; started threads stay with whoever started them. Sources: amp:nov12-spaces.
  • Attribution [unknown] Not established for attribution in the named first-party source pass. Product access and scenario tests were not run.
  • Context loss [unknown] Not established for context loss in the named first-party source pass. Product access and scenario tests were not run.
  • Harness transfer [unknown] Not established for harness transfer in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:nov07-multiplayer, amp:nov12-spaces, amp:b02-threads, amp:b02-multiplayer, amp:b02-spaces

Verification and delivery

Agent cross-checked partial

The thread's Changes view shows the diff, alongside files, services and conversation. Thread artifacts retain plans, reports and notes. The Artifacts tab groups multiple documents in folders. Artifact links in the transcript open the document in its thread. Artifacts and their uploaded images remain with the thread; deleting the thread deletes its artifacts. A child thread can edit or copy an accessible parent artifact, then notify its thread of the change. Portals expose orb web servers for preview. Desktop runs report what they did with screenshots, and delegated threads can return screenshots when asked; no screenshot gallery is documented. The thread holds the conversation, changes, running services and proof; test results are not a separate retained artifact.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: recordings, reviewer_outputs, revision_links, prompt_leakage. No configured product fixture was run; documentation does not establish successful hands-on behavior.
13 atomic answers
  • Diffs [supported] The thread's Changes view shows the diff, alongside files, services and conversation. Sources: amp:nov07-orbs.
  • Documents [supported] Thread artifacts retain plans, reports and notes. Sources: amp:gap07-threads.
  • Screenshots [partial] Desktop runs report what they did with screenshots, and delegated threads can return screenshots when asked; no screenshot gallery is documented. Sources: amp:b02-portals, amp:b02-a2a.
  • Recordings [unknown] Not established for recordings in the named first-party source pass. Product access and scenario tests were not run.
  • Previews [supported] Portals expose orb web servers for preview. Sources: amp:b02-portals.
  • Test outputs [partial] The thread holds the conversation, changes, running services and proof; test results are not a separate retained artifact. Sources: amp:b02-orbs.
  • Reviewer outputs [unknown] Not established for reviewer outputs in the named first-party source pass. Product access and scenario tests were not run.
  • Persistence [supported] Artifacts and their uploaded images remain with the thread; deleting the thread deletes its artifacts. Sources: amp:gap07-threads.
  • Child findings [supported] A child thread can edit or copy an accessible parent artifact, then notify its thread of the change. Sources: amp:gap07-threads.
  • Prompt leakage [unknown] Not established for prompt leakage in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:nov07-orbs, amp:gap07-threads, amp:b02-portals, amp:b02-a2a, amp:b02-orbs

Agent cross-checked partial

Default Ship asks the agent to run the full test suite. The documented agent instruction ignores a failing test only after confirming that it fails on the base branch too. This describes a prompt, not an independently enforced gate. A project can configure Ship Behavior or write a Custom Ship prompt. CI subscriptions follow an exact commit's checks and report failures. The default Ship prompt runs the full test suite before pushing, but gates are prompt instructions, not enforced policy. Optional: the Task subagent review skill, the oracle plugin and a built-in review prompt.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: lint, types, spec_checks, required_checks, requirement_conflicts. No configured product fixture was run; documentation does not establish successful hands-on behavior.
11 atomic answers
  • Tests [supported] Default Ship asks the agent to run the full test suite. Sources: amp:gap07-shipping.
  • Lint [unknown] Not established for lint in the named first-party source pass. Product access and scenario tests were not run.
  • Types [unknown] Not established for types in the named first-party source pass. Product access and scenario tests were not run.
  • Ci [supported] CI subscriptions follow an exact commit's checks and report failures. Sources: amp:b02-github.
  • Independent review [partial] Optional: the Task subagent review skill, the oracle plugin and a built-in review prompt. Sources: amp:b02-models, amp:b02-puck.
  • Spec checks [unknown] Not established for spec checks in the named first-party source pass. Product access and scenario tests were not run.
  • Required checks [unknown] Not established for required checks in the named first-party source pass. Product access and scenario tests were not run.
  • Failure blocking [partial] The documented agent instruction ignores a failing test only after confirming that it fails on the base branch too. This describes a prompt, not an independently enforced gate. Sources: amp:gap07-shipping.
  • Requirement conflicts [unknown] Not established for requirement conflicts in the named first-party source pass. Product access and scenario tests were not run.
  • Configured policy [supported] A project can configure Ship Behavior or write a Custom Ship prompt. Sources: amp:gap07-shipping.
  • Enforced policy [partial] The default Ship prompt runs the full test suite before pushing, but gates are prompt instructions, not enforced policy. Sources: amp:b02-shipping.

Sources: amp:gap07-shipping, amp:b02-github, amp:b02-shipping, amp:b02-models, amp:b02-puck

Agent cross-checked supported

Push to Branch ships to a feature branch instead of the base branch. Default Ship commits uncommitted files before rebasing and pushing. Orbs can push branches and open PRs using a connected GitHub identity. Default Ship rebases on the latest base branch and repeats after a concurrent push. The agent resolves conflicts and asks the user before proceeding on substantive conflicts. A PR linked by thread URL or ID appears in the thread title bar with open, draft, queued, merged or closed status. The agent follows CI for a commit and addresses PR feedback from subscriptions. PR subscriptions deliver reviews and inline review comments to the thread. Runners create a Git worktree per thread when asked, also for agent-started threads.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Branches [supported] Push to Branch ships to a feature branch instead of the base branch. Sources: amp:gap07-shipping.
  • Worktrees [supported] Runners create a Git worktree per thread when asked, also for agent-started threads. Sources: amp:b02-runners.
  • Commits [supported] Default Ship commits uncommitted files before rebasing and pushing. Sources: amp:gap07-shipping.
  • Pull requests [supported] Orbs can push branches and open PRs using a connected GitHub identity. Sources: amp:nov07-github.
  • Comments [supported] PR subscriptions deliver reviews and inline review comments to the thread. Sources: amp:b02-github, amp:b02-chronicle.
  • Ci response [supported] The agent follows CI for a commit and addresses PR feedback from subscriptions. Sources: amp:b02-github.
  • Rebase [supported] Default Ship rebases on the latest base branch and repeats after a concurrent push. Sources: amp:gap07-shipping.
  • Conflicts [supported] The agent resolves conflicts and asks the user before proceeding on substantive conflicts. Sources: amp:gap07-shipping.
  • Product state [supported] A PR linked by thread URL or ID appears in the thread title bar with open, draft, queued, merged or closed status. Sources: amp:nov07-github.

Sources: amp:nov07-github, amp:gap07-shipping, amp:b02-github, amp:b02-chronicle, amp:b02-runners

Agent cross-checked partial

Default Ship writes directly to the base branch after rebasing; PR approval and merge-policy enforcement are not established. Ship behavior is a project-configured agent prompt. The source does not establish an immutable authorization boundary. A user presses Ship to start delivery, and substantive rebase conflicts are checked with the user; a separate approval gate is not documented in the checked Shipping page. amp boxes deploy builds and serves an app on a box; service-account CI can redeploy.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: release, exact_revision. No configured product fixture was run; documentation does not establish successful hands-on behavior.
6 atomic answers
  • Approve [partial] A user presses Ship to start delivery, and substantive rebase conflicts are checked with the user; a separate approval gate is not documented in the checked Shipping page. Sources: amp:b02-shipping.
  • Merge [partial] Default Ship writes directly to the base branch after rebasing; PR approval and merge-policy enforcement are not established. Sources: amp:gap07-shipping.
  • Release [unknown] Not established for release in the named first-party source pass. Product access and scenario tests were not run.
  • Deploy [supported] amp boxes deploy builds and serves an app on a box; service-account CI can redeploy. Sources: amp:b02-boxes, amp:b02-workspaces.
  • Exact revision [unknown] Not established for exact revision in the named first-party source pass. Product access and scenario tests were not run.
  • Authority enforcement [partial] Ship behavior is a project-configured agent prompt. The source does not establish an immutable authorization boundary. Sources: amp:gap07-shipping.

Sources: amp:gap07-shipping, amp:b02-shipping, amp:b02-boxes, amp:b02-workspaces

Agent cross-checked partial

The thread records linked PRs when the PR description includes its thread URL or ID. Threads show commit and PR previews with status; CI subscriptions report check results. Commits carry an Amp-Thread-ID trailer, and a PR description with the trailer lists the PR in the thread. Space progress counts a thread shipped when its commits reach the default branch, its PR merges or Ship archives it. Box deploys return the app URL on onamp.dev; linking a deployment to the thread is not documented. The thread keeps conversation, code changes, running services and proof.

Scope
Surfaces: Amp web, Mac and iOS, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Completion evidence and rollback: first-party sources in this pass did not establish rollback, revert, stale_approval_invalidation. No draft PR, failed-gate, stale-approval, rollback or six-task batch-review fixture was run. Described actions do not prove delivery authority.
9 atomic answers
  • Delivery status [supported] Space progress counts a thread shipped when its commits reach the default branch, its PR merges or Ship archives it. Sources: amp:b02-spaces.
  • Retained evidence [supported] The thread keeps conversation, code changes, running services and proof. Sources: amp:b02-orbs.
  • Rollback [unknown] Not established for rollback in the named first-party source pass. Product access and scenario tests were not run.
  • Revert [unknown] Not established for revert in the named first-party source pass. Product access and scenario tests were not run.
  • Stale approval invalidation [unknown] Not established for stale approval invalidation in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:nov07-github, amp:b02-github, amp:b02-threads, amp:b02-spaces, amp:b02-boxes, amp:b02-orbs

Agent cross-checked partial

TypeSafe's Jev model suggests the next action in a thread; no review queue is documented.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public first-party sources checked 2026-11-21; no installed release tested · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Unknown after the 2026-11-21 backfill re-verification of first-party sources: review_queue, summaries, grouping, risk_size_filters, findings, artifacts, request_changes, exact_revision_approval, dependency_queues, stale_approval_invalidation, check_deduplication. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Review queue [unknown] Not established for review queue in the named first-party source pass. Product access and scenario tests were not run.
  • Summaries [unknown] Not established for summaries in the named first-party source pass. Product access and scenario tests were not run.
  • Grouping [unknown] Not established for grouping in the named first-party source pass. Product access and scenario tests were not run.
  • Risk size filters [unknown] Not established for risk size filters in the named first-party source pass. Product access and scenario tests were not run.
  • Findings [unknown] Not established for findings in the named first-party source pass. Product access and scenario tests were not run.
  • Artifacts [unknown] Not established for artifacts in the named first-party source pass. Product access and scenario tests were not run.
  • Request changes [unknown] Not established for request changes in the named first-party source pass. Product access and scenario tests were not run.
  • Exact revision approval [unknown] Not established for exact revision approval in the named first-party source pass. Product access and scenario tests were not run.
  • Dependency queues [unknown] Not established for dependency queues in the named first-party source pass. Product access and scenario tests were not run.
  • Next actions [partial] TypeSafe's Jev model suggests the next action in a thread; no review queue is documented. Sources: amp:b02-security.
  • Stale approval invalidation [unknown] Not established for stale approval invalidation in the named first-party source pass. Product access and scenario tests were not run.
  • Check deduplication [unknown] Not established for check deduplication in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:b02-security

Ownership, privacy and economics

Agent cross-checked partial

Amp access is covered by the limited, revocable service license in its custom terms. The hosted service is governed by Amp License Terms; an open-source server license was not established. Plugins and skills are user-supplied code in personal, workspace or project locations; licenses of Amp's own published plugins were not established.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: source_visibility, source_revision, hosted_parity. No configured product fixture was run; documentation does not establish successful hands-on behavior.
6 atomic answers
  • Client license [supported] Amp access is covered by the limited, revocable service license in its custom terms. Sources: amp:gap07-terms.
  • Server license [supported] The hosted service is governed by Amp License Terms; an open-source server license was not established. Sources: amp:gap07-terms.
  • Hosted extensions [partial] Plugins and skills are user-supplied code in personal, workspace or project locations; licenses of Amp's own published plugins were not established. Sources: amp:b02-plugins, amp:b02-skills.
  • Source visibility [unknown] Not established for source visibility in the named first-party source pass. Product access and scenario tests were not run.
  • Source revision [unknown] Not established for source revision in the named first-party source pass. Product access and scenario tests were not run.
  • Hosted parity [unknown] Not established for hosted parity in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:gap07-terms, amp:b02-plugins, amp:b02-skills

Agent cross-checked partial

Amp explicitly says it does not offer self-hosted deployments of its control plane. Self-hosted Orbs are execution workers. Threads export to Markdown, with full JSON available to the creator. Thread export formats are Markdown and JSON; artifacts export Markdown, HTML and PDF. Thread transcripts can be exported; importing an exported history was not established. An Amp account is required and the server is not self-hostable; self-hosted orb providers still connect to Amp. What remains usable without Amp is not documented in the checked pages (Security reference, Self-hosted orbs). Cancel any time; the paid tier lasts to the period end. Account deletion removes owned threads within 30 days, except Enterprise workspace threads. Amp Server handles accounts, threads, sync and usage; model requests go from Amp servers; e2b provides orb compute.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: import. No configured product fixture was run; documentation does not establish successful hands-on behavior.
8 atomic answers
  • Self hosting [unsupported] Amp explicitly says it does not offer self-hosted deployments of its control plane. Self-hosted Orbs are execution workers. Sources: amp:gap07-security.
  • Vendor dependencies [supported] Amp Server handles accounts, threads, sync and usage; model requests go from Amp servers; e2b provides orb compute. Sources: amp:b02-routing, amp:b02-security.
  • Export [supported] Threads export to Markdown, with full JSON available to the creator. Sources: amp:gap07-threads.
  • Import [unknown] Not established for import in the named first-party source pass. Product access and scenario tests were not run.
  • Formats [supported] Thread export formats are Markdown and JSON; artifacts export Markdown, HTML and PDF. Sources: amp:gap07-threads.
  • Cancellation [supported] Cancel any time; the paid tier lasts to the period end. Account deletion removes owned threads within 30 days, except Enterprise workspace threads. Sources: amp:b02-pricing, amp:b02-security.
  • Account independence [partial] An Amp account is required and the server is not self-hostable; self-hosted orb providers still connect to Amp. What remains usable without Amp is not documented in the checked pages (Security reference, Self-hosted orbs). Sources: amp:b02-security, amp:b02-selfhosted.
  • History portability [partial] Thread transcripts can be exported; importing an exported history was not established. Sources: amp:gap07-threads.

Sources: amp:gap07-security, amp:gap07-threads, amp:b02-security, amp:b02-selfhosted, amp:b02-pricing, amp:b02-routing

Agent cross-checked partial

Local code snippets and context can be sent to Amp Server and model providers. Prompts and conversation history are sent to Amp Server and then inference providers. Authentication audit logs are available to Enterprise admins; internal application logs are not exposed to admins. Enterprise workspace threads remain until the enterprise contract ends, including after the author leaves. Deleting a thread also deletes its associated Orb, usually within seconds. Training can be toggled in Settings Privacy; workspace enabling requires admin approval. Amp Server stores data in a multi-tenant Google Cloud Platform project; its primary infrastructure is hosted in the US, and no narrower region is stated. Personal provider subscription terms and data controls apply independently of Amp training settings. Attachments stay private to the thread under access checks; deleted threads and their data are removed within 30 days. Training requires explicit opt-in and workspace admin approval, never on Enterprise; no first-run consent dialog is documented. Best-effort secret redaction before content reaches threads or providers; stored secrets are encrypted; the CLI keeps credentials in ~/.local/share/amp/secrets.json. The security reference lists GCP, Anthropic, OpenAI, SpaceXAI, Meta, Vertex, Bedrock, Baseten, TypeSafe, e2b, Pierre, LiveKit, Parallel, Cloudflare Email, WorkOS, Stripe and others, with what each sees. Telemetry is stored with thread and user data in a GCP project; what is collected and opt-out controls are not described.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: telemetry_defaults, telemetry_controls. No configured product fixture was run; documentation does not establish successful hands-on behavior.
15 atomic answers
  • Code data [supported] Local code snippets and context can be sent to Amp Server and model providers. Sources: amp:gap07-security.
  • Prompts [supported] Prompts and conversation history are sent to Amp Server and then inference providers. Sources: amp:gap07-security.
  • Credentials [supported] Best-effort secret redaction before content reaches threads or providers; stored secrets are encrypted; the CLI keeps credentials in ~/.local/share/amp/secrets.json. Sources: amp:b02-security, amp:b02-routing.
  • Logs [supported] Authentication audit logs are available to Enterprise admins; internal application logs are not exposed to admins. Sources: amp:gap07-security.
  • Artifacts [supported] Attachments stay private to the thread under access checks; deleted threads and their data are removed within 30 days. Sources: amp:b02-files, amp:b02-security.
  • Retention [supported] Enterprise workspace threads remain until the enterprise contract ends, including after the author leaves. Sources: amp:gap07-security.
  • Deletion [supported] Deleting a thread also deletes its associated Orb, usually within seconds. Sources: amp:gap07-security.
  • Training [supported] Training can be toggled in Settings Privacy; workspace enabling requires admin approval. Sources: amp:gap07-security.
  • Residency [partial] Amp Server stores data in a multi-tenant Google Cloud Platform project; its primary infrastructure is hosted in the US, and no narrower region is stated. Sources: amp:gap07-security.
  • Subprocessors [supported] The security reference lists GCP, Anthropic, OpenAI, SpaceXAI, Meta, Vertex, Bedrock, Baseten, TypeSafe, e2b, Pierre, LiveKit, Parallel, Cloudflare Email, WorkOS, Stripe and others, with what each sees. Sources: amp:b02-security.
  • Telemetry disclosure [partial] Telemetry is stored with thread and user data in a GCP project; what is collected and opt-out controls are not described. Sources: amp:b02-security.
  • Telemetry defaults [unknown] Not established for telemetry defaults in the named first-party source pass. Product access and scenario tests were not run.
  • Telemetry controls [unknown] Not established for telemetry controls in the named first-party source pass. Product access and scenario tests were not run.
  • Provider separation [supported] Personal provider subscription terms and data controls apply independently of Amp training settings. Sources: amp:gap07-security.

Sources: amp:gap07-security, amp:b02-files, amp:b02-security, amp:b02-routing

Agent cross-checked partial

Public tiers are Hobby free, Megawatt $20/month, Gigawatt $200/month, Teams at no additional workspace charge and custom Enterprise. Team members retain individual tiers; model/tool and Orb usage are separately metered. No seat minimum: workspaces cost nothing and members can stay on Hobby; SAML/OIDC SSO needs one paid member; Enterprise has pooled credits and no paid seats. Invoices are issued through Stripe, which accepts VAT IDs; tax treatment is not otherwise stated.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
generally-available
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: trial. No configured product fixture was run; documentation does not establish successful hands-on behavior.
12 atomic answers
  • Currency [supported] Public tier prices are USD. Sources: amp:gap07-pricing.
  • Interval [supported] Megawatt and Gigawatt are monthly tiers. Sources: amp:gap35-pricing.
  • Seats [partial] Teams have no additional workspace/seat charge; each member retains an individual tier. Enterprise pricing is custom. Sources: amp:gap35-pricing.
  • Seat minimum [supported] No seat minimum: workspaces cost nothing and members can stay on Hobby; SAML/OIDC SSO needs one paid member; Enterprise has pooled credits and no paid seats. Sources: amp:b02-pricing, amp:b02-pricing-docs.
  • Workspace fees [supported] Teams carry no extra charge; Enterprise has custom pricing. Sources: amp:gap07-pricing.
  • Included usage [supported] Megawatt includes $20 monthly agent usage and 750 hours of a1.small Orbs; larger sizes consume the allowance faster. Sources: amp:gap07-pricing.
  • Credits [supported] Purchased credits expire twelve months after purchase and workspace credits are shared. Sources: amp:gap07-pricing.
  • Trial [unknown] Not established for trial in the named first-party source pass. Product access and scenario tests were not run.
  • Overages [supported] Users can buy credits after consuming included agent usage. Sources: amp:gap07-pricing.
  • Taxes [partial] Invoices are issued through Stripe, which accepts VAT IDs; tax treatment is not otherwise stated. Sources: amp:b02-pricing-docs.
  • Model cost [supported] Own subscriptions and API keys have no Amp fees outside Enterprise; Amp-hosted model credits follow provider prices without markup for non-enterprise users. Sources: amp:gap07-pricing.
  • Compute cost [supported] At the 7 November check, a1.medium lists 4 CPUs, 8 GB RAM and $0.33/hour, billed per minute; other sizes differ. Sources: amp:nov07-orb-costs.

Sources: amp:nov07-pricing, amp:nov07-orb-costs, amp:gap07-pricing, amp:gap35-pricing, amp:b02-pricing, amp:b02-pricing-docs

Agent cross-checked partial

Orbs cost $0.08-$2.13 per hour by size, billed per minute and only while running; Megawatt includes 45,000 orb minutes. Hobby $0, Megawatt $20 ($10 with the education discount), Megawatt 50 $50 and Gigawatt $200 per month; Teams adds no fee; Enterprise is custom. Gigawatt is listed in the docs pricing table (last modified 2026-11-17) and was recorded at $200 on 2026-11-13; the interactive pricing page shows it only behind a toggled tab, so it was not re-observed in that page's static HTML on 2026-11-21. Megawatt includes $20 of agent usage and 45,000 a1.small orb minutes; Megawatt 50 includes 2.5 times that; Gigawatt includes $200 of agent usage and 1,000 hours of a1.xxlarge orbs. Included usage resets monthly without rollover. One person: Hobby $0 with pay-as-you-go credits and orbs, or Megawatt $20 with included usage; model usage beyond is billed at provider API price. Two people: a free Teams workspace, each member on Hobby ($0), Megawatt ($20), Megawatt 50 ($50) or Gigawatt ($200); by default the workspace pays its members' paid tiers, and multiplayer costs go to the thread owner. Megawatt-only scenario: five people cost $0 (all Hobby) to $100 per month (all on Megawatt) in platform tiers; the range excludes Megawatt 50 ($50 each) and Gigawatt ($200 each). A Team workspace can set a Megawatt or Gigawatt base tier for all members and by default pays members' tiers. Credits and orb minutes beyond included usage are extra; workload cost is not priced. Credits pay actual model and tool usage without markup for non-enterprise accounts; orbs bill per minute by size; boxes bill separately. Per-task model spend varies and is not estimated in advance; Amp can explain a thread's usage afterwards. Enterprise pricing is custom.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public first-party sources checked 2026-11-21; no installed release tested · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-21 (1 day old)
Agent cross-check
2026-11-21
  • Unknown after the 2026-11-21 backfill re-verification of first-party sources: task_assumptions, concurrency, tokens. No configured product fixture was run; documentation does not establish successful hands-on behavior.
11 atomic answers
  • One person [partial] One person: Hobby $0 with pay-as-you-go credits and orbs, or Megawatt $20 with included usage; model usage beyond is billed at provider API price. Sources: amp:b02-pricing-docs.
  • Two people [partial] Two people: a free Teams workspace, each member on Hobby ($0), Megawatt ($20), Megawatt 50 ($50) or Gigawatt ($200); by default the workspace pays its members' paid tiers, and multiplayer costs go to the thread owner. Sources: amp:b02-pricing-docs, amp:b02-multiplayer, amp:b152-md-pricing, amp:b152-workspaces-billing.
  • Five people [partial] Megawatt-only scenario: five people cost $0 (all Hobby) to $100 per month (all on Megawatt) in platform tiers; the range excludes Megawatt 50 ($50 each) and Gigawatt ($200 each). A Team workspace can set a Megawatt or Gigawatt base tier for all members and by default pays members' tiers. Credits and orb minutes beyond included usage are extra; workload cost is not priced. Sources: amp:b02-pricing-docs, amp:b02-pricing, amp:b152-md-pricing, amp:b152-workspaces-billing.
  • Task assumptions [unknown] Not established for task assumptions in the named first-party source pass. Product access and scenario tests were not run.
  • Concurrency [unknown] Not established for concurrency in the named first-party source pass. Product access and scenario tests were not run.
  • Tokens [unknown] Not established for tokens in the named first-party source pass. Product access and scenario tests were not run.
  • Compute hours [supported] Orbs cost $0.08-$2.13 per hour by size, billed per minute and only while running; Megawatt includes 45,000 orb minutes. Sources: amp:b02-sizes, amp:b02-pricing-docs.
  • Fixed cost [partial] Hobby $0, Megawatt $20 ($10 with the education discount), Megawatt 50 $50 and Gigawatt $200 per month; Teams adds no fee; Enterprise is custom. Gigawatt is listed in the docs pricing table (last modified 2026-11-17) and was recorded at $200 on 2026-11-13; the interactive pricing page shows it only behind a toggled tab, so it was not re-observed in that page's static HTML on 2026-11-21. Sources: amp:b02-pricing-docs, amp:b152-md-pricing, amp:gap35-pricing.
  • Variable cost [supported] Credits pay actual model and tool usage without markup for non-enterprise accounts; orbs bill per minute by size; boxes bill separately. Sources: amp:b02-pricing-docs, amp:b02-sizes, amp:b02-boxes.
  • Included cost [supported] Megawatt includes $20 of agent usage and 45,000 a1.small orb minutes; Megawatt 50 includes 2.5 times that; Gigawatt includes $200 of agent usage and 1,000 hours of a1.xxlarge orbs. Included usage resets monthly without rollover. Sources: amp:b02-pricing-docs, amp:b152-md-pricing.
  • Unknown cost [partial] Per-task model spend varies and is not estimated in advance; Amp can explain a thread's usage afterwards. Enterprise pricing is custom. Sources: amp:b02-pricing-docs, amp:b152-md-pricing.

Sources: amp:b02-sizes, amp:b02-pricing-docs, amp:b02-pricing, amp:b02-multiplayer, amp:b02-boxes, amp:b152-md-pricing, amp:b152-workspaces-billing, amp:gap35-pricing

Agent cross-checked partial

Dated releases include Android (Oct 27), Artifacts (Nov 2), Service Accounts (Nov 3), GitLab (Nov 5), Spaces (Nov 6) and Boxes (Nov 10, 2026). macOS 26+ on Apple silicon; iOS 26+ via TestFlight; Android 13+ by APK; Windows 10 1809+; listed Linux distributions; a1.3xlarge only for Gigawatt and Enterprise. The JetBrains integration is deprecated without updates; Amp states it removes unused features and keeps no backward compatibility. Threads export as Markdown, or full JSON for the creator, from the menu or CLI. The iOS app is a TestFlight beta pending App Store release. ampcodestatus.com with email, RSS and Slack alerts; @ampcodestatus on X. Bug reports from clients, help via X or email; Enterprise lists priority support.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Amp docs and chronicle retrieved 2026-11-12 (news through Nov 10, 2026) · Plan: Not specified · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-12 (10 days old)
Agent cross-check
2026-11-21
  • Only the atoms cited here are established from documentation; the remaining atoms stay unknown and no hands-on test was run.
8 atomic answers
  • Release stage [partial] The iOS app is a TestFlight beta pending App Store release. Sources: amp:b02-ios.
  • Access restrictions [supported] macOS 26+ on Apple silicon; iOS 26+ via TestFlight; Android 13+ by APK; Windows 10 1809+; listed Linux distributions; a1.3xlarge only for Gigawatt and Enterprise. Sources: amp:b02-help, amp:b02-sizes.
  • Support [supported] Bug reports from clients, help via X or email; Enterprise lists priority support. Sources: amp:b02-help, amp:b02-pricing.
  • Response commitments [unknown] Not established for response commitments in the named first-party source pass. Product access and scenario tests were not run.
  • Release activity [supported] Dated releases include Android (Oct 27), Artifacts (Nov 2), Service Accounts (Nov 3), GitLab (Nov 5), Spaces (Nov 6) and Boxes (Nov 10, 2026). Sources: amp:nov12-chronicle.
  • Status history [supported] ampcodestatus.com with email, RSS and Slack alerts; @ampcodestatus on X. Sources: amp:b02-help.
  • Deprecation [supported] The JetBrains integration is deprecated without updates; Amp states it removes unused features and keeps no backward compatibility. Sources: amp:b02-help, amp:b02-intro.
  • Export options [supported] Threads export as Markdown, or full JSON for the creator, from the menu or CLI. Sources: amp:b02-threads.

Sources: amp:nov12-chronicle, amp:b02-help, amp:b02-sizes, amp:b02-intro, amp:b02-threads, amp:b02-ios, amp:b02-pricing

Agent cross-checked partial

Amp publicly states SOC 2 Type II certification; the underlying report was not inspected. Vendor security statement only; certificate issuer, validity period and report scope were not independently verified. SOC 2 Type II reports are available on request through the Security Trust Portal; not publicly downloadable. The vendor SOC 2 Type II statement was re-read on 2026-11-21; the report, audit period and covered services were not accessed.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: First-party documentation; client, plan and execution restrictions are named per atomic answer. Unlisted parity is unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
unknown
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: iso_scope, iso_issuer, iso_validity, soc2_scope, soc2_period. No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Iso scope [unknown] Not established for iso scope in the named first-party source pass. Product access and scenario tests were not run.
  • Iso issuer [unknown] Not established for iso issuer in the named first-party source pass. Product access and scenario tests were not run.
  • Iso validity [unknown] Not established for iso validity in the named first-party source pass. Product access and scenario tests were not run.
  • Soc2 type [supported] Amp publicly states SOC 2 Type II certification; the underlying report was not inspected. Sources: amp:gap07-security.
  • Soc2 scope [unknown] Not established for soc2 scope in the named first-party source pass. Product access and scenario tests were not run.
  • Soc2 period [unknown] Not established for soc2 period in the named first-party source pass. Product access and scenario tests were not run.
  • Report access [supported] SOC 2 Type II reports are available on request through the Security Trust Portal; not publicly downloadable. Sources: amp:b02-security.
  • Verification date [partial] The vendor SOC 2 Type II statement was re-read on 2026-11-21; the report, audit period and covered services were not accessed. Sources: amp:b02-security.
  • Evidence status [partial] Vendor security statement only; certificate issuer, validity period and report scope were not independently verified. Sources: amp:gap07-security.

Sources: amp:gap07-security, amp:b02-security

Agent cross-checked partial

The Hobby tier is recurring free; model usage and hosted compute may still cost money. Self-hosted Orbs and own subscriptions or API keys have no Amp fee for individuals and teams; infrastructure and provider costs remain. Hobby includes no usage. Own subscriptions and API keys have no Amp token fees or limits outside Enterprise; provider limits still apply. The iOS app is a public TestFlight beta that needs no invitation. Hobby is free with own subscriptions or keys, free self-hosted orbs and runners, and pay-as-you-go orbs; a Teams workspace with sharing and multiplayer costs nothing extra. a1.3xlarge needs Gigawatt or Enterprise; SAML/OIDC SSO needs a paid member; service accounts need Enterprise or bought Team credits; SCIM, audit logs and IP allowlisting are Enterprise.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: Not specified · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • Unknown after the targeted first-party documentation, release and repository pass: trial, credits_trial, card_required, paid_evaluation. No configured product fixture was run; documentation does not establish successful hands-on behavior.
10 atomic answers
  • Ongoing free [supported] The Hobby tier is recurring free; model usage and hosted compute may still cost money. Sources: amp:gap07-pricing.
  • Trial [unknown] Not established for trial in the named first-party source pass. Product access and scenario tests were not run.
  • Credits trial [unknown] Not established for credits trial in the named first-party source pass. Product access and scenario tests were not run.
  • Self host cost [supported] Self-hosted Orbs and own subscriptions or API keys have no Amp fee for individuals and teams; infrastructure and provider costs remain. Sources: amp:gap07-pricing.
  • Paid only [supported] a1.3xlarge needs Gigawatt or Enterprise; SAML/OIDC SSO needs a paid member; service accounts need Enterprise or bought Team credits; SCIM, audit logs and IP allowlisting are Enterprise. Sources: amp:b02-sizes, amp:b02-pricing, amp:b02-workspaces.
  • Early access [supported] The iOS app is a public TestFlight beta that needs no invitation. Sources: amp:b02-ios.
  • Free scenarios [supported] Hobby is free with own subscriptions or keys, free self-hosted orbs and runners, and pay-as-you-go orbs; a Teams workspace with sharing and multiplayer costs nothing extra. Sources: amp:b02-pricing-docs, amp:b02-pricing.
  • Card required [unknown] Not established for card required in the named first-party source pass. Product access and scenario tests were not run.
  • Usage caps [partial] Hobby includes no usage. Own subscriptions and API keys have no Amp token fees or limits outside Enterprise; provider limits still apply. Sources: amp:gap07-pricing.
  • Paid evaluation [unknown] Not established for paid evaluation in the named first-party source pass. Product access and scenario tests were not run.

Sources: amp:nov07-pricing, amp:gap07-pricing, amp:b02-ios, amp:b02-pricing-docs, amp:b02-pricing, amp:b02-sizes, amp:b02-workspaces

Agent cross-checked supported

Agent usage is billed in credits and Orb compute by the minute. Megawatt includes $20 agent usage and 45,000 minutes of a1.small Orbs monthly. Paid credits permit continued model and tool usage beyond the monthly allowance. Self-hosted orbs are free on Hobby, Individual and Teams; Enterprise workspaces pay 100% of the standard orb price, billed per minute while the orb is connected to a thread, with volume discounts on request. The guide states no provider API markup for individuals and non-enterprise workspaces. Paid credits require no paid tier or commitment. Enterprise uses custom pricing. Cancel any time in user settings; the tier stays active to the end of the month. Partially specified: tier prices including Gigawatt $200, orb rates and no-markup credits are public; Enterprise is quote-only.

Scope
Surfaces: Amp web, Mac and iOS, Amp CLI, Amp Orbs · Version: Public sources checked 2026-11-07; no installed release tested · Plan: Plan restrictions and client/mode boundaries are stated per atomic answer; unlisted parity remains unknown. · OS: Not specified · Execution modes: managed-cloud, self-hosted · Region: Not specified · Harness: Not specified
Availability
unknown
Delivery
native
Checked
2026-11-07 (15 days old)
Agent cross-check
2026-11-21
  • No configured product fixture was run; documentation does not establish successful hands-on behavior.
9 atomic answers
  • Units [supported] Agent usage is billed in credits and Orb compute by the minute. Sources: amp:gap07-pricing.
  • Included limits [supported] Megawatt includes $20 agent usage and 45,000 minutes of a1.small Orbs monthly. Sources: amp:gap07-pricing.
  • Overages [supported] Paid credits permit continued model and tool usage beyond the monthly allowance. Sources: amp:gap07-pricing.
  • Compute markup [supported] Self-hosted orbs are free on Hobby, Individual and Teams; Enterprise workspaces pay 100% of the standard orb price, billed per minute while the orb is connected to a thread, with volume discounts on request. Sources: amp:b152-sizes.
  • Model markup [supported] The guide states no provider API markup for individuals and non-enterprise workspaces. Sources: amp:nov07-pricing.
  • Minimum commitment [supported] Paid credits require no paid tier or commitment. Sources: amp:gap07-pricing.
  • Cancellation [supported] Cancel any time in user settings; the tier stays active to the end of the month. Sources: amp:b02-pricing.
  • Sales only unknowns [supported] Enterprise uses custom pricing. Sources: amp:nov07-pricing.
  • Transparency classification [supported] Partially specified: tier prices including Gigawatt $200, orb rates and no-markup credits are public; Enterprise is quote-only. Sources: amp:b02-pricing-docs, amp:b02-pricing, amp:b02-sizes, amp:b152-md-pricing.

Sources: amp:nov07-pricing, amp:gap07-pricing, amp:b02-pricing, amp:b02-pricing-docs, amp:b02-sizes, amp:b152-sizes, amp:b152-md-pricing

Sources

amp:nov07-intro

Introduction

Amp offers web, macOS, iOS, Android and CLI access to threads; Orbs keep working after closing the laptop.

Kind
documented
Locator
Quickstart; Explore
Source date
Not stated
Retrieved
2026-11-07
amp:gap35-linux

Amp linux

Amp has a native Linux desktop app with install instructions, desktop integration and a systemd-backed local runner. It supports tray operation and launch arguments; the Linux app lacks Mac Puck windows/dictation and multiple windows.

Kind
documented
Locator
Linux app installation, local runner, tray and differences from Mac
Source date
Not stated
Retrieved
2026-11-13
amp:nov12-chronicle

Amp Chronicle

Dated news: Boxes, persistent always-on machines (Nov 10); Portals on your runner (Nov 9); Spaces (Nov 6); GitLab integration for gitlab.com or self-hosted (Nov 5); Service Accounts for team-owned threads (Nov 3); Artifacts (Nov 2); macOS Satellites (Oct 29); self-hosted orb providers (Oct 28); Amp on Android (Oct 27).

Kind
vendor-claimed
Locator
News, Oct 27 – Nov 10, 2026
Source date
2026-11-10
Retrieved
2026-11-12
amp:b02-cli

CLI Getting Started

CLI on macOS, Linux and Windows via WSL; --executor local, orb or runner:<id>. ide connect links VS Code, Cursor, Windsurf, Zed and Neovim (Neovim needs the Amp plugin) for open-file context and IDE edits.

Kind
documented
Locator
Install; Manage CLI accounts; Choose Where the Thread Runs; Connect an Editor
Source date
Not stated
Retrieved
2026-11-21
amp:b02-help

Getting Help

Bug reports from CLI, apps or threads; help via X or amp-devs@ampcode.com. macOS app: Apple silicon, macOS 26+; iOS/iPadOS 26+ via public TestFlight beta; Android 13+ by APK, not Google Play; Windows 10 1809+ or 11; Linux Debian 12+, Ubuntu 22.04+, Fedora, Arch. The JetBrains integration is deprecated and gets no updates. Status at ampcodestatus.com with email, RSS and Slack alerts.

Kind
documented
Locator
Getting Help; Supported Platforms; Service Status
Source date
Not stated
Retrieved
2026-11-21
amp:b152-apps

Apps | Amp Docs

Amp runs as a native app on Mac, iPhone, iPad, Android phone or tablet, Windows and Linux; the apps give the same threads, orbs and Puck as ampcode.com and add notifications, dictation and sharing from other apps. Mac: Apple silicon, macOS 26+. iPhone/iPad: TestFlight beta, iOS or iPadOS 26+. Android: direct APK, Android 13+. Windows: Windows 10 1809+ or 11. Up to five accounts can stay signed in on one device. No page section calls the Windows app experimental.

Kind
documented
Locator
Overview; download buttons; Sign In and Account
Source date
Not stated
Retrieved
2026-11-21
amp:b152-help

Getting Help | Amp Docs

macOS app: Apple silicon, macOS 26+. iOS app: iOS or iPadOS 26+, public TestFlight link while in beta. Android app: Android 13+, direct APK, not Google Play. Windows app: Windows 10 1809+ or Windows 11. CLI: macOS, Linux and Windows via WSL.

Kind
documented
Locator
System requirements
Source date
Not stated
Retrieved
2026-11-21
amp:b152-windows

Amp for Windows | Amp Docs

Requires Windows 10 version 1809 or later, or Windows 11; runs natively on x64 and Arm. Everything on ampcode.com works in the app; threads run in orbs or on runners, and the app can run a runner per account. Notifications report a thread ready for input, mentions and access requests, with answer buttons. Share to Puck sends files or text. The page does not call the app experimental.

Kind
documented
Locator
Requirements; Install; Features (Threads and orbs, Run threads on this computer, Notifications, Share to Puck)
Source date
Not stated
Retrieved
2026-11-21
amp:b152-chronicle

Amp Chronicle

November 17, 2026: "Amp for Windows: Amp on your desktop, now on Windows." November 12, 2026: "Bye Bye, Dial" says Amp now has a model selector and the Dial is gone.

Kind
documented
Locator
November 17, 2026 "Amp for Windows"; November 12, 2026 "Bye Bye, Dial"
Source date
2026-11-17
Retrieved
2026-11-21
amp:nov07-models

Modes & models

Task and Read Thread subagents have separate context, report summaries and support follow-up work. They cannot communicate directly with one another.

Kind
documented
Locator
Subagents; Custom agents
Source date
Not stated
Retrieved
2026-11-07
amp:gap35-agent-architecture

Amp models and subagents

Amp uses its own agent across web, apps and CLI. The selected model is wrapped in Amp system prompts/tools; Task and Read Thread are Amp subagents. Custom plugin agents choose a model through amp.createAgent rather than selecting a third-party coding CLI harness.

Kind
documented
Locator
Introduction same agent everywhere; Models and Subagents main agent, custom agents and system models
Source date
Not stated
Retrieved
2026-11-13
amp:b02-threads

Threads

Threads have T-... URLs and open in web, CLI and all apps; they can run in an orb, on a runner or locally. Activity filters by time, status, author and project and searches with label: and other syntax. Messages sent while the agent works steer it; Cmd/Ctrl+Enter queues; Esc twice interrupts. Handoff starts a fresh thread with the relevant context; agents read threads by URL or @T- mention and search threads. Commits carry an Amp-Thread-ID trailer. Sharing is restricted, workspace or link; multiplayer contributors prompt, viewers read; admins open restricted threads through audited access. Export to Markdown, or full JSON for the creator. Labels, archive/unarchive, snooze, delete and per-thread cost are in the thread menu; snoozed threads awaiting approval reappear. Tagging a member turns on multiplayer. Artifacts are revisioned documents teammates and agents edit together.

Kind
documented
Locator
Threads; Where Threads Live; Start a Thread; Inside a Thread; Continue; Reference; Share; Export; Organize; Work Together; Artifacts
Source date
Not stated
Retrieved
2026-11-21
amp:b02-models

Models & Subagents

Task and Read Thread subagents run the thread model in their own context; Amp uses them automatically or on request. The main agent receives their final summary, cannot have them guided directly, and can give a Task subagent another task with its earlier context. System models analyze images, PDFs, audio and video. Finder returns relevant files and line ranges; librarian clones other repositories. Fable BYOK requires an Anthropic workspace with data retention enabled; zero-retention credentials cannot access Fable.

Kind
documented
Locator
Subagents; System Models; Custom Agents; Oracle, Librarian, Finder; Claude Fable with BYOK
Source date
Not stated
Retrieved
2026-11-21
amp:b02-model-selector

Model Selector (former Dial page)

The thread owner can change model and effort at any time; the transcript records the switch. Claude-plan requests run through Claude Code via the Claude Agent SDK on Amp servers. The Claude Code agent is selectable under Your Agents, runs Claude Code with Amp tools, needs a linked Claude subscription, and can be started from the CLI with --mode external-agent:claude-code.

Kind
documented
Locator
Switch Models in a Thread; Use Your Claude Subscription; Use the Claude Code Agent
Source date
Not stated
Retrieved
2026-11-21
amp:b152-model-selector

Model Selector | Amp Docs

Other Models lists every other model and agent; its first group, Your Agents, lists agents from plugins and Claude Code when a Claude subscription is linked. A thread that starts on one of these agents keeps it and cannot switch to another model; only the thread owner can switch models in other threads. Claude models served by a linked Claude plan run through Claude Code, which runs through the Claude Agent SDK on Amp's servers. The Claude Code agent runs Claude Code with Amp's tools, requires a linked Claude subscription and can be started from the selector or with --mode external-agent:claude-code in execute mode.

Kind
documented
Locator
Switch Models in a Thread; Your Agents; Use Your Claude Subscription; Use the Claude Code Agent
Source date
Not stated
Retrieved
2026-11-21
amp:nov07-pricing

Pricing

Hobby includes product features with separately billed hosted Orbs and inference routes. Teams have no additional charge; enterprise pricing is custom.

Kind
documented
Locator
Amp tiers; How usage is charged; Enterprise; Notes
Source date
Not stated
Retrieved
2026-11-07
amp:b02-intro

Amp introduction

Quickstart: sign up, optionally sign in with ChatGPT, create a project from a Git repository or start without one, run an agent in an orb, install apps, use the CLI. Amp states it kills features the team does not use and keeps no backward compatibility or legacy features.

Kind
documented
Locator
Introduction; Quickstart; Explore
Source date
Not stated
Retrieved
2026-11-21
amp:b02-pricing

Amp pricing page

Hobby has no monthly fee; own subscriptions or keys carry no Amp token fees on Hobby, Individual and Teams. A workspace costs nothing extra; some features such as SAML/OIDC SSO need at least one paid member. Cancel any time in user settings; the paid tier stays active to the end of the period. Enterprise lists audit logs, network/MCP access controls, IP allowlisting, regional endpoints, higher resource quotas and priority support. SOC 2 Type 2 is referenced.

Kind
documented
Locator
Tier cards; Questions & Answers
Source date
Not stated
Retrieved
2026-11-21
amp:b02-routing

Model Routing

Sign in with ChatGPT links each ChatGPT account to one Amp account (legacy connection for several). Copilot needs Copilot CLI enabled; *.ghe.com data-residency hosts are not supported yet. Gemini image generation requires an AI Studio key. One active connection per subscription type. Amp sends model requests from its own servers.

Kind
documented
Locator
Subscriptions; GitHub Copilot; Images
Source date
Not stated
Retrieved
2026-11-21
amp:b152-routing

Model Routing | Amp Docs

Sign in with ChatGPT also signs the user in to Amp, so each ChatGPT account can connect to only one Amp account. To use one ChatGPT account from several Amp accounts, add ChatGPT Subscription (Legacy) in personal Model Routing on each. Copilot needs Copilot CLI enabled; *.ghe.com data-residency hosts are not supported yet.

Kind
documented
Locator
Subscriptions (Sign in with ChatGPT; ChatGPT Subscription (Legacy)); GitHub Copilot
Source date
Not stated
Retrieved
2026-11-21
amp:nov07-github

GitHub & Git

A GitHub App authorizes selected repositories, branches and PRs; events can continue a thread or spawn a new Orb.

Kind
documented
Locator
Connection; PR status; GitHub webhooks
Source date
Not stated
Retrieved
2026-11-07
amp:b02-customizing

Customizing Orbs

Pre-clone and pre-setup scripts and .agents/setup prepare project snapshots per orb size; .agents/resume authenticates, repairs or reconnects after activation and each wake; .amp/services.yaml declares services. Repository Setup Failed links a Setup Log.

Kind
documented
Locator
Snapshots; .agents/setup; .agents/resume; Setup Log
Source date
Not stated
Retrieved
2026-11-21
amp:b02-runners

Runners

amp --no-tui starts a runner; orbs can route web traffic through a runner; runner portals are visible to workspace members it is shared with and cannot be public. Runners can create a Git worktree per thread, including for agent-started threads.

Kind
documented
Locator
Runner; Orb Network Routing; Portals on Your Runner; Create a Worktree
Source date
Not stated
Retrieved
2026-11-21
amp:b02-selfhosted

Self-Hosted Orbs

Self-hosted orbs are available on every plan: amp orb provider connects out to Amp and runs a user dispatch program for spawn, pause and delete jobs; a Helm chart covers GKE, EKS and AKS.

Kind
documented
Locator
Overview; Dispatch Program
Source date
Not stated
Retrieved
2026-11-21
amp:b02-execute

Execute Mode

amp -x runs one prompt and exits; -ox runs it in an orb and returns the thread URL; --executor runner:<id> starts runner threads. Non-interactive use sets AMP_API_KEY to an sgamp_ access token; a service account API key runs as the workspace.

Kind
documented
Locator
Execute Mode; Spawning Orbs; Spawning Runner Threads; Non-Interactive Environments
Source date
Not stated
Retrieved
2026-11-21
amp:b02-workspaces

Workspaces

Roles Member and Admin; Enterprise adds Billing Manager, Auditor, Group Manager. Service accounts need Enterprise or a Team workspace with bought credits; full-access keys run CLI or SDK threads. Usage Breakdown by category, model, mode, member, reasoning, speed, orb size and provider, switching spend, tokens and orb hours, with CSV export including a member summary.

Kind
documented
Locator
Roles; Workspace Settings; Service Accounts; Usage
Source date
Not stated
Retrieved
2026-11-21
amp:b02-spaces

Spaces

A Space chats with Amp, which starts parallel threads shown as live cards with status and attention. Threads nested under a moved thread move with it. Contributors chat, viewers read. Ownership transfers on acceptance. A progress chart counts shipped (commits on default branch, merged PR, or archived by Ship), archived and open threads.

Kind
documented
Locator
Create; Work in a Space; Sharing; Transfer; Track progress
Source date
Not stated
Retrieved
2026-11-21
amp:b02-automations

Automations & Webhooks

Schedules set in plain language run once or repeat until paused, deleted, ended or a completion condition is met; Amp wakes the agent and resumes the orb. Failed runs show the error; temporary delivery errors can keep a recurring schedule enabled; Amp may pause it. A run can unsnooze a thread. Plugin webhooks in orb threads store events, deliver at least once, retry with backoff to 5 minutes and drop after 1 hour.

Kind
documented
Locator
Automations; Manage; Run Quietly; Webhooks; Delivery Guarantees
Source date
Not stated
Retrieved
2026-11-21
amp:b02-github

GitHub & Git

Threads show commit, PR and CI previews. Issue/PR subscriptions receive comments, reviews, inline review comments and merge-queue events and continue the thread; spawners start an orb per new issue, PR or review request; CI subscriptions follow an exact commit's checks. No long-lived token in orbs; a credential helper fetches short-lived tokens.

Kind
documented
Locator
What Amp Uses the Connection For; Webhooks; Follow an Issue or PR; Orb Spawner; Follow CI; How Orbs Authenticate
Source date
Not stated
Retrieved
2026-11-21
amp:b02-projects

Projects

Project settings open for workspace admins and the project creator. Amp-hosted repositories offer a post-receive webhook.

Kind
documented
Locator
Project Settings; Webhooks
Source date
Not stated
Retrieved
2026-11-21
amp:b02-sdk

Amp SDK

TypeScript (@ampcode/sdk) and Python SDKs run the agent programmatically and continue threads by ID. For TypeScript, the Amp CLI must be at least the version pinned by the installed SDK release. @ampcode/sdk@0.1.0-20260528044221-ge0e19fa is the legacy release for users who need Amp from before Amp Neo.

Kind
documented
Locator
Install; Thread Continuity
Source date
Not stated
Retrieved
2026-11-21
amp:b02-security

Amp Security Reference

Vendor states SOC 2 Type II and annual pentests; reports by request through the Security Trust Portal. Lists GCP (US, threads, user data and telemetry), model providers, e2b orb compute and other subprocessors; TypeSafe Jev suggests next actions. Client and server do not store, clone or index the entire codebase. Deleted threads are removed within 30 days; Enterprise threads remain with the workspace when users leave. Paused orbs stay encrypted until thread deletion. Thread storage preserves prompts, responses, tool calls and results as an audit trail; a data management API exposes analytics and thread data. SCIM deprovisions; admin access to restricted threads needs passkey re-authentication. Training needs explicit opt-in, workspace admin approval, never on Enterprise. Secret redaction is best-effort. Amp offers no self-hosted deployment.

Kind
documented
Locator
Certifications; Infrastructure & Service Providers; Data Security; Thread Data; Orb Data; Prompt Injection Defenses; User Authentication; Audit Logging; Model Training; System Components; Client Security; Secret Redaction
Source date
Not stated
Retrieved
2026-11-21
amp:b02-chronicle

Amp Chronicle

Dated news: You've Got Comments (2026-10-12, follows up on GitHub PRs); Take Puck with You (2026-10-13, Puck usable in other agents via MCP); Assign It To Amp (2026-10-19, Linear); Bye Bye, Dial (2026-11-12, model selector replaces the Dial); Amp for Windows (2026-11-17).

Kind
documented
Locator
News entries 2026-10-12 to 2026-11-17
Source date
2026-11-17
Retrieved
2026-11-21
amp:b152-external-api

Amp External API Reference

Public External API v2 at https://ampcode.com/api/v2 for integrations with workspace data: threads (list, stream list changes, delete, metadata, messages, usage), workspace members, projects and repository search/contents, workspace groups, entitlements, workspace model-provider keys, daily usage analytics and the calling actor. Access uses machine-to-machine OAuth client-credentials apps that workspace admins create with scopes; Sign in with Amp apps are not generally available. An M2M token with threads:write can delete threads but not create them; Amp points product automation to the CLI or SDK.

Kind
documented
Locator
Amp External API v2 overview; Authentication; endpoint navigation (linked as "API" in the docs navigation)
Source date
Not stated
Retrieved
2026-11-21
amp:b152-puck-mcp

Puck | Amp Docs

Puck can be used from Claude, ChatGPT and other MCP clients, acting with the user's Amp account. Other MCP clients add https://ampcode.com/mcp as a remote MCP server; clients supporting Client ID Metadata Documents connect automatically, Amp does not support dynamic client registration, and other clients need a client ID. The server has three tools: puck, new_puck_conversation and orbs.

Kind
documented
Locator
Use Puck in Other Apps
Source date
Not stated
Retrieved
2026-11-21
amp:b152-docs-principles

Amp Docs overview

Under "On the Frontier", the docs say Amp goes where the models take it, with "No backward compatibility".

Kind
documented
Locator
Principles: On the Frontier
Source date
Not stated
Retrieved
2026-11-21
amp:nov07-multiplayer

Multiplayer

Workspace members can co-prompt an enabled thread and access its Orb or shared runner; access is time-limited and bills the owner.

Kind
documented
Locator
Activate multiplayer; Security; MCP servers
Source date
Not stated
Retrieved
2026-11-07
amp:nov07-mcp

MCP

Amp manages local and remote MCP definitions with OAuth or headers; no external-tool call was tested.

Kind
documented
Locator
Local and remote configuration
Source date
Not stated
Retrieved
2026-11-07
amp:b02-integrations

Integrations

First-party integrations: GitHub, GitLab, Google, Linear and Slack; other services via MCP. Assigning or mentioning Amp in Linear starts a Linear agent session and orb thread that replies in Linear; orbs read and update issues via the user's Linear connection; comments as Amp only on request. Slack posts ask first by default.

Kind
documented
Locator
GitHub; GitLab; Google; Linear; Slack; Other Services
Source date
Not stated
Retrieved
2026-11-21
amp:b02-plugins

Plugins

TypeScript or JavaScript plugins handle events, register tools, skills, commands and UI. tool.call runs before a tool and returns allow, reject-and-continue, modify or synthesize. Plugins define custom agent modes.

Kind
documented
Locator
Plugins; tool.call; Define a Custom Agent Mode
Source date
Not stated
Retrieved
2026-11-21
amp:b02-agentsmd

AGENTS.md

Repository, personal and workspace Global AGENTS.md; @-mentioned files with glob front matter; Amp can generate or update AGENTS.md on request.

Kind
documented
Locator
Global AGENTS.md; Writing AGENTS.md; globs
Source date
Not stated
Retrieved
2026-11-21
amp:b02-skills

Skills

Project skills in .agents/skills, personal and workspace skills repositories, plus Claude-compatible skill directories.

Kind
documented
Locator
Skills; Locations
Source date
Not stated
Retrieved
2026-11-21
amp:b02-apps

Amp Apps

Amp describes itself as a native app on Mac, iPhone, iPad, Android, Windows and Linux, with the same threads, orbs and Puck plus notifications, dictation and sharing. No UI framework is named.

Kind
documented
Locator
Amp Apps; Install
Source date
Not stated
Retrieved
2026-11-21
amp:b02-windows

Amp for Windows

App Installer installs the version for the computer, running natively on x64 and Arm. Notifications, taskbar unread count, and a tray icon with dots for running, unread, waiting and failed threads; built-in runner.

Kind
documented
Locator
Install; Features; System Tray
Source date
Not stated
Retrieved
2026-11-21
amp:b02-puck

Meet Puck

Puck starts and steers agents, finds and archives threads, splits work across agents and gathers reports, and sends saved prompts such as ship, review, update-base and custom prompts.

Kind
documented
Locator
What to Ask; Capabilities; Send Saved Prompts
Source date
Not stated
Retrieved
2026-11-21
amp:gap07-threads

Threads

Changes has per-commit diffs and navigation. Thread exports are Markdown or owner-only JSON. Artifacts are editable documents with revisions, conflict detection and Markdown/HTML/PDF export.

Kind
documented
Locator
Changes; Export a Thread; Artifacts
Source date
2026-11-06
Retrieved
2026-11-07
amp:nov12-spaces

Spaces

A Space has an optional Goal and Project, sharing and optional Slack channels. Amp starts a thread per request, shown as a card with live status and whether it needs attention. Existing threads can be added or moved with the threads they started; removed threads keep their history and environment. @Amp in a linked public Slack channel starts work. Teammates chat and comment; owners transfer ownership. A 30-day chart counts threads as Shipped, Archived or Open.

Kind
documented
Locator
Create a Space; threads; Slack; transfer; progress chart
Source date
Not stated
Retrieved
2026-11-12
amp:nov07-instructions

AGENTS.md

Repository, personal and managed guidance has documented inclusion scopes; workspace guidance excludes subagents, Puck and raw custom agents.

Kind
documented
Locator
Automatic inclusion; global guidance
Source date
Not stated
Retrieved
2026-11-07
amp:b02-files

Files & Attachments

Attachments stay private to the thread and protected by access checks; Amp inspects images, PDFs, audio and video.

Kind
documented
Locator
Attachments
Source date
Not stated
Retrieved
2026-11-21
amp:b02-a2a

Agent to Agent

Agents start other threads in orbs, projects or runners, send instructions and files, and bring results back into the current thread; fan-out threads can report results with screenshots when asked.

Kind
documented
Locator
Examples
Source date
Not stated
Retrieved
2026-11-21
amp:nov07-orbs

Orbs

Per-thread Orbs preserve files and services across idle pauses and queue starts beyond a documented burst allowance.

Kind
documented
Locator
Orb spawn pacing; review; follow along
Source date
Not stated
Retrieved
2026-11-07
amp:b02-orbs

Orbs overview

Each orb thread gets a fresh isolated cloud environment with code, plugins and tools; work continues with the laptop closed; several tasks can run at once. A sleeping orb costs nothing and wakes with conversation, files and services in place. Each user gets a burst of 20 metered orbs, then one new orb every five minutes; later starts wait with an estimated wait instead of failing; higher limits via support. The Terminal tab is a shared tmux shell on the same working copy. Apps show the same threads and notify when a thread is ready.

Kind
documented
Locator
Why Use an Orb; Orb Spawn Pacing; Terminal; Follow Along; Sync
Source date
Not stated
Retrieved
2026-11-21
amp:b02-entitlements

Workspace Entitlements

Enterprise per-user usage quotas such as $100/day or $50/week, assigned by default, individual, workspace group or SCIM directory group; Amp checks spend against the effective entitlement; BYOK counts at estimated list price; subscription inference does not count.

Kind
documented
Locator
Entitlements; Resolution and Usage Tracking
Source date
Not stated
Retrieved
2026-11-21
amp:b02-multiplayer

Multiplayer

Multiplayer works on orb and shared-runner threads for 7 days (5 minutes to 7 days via CLI); costs go to the thread owner. Contributors can access the orb or shared runner, secrets, files and terminal. Multiplayer on a runner ends when the owner stops sharing it. The agent refuses account changes in multiplayer threads and asks the owner or a workspace admin, not other teammates, to allow box and secret changes; Slack posts need the owner's approval.

Kind
documented
Locator
Activate; Changes to Your Amp Account; Integrations; Tagging
Source date
Not stated
Retrieved
2026-11-21
amp:nov07-automation

Automations & webhooks

A saved thread schedule wakes the same agent and Orb; one-off, recurring and completion-conditioned runs are documented.

Kind
documented
Locator
Automations; Manage an automation
Source date
Not stated
Retrieved
2026-11-07
amp:b02-sizes

Orb sizes and costs

Sizes a1.tiny to a1.3xlarge (1-16 CPUs, 2-44 GB, 60 GB disk) at $0.08-$2.13 per hour, billed per minute; a1.3xlarge only for Gigawatt and Enterprise. Self-hosted orbs are free on Hobby, Individual and Teams; Enterprise pays the standard price per minute. An orb pauses 5 minutes after agent work ends or 20 minutes after the last interaction, whichever is later; these are idle timeouts, not run limits. Archiving a thread pauses its orb immediately; left-running services pause with the orb and return when it wakes.

Kind
documented
Locator
Available Sizes; Billing; When an Orb Pauses
Source date
Not stated
Retrieved
2026-11-21
amp:b02-linux

Amp for Linux

Launcher unread count and a tray menu listing recent threads with a dot for running, unread, waiting or failed ones; built-in runner.

Kind
documented
Locator
Features; Tray and Open at Login
Source date
Not stated
Retrieved
2026-11-21
amp:nov07-orb-costs

Sizes & costs

Hosted sizes and hourly rates are published and billed by minute; idle pause stops charges. Enterprise self-hosted pricing changes after November 13.

Kind
documented
Locator
Available sizes; Billing; When an Orb pauses
Source date
Not stated
Retrieved
2026-11-07
amp:gap07-self-orbs

Self-Hosted Orbs

An outbound provider runs user-supplied spawn/pause/delete dispatch. Docker and Kubernetes examples retain disk but not memory. Self-hosted Orbs still connect to Amp.

Kind
documented
Locator
How It Works; Caution; infrastructure table
Source date
2026-11-03
Retrieved
2026-11-07
amp:b02-pricing-docs

Pricing (docs)

Hobby free; Individual Megawatt $20/month with 45,000 Amp-hosted orb minutes (Gigawatt price not rendered in the static page); Megawatt 50 $50/month with 2.5x included usage; Teams no extra charge, SAML/OIDC SSO, pooled credits; Enterprise custom, pooled credits only, no paid seats, spend limits, higher quotas. Included usage resets monthly. Paid credits are charged at actual model and tool usage without markup for individuals and non-enterprise workspaces; credits expire after 12 months. Thread cost detail is behind the $ price in each thread; Amp can explain token usage; invoices via Stripe accept VAT IDs.

Kind
documented
Locator
Amp Tiers; How Usage Is Charged; Enterprise; Notes
Source date
Not stated
Retrieved
2026-11-21
amp:gap07-runners

Runners

Runners serve local or remote directories. New Worktree creates a sibling checkout and branch; threads can archive and remove only clean worktrees.

Kind
documented
Locator
Start a Runner; Create a Worktree
Source date
2026-11-04
Retrieved
2026-11-07
amp:b02-secrets

Handling Secrets

Secrets are stored in settings and injected into orbs; OIDC gives orbs short-lived narrow credentials instead of fixed tokens.

Kind
documented
Locator
Secrets; OIDC
Source date
Not stated
Retrieved
2026-11-21
amp:gap07-customizing

Customizing Orbs

Project snapshots reuse dependencies up to 72 hours. Setup and resume scripts have distinct credentials and lifetimes. Services are declared separately; failed setup is visible in Setup Log.

Kind
documented
Locator
Orb Lifecycle; .agents/setup; .agents/resume; Services
Source date
2026-11-05
Retrieved
2026-11-07
amp:b02-portals

Portals & Desktop

Portals are authenticated URLs for orb web servers, viewable by people who can view the thread; a review widget sends element comments to the agent. Public access lasts 1 hour to 7 days and needs approval when the agent requests it. The Desktop tab runs a Linux desktop; a recorded run reports with screenshots.

Kind
documented
Locator
Portals; Review and Comment; Access and Lifecycle; Desktop
Source date
Not stated
Retrieved
2026-11-21
amp:b02-visibility

Workspace Thread Visibility Controls

Workspace-project threads are shared with the workspace by default, personal threads private; workspaces can disable outside sharing and default to private; Enterprise adds groups and per-group visibility.

Kind
documented
Locator
Options
Source date
Not stated
Retrieved
2026-11-21
amp:gap07-workspaces

Workspaces

Member uses shared resources; Admin also manages membership, billing, settings and policies and can inspect private threads. Enterprise adds narrower roles.

Kind
documented
Locator
Members; Personal vs. Workspace
Source date
2026-11-05
Retrieved
2026-11-07
amp:b02-shipping

Shipping Changes

Pressing Ship sends a prompt: commit, rebase, run the full test suite, push to the base branch; Ship Behavior can push a branch or use a custom prompt. Substantive conflicts are checked with the user. Archive appears after the work lands.

Kind
documented
Locator
Ship; Default Ship Flow
Source date
Not stated
Retrieved
2026-11-21
amp:b02-tools

Tools

By default Amp does not ask for approval before running tools; use a custom policy plugin, distributable as a workspace plugin.

Kind
documented
Locator
Tools; Permissions
Source date
Not stated
Retrieved
2026-11-21
amp:b02-settings

CLI Configuration

amp.tools.disable disables tools by name or glob; amp.mcpPermissions allows or rejects MCP servers by pattern, first match wins, default allow.

Kind
documented
Locator
amp.tools.disable; amp.mcpPermissions
Source date
Not stated
Retrieved
2026-11-21
amp:gap07-security

Amp Security Reference

Amp describes a cloud control plane without self-hosted deployments, GCP storage, separately controlled training, thread deletion, SOC 2 Type II and authentication audit logs.

Kind
documented
Locator
System Components; Data Security and Retention; Audit Logs; Assurance
Source date
Not stated
Retrieved
2026-11-07
amp:b02-ios

Amp for iPhone and iPad

The iOS app is a beta distributed by public TestFlight link; an App Store release will come later. It notifies when a thread is ready for the next message.

Kind
documented
Locator
Install; Notifications
Source date
Not stated
Retrieved
2026-11-21
amp:gap07-shipping

Shipping Changes

Default Ship commits, rebases, runs tests and pushes to the base branch. Push to Branch changes the destination; Custom Ship is a configurable prompt. Substantive conflicts require confirmation.

Kind
documented
Locator
Default Ship Flow; Ship Behavior; Restack Changes
Source date
2026-11-05
Retrieved
2026-11-07
amp:b02-boxes

Boxes

Always-on boxes from about $18/month; amp boxes deploy builds a release and serves it at the app URL such as https://<app>--<owner>.onamp.dev; service-account CI can redeploy.

Kind
documented
Locator
Boxes; Deploy an App
Source date
Not stated
Retrieved
2026-11-21
amp:gap07-terms

Amp License Terms

Amp grants a revocable, nontransferable service license and reserves proprietary rights. This is a custom service license, not an open-source license.

Kind
documented
Locator
License; Intellectual Property
Source date
Not stated
Retrieved
2026-11-07
amp:gap07-pricing

Amp Pricing

Hobby is recurring free with no included usage. BYO subscriptions/keys incur no Amp fees outside Enterprise. Megawatt costs $20/month with $20 usage and 750 a1.small Orb hours; compute and credits remain separate.

Kind
documented
Locator
Amp Tiers; How Usage Is Charged
Source date
2026-09-14
Retrieved
2026-11-07
amp:gap35-pricing

Amp pricing

The complete public tier table lists Hobby free, Megawatt $20/month, Gigawatt $200/month, Teams at no additional charge and custom Enterprise. Usage and Orbs are separately metered. Members keep individual tiers; the public table has no separate per-seat workspace fee or one-time license.

Kind
documented
Locator
Amp Tiers table; How Usage Is Charged; Enterprise. Page lastModified 2026-11-11.
Source date
Not stated
Retrieved
2026-11-13
amp:b152-md-pricing

Pricing (Markdown) | Amp Docs

Hobby free with nothing included. Megawatt $20/month ($10 with the education discount) includes $20 of agent usage and 750 hours (45,000 minutes) of a1.small orbs. Gigawatt $200/month includes $200 of agent usage and 1,000 hours of a1.xxlarge orbs. Teams add no extra charge; each member keeps their own tier and purchased credits are pooled. Enterprise is custom. Megawatt 50 ($50/month, 2.5 times Megawatt's included usage) is offered after sign-in. Included usage resets monthly without rollover; extra credits are billed at list price with no markup for individuals and non-enterprise workspaces. The interactive pricing page shows Gigawatt only behind a toggled tab, so its static HTML lacks this row.

Kind
documented
Locator
Amp Tiers table; Megawatt 50 note; How Usage Is Charged (lastModified 2026-11-17)
Source date
2026-11-17
Retrieved
2026-11-21
amp:b152-workspaces-billing

Workspaces | Amp Docs

Team workspace admins can change a member's tier and set an optional base tier of Megawatt or Gigawatt for all members; service accounts never get a base tier seat and do not count toward its price. A Team workspace pays for its members' usage and paid tiers by default (Pay for Members); admins can turn this off so members pay for themselves, which removes the base tier. Enterprise workspaces always pay for their members.

Kind
documented
Locator
Member tiers; Pay for Members
Source date
Not stated
Retrieved
2026-11-21
amp:b152-sizes

Orb Sizes and Costs | Amp Docs

Self-hosted orbs are free on the Hobby, Individual and Teams plans. Enterprise workspaces pay 100% of the standard price for them, billed by the minute while the orb is connected to a thread; volume discounts are available from the Amp team. a1.3xlarge is only for Gigawatt subscribers and Enterprise members.

Kind
documented
Locator
Self-Hosted pricing paragraph
Source date
Not stated
Retrieved
2026-11-21

Comparisons with Amp

Compare Amp with any other product on adecomparison.com.