Integrations Overview

Warp integrations let your team trigger agents directly from the terminal, or from tools like Slack, Linear, Jira, and GitHub. Once set up, agents can:

• Read conversation or issue context
• Run code inside your codebase in a remote environment
• Open pull requests and perform other multi-step agent workflows on your behalf

If you’re deciding whether an agent should run from a schedule, Slack, Linear, GitHub, GitHub Actions, the Oz CLI, or the API, see Run agents unattended with schedules and triggers.

Note

Warp has two distinct GitHub surfaces. The GitHub integration starts agents when someone mentions @oz-agent on an issue, pull request, or review comment, using the Oz by Warp GitHub App. GitHub Actions runs agents inside workflows you define in your own CI pipeline.

Note

For a full walkthrough of Warp’s integrations and configurable environments, please refer to Integration setup.

All of this is powered by the Oz CLI.

---

Get started

Use the setup walkthrough below for a quick look at how environments connect to integrations, then choose the guide that matches what you want to do next.

• Integrations quickstart - Trigger your first agent from Slack and watch the run from start to finish.
• Integration setup - Configure environments, GitHub authorization, CLI flags, and integrations in more detail.
• Slack, Linear, and Jira - Trigger agents from team conversations, issues, and comments.
• GitHub - Mention @oz-agent on issues, pull requests, and review comments to start agents that reply in the thread.
• GitHub Actions - Run agents from CI workflows and repository events.
• GitLab, Bitbucket, and Azure DevOps - Connect non-GitHub repositories with tokens and Warp-managed secrets.
• AWS, GCP, and other cloud providers - Give cloud agents short-lived access to cloud services.
• Managing cloud agents - Monitor and review integration-triggered runs across your team by source, status, or creator.