---
title: "Integrations"
description: "Connect coding-agent work to GitHub, Slack, Linear, Sentry, Sazabi, Axiom, and external tools."
canonical_url: "https://hoplite.sh/docs/integrations"
markdown_url: "https://hoplite.sh/docs/integrations.md"
---

# Integrations
URL: /docs/integrations
LLM index: /llms.txt
Description: Connect coding-agent work to GitHub, Slack, Linear, Sentry, Sazabi, Axiom, and external tools.
Related: /docs/integrations/slack, /docs/integrations/linear, /docs/integrations/sazabi, /docs/agent/mcp, /docs/github

# Integrations

Bring Hoplite into the tools your team uses to plan, discuss, and review work. Integrations connect repository access, incoming tasks, and external tools to your agents.

Integration settings live under **Settings → Integrations**, grouped into personal, selected-project, and workspace sections. Connect the provider at the scope it needs, then use a project binding when the provider must route events into one particular project. Slack's workspace installation authorizes the bot across every project in the Hoplite workspace, while Linear bindings route its events into a project.

## Available integrations

| Integration | What it unlocks |
| --- | --- |
| **[GitHub](/docs/github)** | The foundation: the GitHub App is installed at the workspace level and repos bind to projects |
| **[Slack](/docs/integrations/slack)** | Connect your Slack workspace and optionally route channels to projects, so threads start and stream where your team talks |
| **[Linear](/docs/integrations/linear)** | Route Linear mentions and delegated issues into a project, with progress flowing back to the issue |
| **Sentry** | Bind one or more Sentry projects so agents can inspect redacted issues, events, releases, alerts, teams, and members; issue comments and resolution are separately capability-gated |
| **[Sazabi](/docs/integrations/sazabi)** | Start automations when Sazabi triggers or resolves an issue, and let agents investigate issues, query logs, and read investigations; issue changes require administrator enablement and the run's approval policy |
| **Axiom** | Investigate logs, OpenTelemetry traces, and metrics with a workspace connection; repository-backed threads can request approved writes when enabled |
| **Bronto** | Agent access is suspended; saved connections remain manageable in organization settings |
| **Phone / iMessage** | Connect your personal Messages account to check agents, relay instructions, and start threads by text |
| **[MCP servers](/docs/agent/mcp)** | Extend the agent's tool catalog with Model Context Protocol servers |

## Axiom and Bronto

Workspace owners and admins connect these providers under **Settings → Integrations**. For Axiom, supply the organization ID and a dedicated API token with the minimum required permissions. Set hourly and daily query-cost limits on the token in Axiom before connecting; Hoplite respects Axiom's budget refusals. For Bronto, choose the EU or US region matching your organization and supply a dedicated regional API key with a least-privilege role. Credentials are encrypted at rest.

Axiom connections start read-only. Enabling writes does not grant blanket permission: the upstream credential and Hoplite's resource policy must authorize each mutation. Cloud runs auto-approve tool calls without a separate prompt; local CLI and desktop runs retain their approval flow. Axiom writes are available only in repository-backed threads; general threads stay read-only and subagents do not inherit Axiom. Disconnecting, replacing credentials, or disabling writes is enforced on subsequent tool calls, including in running threads.

Agents use `axiom_control` for operation discovery and bounded queries with explicit time ranges. Bronto agent access is disabled for both parent runs and subagents, regardless of the write setting. Connecting a Bronto key does not grant agents access; existing connections remain manageable in settings.

## Phone and iMessage

Under **Settings → Integrations → Personal**, connect your phone and send the prefilled greeting in Messages. If the pairing does not complete because a relay, keyboard, or OS stripped the invisible pairing token, choose **Or add manually**, enter your number with its country code, and send the new prefilled message. Loosely formatted international numbers are accepted; a number already linked to an active account cannot be claimed. Unlink the current connection before moving the number between active accounts.

The iMessage assistant can inspect supported settings but cannot change them. Use the Hoplite app to change personal, project, integration, or workspace settings; your normal role permissions still apply.

To drive Hoplite *from* your tools instead — Claude Code, Cursor, or another MCP client — see [Hoplite's MCP server](/docs/cli/mcp-server).

## GitCafe

When GitCafe is available in your workspace, an administrator can connect GitCafe with a username and personal access token, sync its discovered repositories, and bind one to a project. The connected repository then uses the same provider-neutral agent tools for branches, pull requests, reviews, and source-control operations.

## Sitemap

Sitemap discovery is not enabled for this deployment.