Skip to main content
Integrations connect Runtime to the systems where work arrives and results go: a Slack mention or a Linear assignment launches a run, and GitHub gives it a repo to clone and push to. They are configured by org admins under Settings > Integrations and hold their own credentials (an app installation or a bot token). What an agent can reach while it works is a separate concept: see Tools and connections.

GitHub App

Clone repositories, push commits, create pull requests, and manage branches from inside sessions.

GitHub User Tokens

Per-user GitHub credentials that let sessions act as the individual developer for git operations.

Linear

Trigger agent sessions from Linear issues. The agent picks up the ticket, writes code, and reports back.

Slack

Trigger agent sessions from Slack messages. Users mention the bot, and it spins up a session to handle the request.
Email, WhatsApp, SMS, schedules and webhooks also start runs. They are configured per agent rather than per org; see Triggers.

​
GitHub App

The GitHub App integration connects your GitHub repositories to Runtime. Once installed:
  • Clone repos into sessions with POST /api/sessions/{id}/git/clone
  • Push changes back to GitHub with POST /api/sessions/{id}/git/operation
  • Create branches and PRs directly from the session
  • Access tokens are managed automatically; you never handle raw GitHub tokens
The integration works through a GitHub App installed on your GitHub organization. Runtime caches and auto-refreshes installation tokens.

​
Setup

  1. Install the Runtime GitHub App on your GitHub org
  2. Select which repositories it can access
  3. The integration appears in Runtime’s installations list
See the GitHub App API reference for all endpoints.

​
User tokens

In addition to the org-level App, individual users can link their GitHub identity. This lets sessions attribute commits to the right person and access repositories the App does not cover. See GitHub User Tokens.

​
Linear

The Linear integration lets agents respond to issues automatically:
  1. A team member creates a Linear issue (or tags the Runtime bot on one)
  2. Runtime spins up a session, clones the relevant repo, and sends the issue description as a prompt
  3. The agent writes code, creates a PR, and updates the issue with progress
Admins configure which Linear workspace to connect and set rate limits on how many agent sessions can be launched per hour. See the Linear API reference.

​
Slack

Similar to Linear, the Slack integration listens for messages in channels:
  1. A user mentions the Runtime bot in Slack
  2. Runtime creates a session and sends the message as a prompt
  3. The agent works on the task and can report back to the Slack thread
Two connection methods are available:
  • Managed app - use Runtime’s hosted Slack app (OAuth install)
  • Self-hosted app - bring your own Slack app with a custom bot token and signing secret
See the Slack API reference.

​
Permissions

Integration endpoints require the integrations:read or integrations:write scope. Org admins and owners set up integrations; members can read their status.

Triggers

How Slack, Linear, GitHub, email, schedules and webhooks start an agent.

Webhooks and triggers

Outbound webhook events and built-in trigger patterns.