Meet Puck

Puck is your personal Amp assistant that helps you manage everything you do in Amp: start agents, monitor them, send messages to them, create projects, and so on. Puck also comes in many looks; see them all at What the Puck?.

Open Puck

On ampcode.com, press Ctrl+/ from any page to open or close Puck. Puck appears over your current page, so it can use the thread or project you are viewing as context.

In the TUI, press Ctrl+O to open the command palette and select puck: open. You can also press Ctrl+X, then P.

In the iOS or Android app, open the sidebar and press Puck. You can also share an image to Amp from any app’s share sheet, and it goes to Puck.

In the macOS app, Ctrl+/ opens Puck in a window of its own, so you can keep the chat beside your work or on another display. Press it again to put that window away. Puck still uses the page your main Amp window is showing as context, so you can say “this thread” or “this project” while the Puck window is in front. Opening a thread or any other page from Puck opens it in its own window rather than replacing the chat.

Both apps add two shortcuts to the Shortcuts app: Dictate to Puck opens Puck and starts dictation, and Call Puck opens Puck and starts a call with it (on iPhone, as a phone call).

Conversations

You can keep several separate conversations with Puck. Each conversation has its own history.

  • Press + (New Chat) in the Puck header to start a new conversation.
  • Click the conversation title in the Puck header to switch to another conversation. Conversations with unread replies are marked. Conversations started from the Slack Integration are not listed here; open them from the Puck link on a Slack reply or find them with thread search.
  • Conversations you have not used in the last 72 hours move into the Inactive Last 72h group at the bottom of the list.
  • To put a conversation away, open the More Actions menu (⋯) and choose Archive Conversation.

What to Ask

Puck can handle quick requests itself or start agents to do larger pieces of work. For example:

Start an agent in ampcode/amp to investigate why CI is failing.
Find the thread where I investigated that server error.
Once this thread is done, archive it.
Create a project and start setting up its development environment.
Start one agent for each script in this repository, then summarize what they found.

Puck can keep track of the agents it starts, send them more instructions, and bring their results back to you.

Capabilities

Puck helps you start, find, and coordinate work across Amp.

Start and Steer Agents

Ask Puck to start an agent in a project. You can give the agent a coding task, ask it to investigate a problem, or send more instructions as the work continues.

Find and Manage Threads

Puck can find previous conversations, check active threads, archive completed work, and help you return to an investigation.

Thread search supports puck:true, which matches conversations with Puck itself. It does not match threads created by Puck. For example, use author:me archived:true puck:true to find your archived conversations with Puck.

Send Saved Prompts

Puck can send a thread a prompt by name instead of writing it out. Ask Puck to ship a thread and it sends the ship prompt: the same text as that thread’s Ship button. Amp also has built-in update-base, refactor-commits, and review prompts. You can edit any built-in on the Prompts page; the Changes pane buttons then send your text too.

To add your own, open Personal Settings or Workspace Settings, open Prompts, and choose New Prompt. Give it a name, such as release-notes, and the text. Then ask Puck to “send release-notes to that thread.” In any thread, you can also ask the agent to use a prompt itself, for example “ship it” or “use release-notes”. Your personal prompts take precedence over workspace prompts with the same name. Only workspace admins can change workspace prompts.

Prompts can also be buttons in a thread’s Changes tab. Check Show as a button in the Changes tab on your own prompt to add it, or turn off the switch next to a built-in to hide its button. The Ship button always shows.

Work With Projects

Puck can find your existing projects, create a project, and start an agent with the right repository and environment.

Coordinate Parallel Work

Puck can split a request across several agents and gather their reports. This is useful when pieces of work can run independently.

Use Skills

Puck loads your personal and workspace skills, so you can ask it to follow one directly. A skill you publish reaches Puck within about a minute, even in a conversation that is already open. Puck has no orb, so it can read a skill’s instructions and files but cannot run its scripts. Plugins do not load in Puck. To create or change a skill, or to use one that runs scripts or plugins, ask Puck to start an agent.

Use Connected Services

Puck can use connected services when they are available. For example, it can inspect GitHub checks or search Slack for context. You can also talk to Puck directly from Slack through the Slack Integration.

Call Puck

To talk with Puck out loud, call it: press Call Puck next to the Puck composer, or press Ctrl+Shift+/ from any page. Puck answers aloud, and the full text of each answer appears in the chat. Press End Call to hang up.

Use Puck in Other Apps

You can talk to the same Puck from Claude, ChatGPT, and other MCP clients. Puck acts with your Amp account there too: it can find your threads, start and steer agents, and use your connected services. Messages go to your latest Puck conversation, so you can continue them in Amp.

Open Settings > Puck and find Puck in Other Apps:

  • Claude: Click Add to Claude. Claude opens its Add custom connector dialog with the name and URL filled in. Confirm, then sign in with your Amp account. On Claude Team and Enterprise plans, only an organization Owner can add custom connectors.
  • ChatGPT: Turn on developer mode in ChatGPT, click Copy URL, and add the URL on ChatGPT’s Plugins page. Then sign in with your Amp account.
  • Other MCP clients: Add https://ampcode.com/mcp as a remote MCP server. Clients that support Client ID Metadata Documents (CIMD) connect automatically. Amp does not support dynamic client registration. Other clients need the client ID under Advanced, and it works only with one of the redirect URIs listed there. Sign-in fails with any other redirect URI. When Amp allows no redirect URIs, Advanced does not appear and only CIMD clients can connect.

The server has two tools: puck sends a message to Puck and returns its reply, and orbs shows your running orbs with links to their portals.

Workspace admins can turn off Puck MCP for all workspace members in Workspace Settings > Integrations & MCP. If your workspace uses its own domain, Settings shows the server URL on that domain. If the domain allows only certain networks, apps that connect from their own servers, such as Claude and ChatGPT, cannot reach it.

Slack Integration

Slack is one way to talk to your personal Puck. Connect the integration, then mention @Amp in a channel or thread. See Slack Integration for setup and examples.