Admin console · animated

Click to expand

Integrations

Route: /integrations/config

Scenario: You’ve just set up Mushi and want reports to automatically create Linear issues for your team, with Sentry feedback forwarding in and all fix-worker PRs going to your main GitHub repo. This page is where you wire all three up in under 10 minutes.

The Integrations page connects Mushi to the external platforms it reads data from (Sentry, Langfuse, GitHub) and the routing destinations it dispatches events to (Jira, Linear, GitHub Issues, PagerDuty).

Hero

The page header shows: N/M connected (how many platforms are configured and passing their health probe), and the timestamp of the last probe event.

Core platform integrations

These integrations feed data into Mushi or extend its internal capabilities.

Sentry

After saving, Mushi subscribes to Sentry’s User Feedback webhook so new Sentry feedback automatically becomes a Mushi report.

Langfuse

When configured, every LLM call from Mushi’s edge functions streams a trace to Langfuse. Traces are visible in Integration health with a direct link.

GitHub

The Codebase index card shows the indexing status for the active project’s repo — ok, stale, failed, off, or never. The index powers the Repo page branch graph and the fix-worker’s code context.

Cursor Cloud

When configured, Mushi can dispatch a Cursor Cloud Agent to fix classified reports — the agent opens a signed draft PR and posts the link back to the Fixes page. Activate via:

• Marketplace — install the Cursor Cloud Agent plugin for event-driven dispatch (recommended for per-severity gating).
• Settings → Autofix — set autofix_agent = cursor_cloud to make Cursor the project-wide default.

Each platform card shows:

• Connection status pill — connected / disconnected / error
• Latest probe latency
• 7-day health sparkline

Click Edit to reveal the form fields. Click Test to run a live probe and see the result as a status toast.

Routing destinations

These integrations receive Mushi events as outbound webhooks or API calls.

Each routing provider card shows its connection state and a Pause / Resume toggle. When paused, events are dropped — not queued — so resume promptly.

Connecting a routing provider:

1. Click Edit.
2. Enter the required credentials (API key, project/team ID, etc.).
3. Click Save.
4. Click Test to fire a test event.

Disconnecting: click Disconnect → confirm in the dialog.

Common tasks

Connecting GitHub so fix-worker can open PRs

1. Create a GitHub App  and install it on your repo.
2. On the GitHub card, click Edit.
3. Enter the App installation ID, repo URL, and default branch.
4. Click Save → Test → confirm the probe returns green.
5. Open Repo graph — the repo header should show your connected repo.

Forwarding Sentry User Feedback into Mushi

1. On the Sentry card, click Edit.
2. Enter your DSN, auth token, org slug, and project slug.
3. Click Save → Test.
4. In Sentry, add a User Feedback webhook pointing to your Mushi API endpoint.
5. Submit a test Sentry feedback — it should appear in Reports within 30 seconds.

Routing critical reports to PagerDuty

1. In Routing destinations, find PagerDuty → click Edit.
2. Enter your PagerDuty API key and service ID.
3. Click Save → Test → confirm a test incident fires.
4. Go to Reports → triage a critical report → confirm a PagerDuty incident opens automatically.

API

GET  /v1/admin/integrations/platform
PUT  /v1/admin/integrations/platform/:kind   { ...credentials }
POST /v1/admin/health/integration/:kind      (live probe)
GET  /v1/admin/integrations                  (routing destinations)
POST /v1/admin/integrations                  { type, ...config }
DELETE /v1/admin/integrations/:type

Common tasks

Setting up Cursor Cloud auto-fix

1. Create a Cursor API key at cursor.com/dashboard/integrations  → API Keys.
2. Connect GitHub (code repo) first — Cursor agents need your repo URL and token.
3. On the Cursor Cloud card, click Edit, paste the crsr_… key, then Save → Test connection.
4. Install the Cursor Cloud Agent plugin from Marketplace (subscribe to report.classified) — or set autofix_agent = cursor_cloud in Settings if you want every fix dispatched via Cursor.
5. Triage a critical report → trigger dispatch → the Fixes page will show the Cursor agent badge and PR link once the run completes.

Related pages

• Repo graph — powered by the GitHub integration
• Integration health — LLM and cron health (not integration probes)
• Plugin marketplace — advanced routing and custom webhooks
• Fix orchestrator — Cursor agent badge, artifact gallery, and live streaming view