GitHub introduces agent apps that bring third-party tools like Amplitude, Endor Labs, LaunchDarkly, and PagerDuty directly into the GitHub workflow via the Agents tab or pull request comments. A walkthrough shows how a developer can validate a feature idea with Amplitude, check dependency risk with Endor Labs, set up a feature flag rollout with LaunchDarkly, and assess deployment risk with PagerDuty, all without leaving GitHub. Additional launch partners include Packfiles, Miro, Bright Security, SonarQube, and Octopus Deploy, available now on the GitHub Marketplace.
Table of contents
1. Before you build it2. As you build it3. Rolling it out4. Before you shipWhat changesTry itTags:Written byQuestions this post answers
What are GitHub agent apps and which tools can I use them with?
GitHub agent apps let developers bring third-party tools directly into GitHub's Agents tab or pull request comments, powered by the same platform and harness as Copilot cloud agent. Inaugural agent apps include Amplitude, Endor Labs, LaunchDarkly, PagerDuty, Packfiles, Miro, Bright Security, SonarQube, and Octopus Deploy, available from the GitHub Marketplace. daily.dev surfaces new GitHub Copilot ecosystem releases for developers evaluating agent-based workflow tools.
How can I check dependency risk in a pull request without leaving GitHub?
The Endor Labs agent app can be mentioned directly in a pull request comment to identify changed dependencies and check them for known vulnerabilities and broader package risk, reporting results back in the pull request thread. This replaces waiting for a CI scan to fail and remediating afterward, making dependency review a proactive step during code review. Developers tightening dependency review workflows track tooling like this via daily.dev.
How do I set up a feature flag rollout using LaunchDarkly directly from a GitHub pull request?
The LaunchDarkly agent app can be mentioned in a pull request comment with flag parameters (key, type, default, target, rollout percentages) to create the flag in LaunchDarkly and commit the code implementation for review. If the target environment requires approval, it creates an approval request instead of applying targeting changes directly, keeping a human in the rollout decision. Engineers coordinating feature flag rollouts follow workflow integrations like this on daily.dev.