Runic’s integrations are local-first. The Preferences > Sync > Integrations pane is a control center for surfaces that already exist in the app rather than a promise that Runic is running a background network service.
Available today
- CLI JSON access: copy
runic usage --format json --prettyfor local scripts, CI, and dashboards. - OpenTelemetry GenAI ledger: view, reveal, and copy the default sanitized JSONL collector path. Add extra JSON/JSONL files or folders through Additional usage log paths.
- Runic MCP: connect an AI client to the bundled local stdio server for read-only limits and refresh health. Add trusted local tool packages without rebuilding Runic. See MCP setup and package format.
- MCP profiles: save localhost bridge profiles and copy
mcp connect localhost:<port>commands for external MCP processes that users run themselves. - Alert webhooks: save a default webhook URL, choose Slack/Discord/generic test payloads, and send a test request. New alert rules can reuse the saved default URL.
- GitHub commit correlation: validate a repository path and copy
runic insights --with-commits --git-directory "<repo>/.git" --json --pretty. - Kosha registry: detect and reveal
~/.kosha/registry.jsonfor local model context metadata. - Provider API keys: link users back to provider documentation and Preferences > Providers, where keys live in macOS Keychain.
Feature research
- Local HTTP API: expose the same read-only CLI JSON payloads over a localhost-only server with explicit enablement and Keychain-backed token auth.
- Webhook dispatch history: record delivery attempts for alert webhooks so failures are visible after the transient test result disappears.
- GitHub project mapping: reuse
GitHubIntegrationto enrich project summaries in the app UI, not onlyrunic insights --with-commits. - Kosha sync health: surface registry age, stale status, and provider coverage next to the current path detection.
Read the source ↗ Checked against Runic 2.13.5 · 9730f91