Integrations

Bosun integrates with task backends, notification channels, executor providers, and operator-facing infrastructure. This page summarizes the current supported surfaces reflected in the repo today.

GitHub

GitHub integration covers both repository operations and task-board flows.

Repository and PR automation for branches, pull requests, CI status handling, and review/merge logic.
Issues and Projects v2 support when GitHub is the active task backend.
OAuth and GitHub App flows via the GitHub auth modules and portal/server endpoints.

KANBAN_BACKEND=github
GITHUB_REPOSITORY=your-org/your-repo
GITHUB_PROJECT_NUMBER=3
BOSUN_GITHUB_CLIENT_ID=...
BOSUN_GITHUB_APP_ID=...

Telegram and Mini App

Telegram remains the main remote control surface for Bosun.

Bot control for status, tasks, operational commands, and alerts.
Mini App for browser-based operator control and monitoring.
Sentinel for watchdog behavior when the main monitor is unhealthy.

TELEGRAM_BOT_TOKEN=...
TELEGRAM_CHAT_ID=...
TELEGRAM_MINIAPP_ENABLED=true
BOSUN_SENTINEL_AUTO_START=true

Cloudflare tunnel

For stable HTTPS access, current Bosun defaults to named Cloudflare tunnel usage rather than treating quick tunnels as the primary path.

TELEGRAM_UI_TUNNEL=named
CLOUDFLARE_TUNNEL_NAME=my-tunnel
CLOUDFLARE_TUNNEL_CREDENTIALS=/path/to/tunnel.json
CLOUDFLARE_BASE_DOMAIN=bosun.example.com
CLOUDFLARE_ZONE_ID=...
CLOUDFLARE_API_TOKEN=...

Jira

Jira is available as a task backend when you need project-board integration outside GitHub.

KANBAN_BACKEND=jira
JIRA_BASE_URL=https://your-domain.atlassian.net
JIRA_EMAIL=you@example.com
JIRA_API_TOKEN=...

Executor providers

Provider	Current repo support
Codex	SDK and transport-based integration through the shell/agent layers.
Copilot	SDK and transport support with model/profile selection.
Claude	SDK and transport support with Anthropic-backed configuration.
Gemini	SDK configuration and optional voice/vision fallback usage.
OpenCode	Local server integration via `OPENCODE_PORT` and `OPENCODE_MODEL`.

Voice and desktop surfaces

Bosun also includes optional voice and desktop experiences. These are not required for the core monitor, but they are part of the active repo and configuration surface.

Voice mode via VOICE_ENABLED, VOICE_PROVIDER, and related model settings.
Desktop portal via the desktop runtime and related CLI flags.

Container isolation

Agent execution can be isolated with container runtimes when you need a harder boundary.

CONTAINER_ENABLED=true
CONTAINER_RUNTIME=docker
CONTAINER_IMAGE=node:22-slim

Current runtime targets include Docker, Podman, and Apple container support where available.

WhatsApp remains optional and is treated as a secondary notification/control channel alongside Telegram.

bosun --whatsapp-auth
bosun --whatsapp-auth --pairing-code