Bitbucket

Bitbucket context enriches an existing Pulse. It does not create Pulses.

How this helps triage: matching excerpts can show up in the summary, the first checks, and What informed this on the Pulse.

Exhale queries selected Bitbucket repositories at triage time and attaches scrubbed recent-commit excerpts as SCM context.

Connect

1. Sign in as a workspace admin.
2. Open Connections → Context → Repositories → Bitbucket.
3. Authorize Bitbucket OAuth and select the repos Exhale may read. Default scopes are account and repository. Reconnect with write access also requests repository:write.
4. Test connection to mark the connector configured.
5. Disconnect clears the stored token.

Bitbucket Cloud access tokens last about two hours; Exhale refreshes them with the stored refresh token before listing repositories or reading commits, and asks you to reconnect if that refresh fails.

Missing credentials, timeouts, or vendor 403s skip this block. Triage still completes. Send-test-alert Pulses skip live collectors.

Plan

Growth or higher.

Connector slots are shared across Context categories (markdown runbooks use a separate document cap). Tighten AI → Prompt → Context use if excerpts are noisy or too large.

API

Canonical paths are under /v1. Writes use the signed-in session and CSRF. Secrets are never returned on GET. Disconnect is DELETE /v1/auth/context-connectors/bitbucket. Start is GET /v1/auth/context-connectors/bitbucket/oauth/start.

Related

• Context index
• Prompt → Context use