Integrations
How Slack, GitHub, Linear, and inbound automations start and continue OpenInspect sessions, and the rules they all share.
OpenInspect sessions can be started from Slack, from a GitHub pull request, from a Linear issue, or by an automation, and every one of them is the same kind of session you would start from the web app.
You can also work with OpenInspect from your own tools. The MCP server lets an MCP client such as Claude Code read your sessions and automation runs, and optionally create and run automations, with a personal access token.

The Code Server and VNC Desktop entries on the same list are not chat integrations: they turn on the in-browser editor and remote desktop inside sessions. See Sandbox tools for using them and Sandbox settings for their ports and scopes.
Choose an entry point
| Integration | Start work | Continue | Where results appear | Authorization |
|---|---|---|---|---|
| Slack | @mention the bot in a channel, or send it a DM | Authorized follow-ups in the same Slack thread (mapping lasts about 7 days) | Completion in the thread when publication is allowed; full output in the web session | Installation access plus channel bindings, scoped catalogs, team membership and grants for team-owned launches |
| GitHub | Open a non-draft PR (deprecated workspace auto-review), or @mention in a PR comment or review thread | Mentions create new sessions; PR Feedback Autofix can resume the session that created a PR | Reviews, comments, and thread replies written by the agent | Installation, Repository Scope, Allowed Trigger Users, and routed-team creation checks |
| Linear | @mention or assign the Linear Agent on an issue | Authorized follow-ups through the same active Linear Agent session | Activities and links, subject to completion delivery checks | Source-control access, Repository Scope, Linear team bindings, and OpenInspect membership and grants for team launches |
| Inbound webhooks and automations | A schedule, an inbound webhook, a GitHub event, a matching Slack channel message, or a Sentry alert fires an automation | Slack message automations continue in the triggering thread for 7 days; other triggers start a run per event | The session in the web app; Slack message automations also post into the triggering thread | The automation's own conditions (for example a Slack User allowlist) and the same repository boundary as everything else |
There are no slash commands in Slack or GitHub, and there is no browser extension. Slack requests in channels need an @mention, and GitHub requests need the bot's full username including [bot].
Rules every integration shares
Slack channels and Linear teams can be bound to an OpenInspect team; GitHub mentions use linked-PR ownership or sender membership routing. GitHub event automations keep their saved owning team. These ownership rules do not grant access to existing sessions. TEAMS_ENFORCEMENT remains shadow by default, not on, so do not assume full team-read isolation. See each integration's guide for its enforced creation and publication checks.
| Rule | What it means | What to do |
|---|---|---|
| Installation scope is the outer boundary | The source-control installation limits available repositories. Team repository grants and scoped catalogs further constrain team-owned work; these are not per-user GitHub repository lists. | Install the App only on intended repositories and configure team grants. GitHub and Linear Repository Scope settings add integration-level filters. |
| Trigger gates do not grant team membership | GitHub checks repository permission or an explicit user list. Slack channel membership and Linear workspace access alone do not grant OpenInspect team membership. Team-owned session creation checks the acting identity and target grants as well as workspace permissions. | Manage trigger settings, team membership, grants, and workspace access separately. |
| Bots act only for admitted people | Slack and Linear link a new person to an account by their profile email and create one only if that email passes the workspace's sign-in rules; without a readable email they cannot use the bot. The GitHub bot acts only for people the workspace already knows, typically from a web sign-in with GitHub, unless unsafe allow-all is in effect. | Sign in on the web with your bot profile's email, or ask an administrator; see Workspace access. |
| External text is marked untrusted | The text that invokes the bot is the request and the agent acts on it: the Slack message or forwarded message, the GitHub comment that mentions the bot, or the Linear issue. Surrounding context, such as earlier thread messages and PR titles and descriptions, is passed as background and wrapped as untrusted input. See Security. | Do not put secrets in issues, comments, or Slack messages: their text reaches the agent. |
| The web session is the source of truth | Slack, GitHub, and Linear show acknowledgements, short completion summaries, and links. Live output, tool calls, file changes, artifacts, and the option to take over live in the session page. | Open the session in the web app to follow progress or step in. |
| Harness depends on the entry point | Slack, GitHub, and Linear sessions run on the harness chosen in their integration settings, OpenCode by default; Slack users can also pick their own in App Home. All three preserve that harness: if it cannot run the resolved model, the bot replies with an explanation and creates no session. Automations run on the harness chosen on the automation. | Choose a compatible model or change the integration harness under Settings › Integrations. For other triggers, use an automation. |
Guides
Slack
Start from a channel or DM, pick a target, continue in the thread, and let agents post updates.
GitHub
Automatic PR reviews, @mention actions, PR Feedback Autofix, and the GitHub bot settings.
Linear
Mention or assign the Linear Agent on an issue and follow progress from Linear.
Inbound webhooks
Start sessions from any system that can send an HTTP request.
Personal access tokens
Issue tokens that let your own tools call the API as you, limited to the permissions you grant.
MCP server
Let Claude Code or another MCP client read sessions and automation runs, and optionally create and run automations.
Next steps
Automation templates
Start an automation from a pre-filled template in the Templates gallery, then adjust the repository, model, and instructions before saving.
Slack
Start OpenInspect sessions from Slack channels and DMs, continue them in threads, set personal defaults in App Home, and let agents post updates.