Integrations

Integrations connect Amp to the services where your team tracks and reviews work. Each person connects their own account under Settings → Integrations & MCP, so Amp acts with that person’s access. Workspace admins install shared apps and turn integrations on or off under Workspace Settings → Integrations & MCP.

GitHub

The GitHub integration lets orbs clone private repositories, push branches, and open pull requests as you. GitHub webhooks can also continue a thread when an issue, pull request, or CI run changes, or start a new orb for each new issue or pull request. See GitHub & Git for the full guide:

Linear

The Linear integration works from both sides. In Linear, people assign issues to Amp or mention @Amp, and Amp works on the issue in an orb and replies in Linear. In Amp, orbs read and update issues through your own Linear connection, and subscriptions can start an orb for each new issue.

Set Up Linear

  1. Install Amp in Linear. A workspace admin clicks Install Amp in Linear on the Linear card under Workspace Settings → Integrations & MCP. A Linear admin must approve the Amp app. Each Linear workspace belongs to one Amp workspace, and the members of that Amp workspace can use it.
  2. Connect Linear. Each person who wants to use Amp from Linear clicks Connect Linear on the Linear card in Settings → Integrations & MCP. This signs you in with Linear and adds Linear to your MCP servers. Amp uses it to recognize you in Linear, and orbs use it to read and update issues as you.

If Install Amp in Linear offers Personal, it connects a Linear workspace that has only you in it to your own Amp account. Sessions and subscriptions in that Linear workspace then run only as you and only in your own projects.

For a private Linear team, a Linear admin must also give the Amp app access to the team. When an installation shows Permissions Update Required, a workspace admin clicks Update Permissions and a Linear admin approves the new permissions. Use Manage in Linear or Uninstall in the installation’s … menu to change or remove the app. Uninstalling stops Linear events and subscriptions, but members keep their own Linear connections.

Assign or Mention Amp

Assign or delegate an issue to Amp, or mention @Amp in a comment. Amp starts a Linear agent session and an orb thread that runs as you. The session links to the thread with Open in Amp and shows Amp’s progress and final reply. It also tells you when Amp stops with an error or waits for you to approve a tool.

  • Reply in the session to send Amp a follow-up. Only the person who started the session can send follow-ups. Anyone else can mention @Amp in a new comment to start their own session.
  • Anyone who can see the session can stop it. Amp interrupts its thread and confirms in Linear.
  • To start a session, you must belong to the Amp workspace that installed Amp in Linear and have connected Linear in Amp with the same Linear account. Amp tells you in Linear when either is missing.

Choose Where Sessions Start

A Linear issue does not name a repository, so Amp picks the project for the session’s orb. It uses the first of these that applies:

  1. A route for the issue’s Linear project.
  2. A route for the issue’s Linear team.
  3. The repository of the GitHub or GitLab pull requests, issues, or commits linked to the issue, when they all match one Amp project.
  4. Linear’s suggested repository, when Linear is confident and the repository matches one Amp project.
  5. The installation’s Default Project.
  6. No project. The orb starts without a repository.

Workspace admins manage this under Agent Routing, below each installation on the Linear card in Workspace Settings → Integrations & MCP. Choose a Default Project, or click Add Route to send a Linear team or project to an Amp project. A Linear project route applies before a team route. Other members see the default project and how many routes exist. Admins can also ask Puck to list or change routes.

Routes and the default project always win. If the chosen project is not available to the person who started the session, the session stops with an error in Linear instead of guessing another repository. Agent Routing applies only to sessions; subscriptions choose their own project.

Comments as Amp

Ask Amp in any thread to comment on a Linear issue, and it posts the comment as Amp through the installed app, not as you. Use this for automated reports that should not look like they came from a person. Amp posts these comments only when you or saved instructions ask for one. Agent sessions reply inside the session rather than as separate comments.

This works when your Amp workspace installed Amp in the Linear workspace and the app can see the issue. It does not need your Linear connection. To comment as yourself, ask Amp to use your Linear tools instead.

Use Linear Tools as Yourself

Connect Linear adds Linear’s MCP server to your account. Every thread can then search, read, create, and update issues and post comments as you, with your Linear permissions. This works whether or not anyone installed Amp in Linear. Subscriptions also use your connection to read issues, so keep it connected.

Start an Orb for Each New Issue

A subscription starts a new orb for each issue created in a Linear team. Use it for triage: find the code that owns the issue, classify it, try to reproduce it, or suggest labels and an assignee. Ask Amp or Puck to create one, and name the Linear team, the Amp project, the agent mode, and what each orb should do:

For each new issue in the ENG Linear team labeled triage, start an orb in our Widget project using Medium mode. Find the code that owns the issue, say whether it is a bug or a feature request, and try to reproduce bugs.
  • Label filter. You can limit a subscription to issues created with one label. The name must match exactly, ignoring case. Adding the label to an issue later does not start an orb. Use a label when you can, because anyone who can create issues in the team can otherwise start orbs that run as you.
  • One-shot by default. Each orb handles its issue once and does not write back to Linear. To report back, say so in the instructions, for example “comment on the issue with your findings”, and Amp comments as Amp.
  • Follow-up comments. Ask Amp to keep following each issue, and later comments on the issue go to the same orb. Comments that mention @Amp start an agent session instead.
  • Project. Each subscription names its own Amp project: a workspace project or one of your personal projects. Agent Routing does not apply.
  • Who can use it. Any member of the Amp workspace that installed Amp in Linear can create a subscription after connecting Linear, for a team they can see in Linear. Orbs run as the person who created the subscription, and only that person can manage it. Issues that Amp creates do not start orbs.

The Linear card in Settings → Integrations & MCP lists your subscriptions under Event Subscriptions. Expand one to see its instructions, whether it follows comments, and the orbs it started. Use the row’s … menu to Pause or Resume it, and ask Amp or Puck to delete it. You can give a subscription an expiration time when you create it. If a subscription stops working, its status explains why, for example when your Linear connection needs to be reconnected.

Slack

Mention @Amp in Slack to ask a question, start work, or check on a thread. See Slack Integration.

Other Services

Connect any other service that has an MCP server, such as Sentry or Notion. See MCP.