Runner.Search issues and PRs across repositories without leaving the workflow.
GitHub Runner Workflows
Track issues, review PRs, and keep development context connected to the rest of your workflow.
Runner connects to GitHub through the Composio toolkit for repository management, issue tracking, pull request review, and code search across your organization.
GitHubDevelopment
+New Session
Sessions
Connected appsGitHub
Linear
Slack
Sentry
GitHubLinearSlackSentry+
Connect a new appWhat would you like to do?
What Runner actually does with GitHub
This page is tied to the real connector definition inside Runner. The highlights below describe the kinds of actions, safeguards, and workflow patterns the app page represents, not a generic integration directory blurb.
Pull code context and review comments into meeting prep and stakeholder updates.
Track development progress alongside CRM, email, and calendar actions.
Backend surface
Composio toolkit powers this connector inside Runner. Backed by the `github` toolkit in Runner's backend catalog with repository, issue, and PR operations.
Operational notes
- GitHub API rate limits apply — Runner scopes queries to avoid exhausting the hourly budget.
- PR review comments and CI check results are available as part of the PR context.
Popular workflows with GitHub
Real workflow pages where GitHub is part of the connected stack. Each workflow shows the trigger, connectors, and outcome.
Triggers and actions
What Runner can do with GitHub. These are grounded in the real backend connector definitions, not generic marketing filler.
Search issues across the org
“Find open issues labeled 'critical' in the main product repo.”
Runner surfaces the issues that matter without manually scanning the backlog.
Pull PR context before the standup
“Show me the open PRs from this sprint and their review status.”
Development progress becomes part of the operating context before the meeting starts.
Link code changes to the business update
“Include the recent release notes and key merged PRs in the weekly stakeholder update.”
Technical progress gets translated into business context without manual lookup.
Create an issue from the conversation
“File a GitHub issue for the auth bug that came up in the customer call, with the relevant details.”
Bugs and feature requests become tracked issues without leaving the workflow.
Check CI status before the release
“Are all checks passing on the release branch?”
Release readiness becomes part of the operating context for ship decisions.
Use GitHub inside a real workflow
Download Runner to connect GitHub to the rest of your workflow instead of treating it like another isolated tab.