Kommit ingests agent activity from three categories of source. This list reflects what's live today; the roadmap below covers what's coming.
Live today
LLM provider call sites
These connect at the SDK call site. You import a thin Kommit wrapper instead of (or in addition to) the provider SDK directly, and we capture the request / response metadata.
| Provider | Status |
|---|---|
Anthropic (@anthropic-ai/sdk) | ✓ Live |
OpenAI (openai) | ✓ Live |
| Mistral | ✓ Live |
| Google (Vertex AI, Gemini) | ✓ Live |
Agent frameworks
Either via the framework's own callback / hook system, or via the Kommit SDK if you instrument manually.
| Framework | Status |
|---|---|
| LangChain (Python + JS) | ✓ Live via callbacks |
| LangGraph | ✓ Live via state-machine hooks |
| Autogen | ✓ Live via SDK |
| Crew | ✓ Live via SDK |
| Raw provider SDK (no framework) | ✓ Live via SDK |
Log forwarders
For agents you'd rather not modify, point your existing log pipeline at Kommit.
| Source | Status |
|---|---|
| S3-compatible bucket (incl. Hetzner Object Storage, Cloudflare R2) | ✓ Live |
| Datadog log forwarder | ✓ Live |
| Loki (Grafana Cloud or self-hosted) | ✓ Live |
| Honeycomb | ✓ Live |
| Generic webhook receiver | ✓ Live |
Notification destinations
Where Kommit sends approval requests and incident notifications.
| Destination | Status |
|---|---|
| Slack | ✓ Live |
| Microsoft Teams | ✓ Live |
| Webhook | ✓ Live |
| ✓ Live | |
| Discord | ✓ Live (used internally; available to customers) |
Design-partner roadmap
These are not in the product yet. We'll build them with the design partners we're currently signing — typical activation timeline is 4–8 weeks from contract.
- —AWS Bedrock runtime
- —Azure OpenAI runtime
- —Helicone observability bridge
- —Langfuse observability bridge
- —PagerDuty incident escalation
- —Jira / Linear ticket creation on incident
- —Direct integration with Snowflake / BigQuery for cost telemetry
If you need any of these in production sooner, tell us during intake — we can usually accelerate one or two per design-partner cycle in exchange for being your reference implementation.
What we don't connect to
- —Browser-extension agents (e.g. anything that scrapes a UI from inside the user's browser) — the security model is fundamentally different and we'd rather not pretend.
- —Air-gapped environments (no outbound from the agent host) — Kommit needs to ingest events; an air-gapped agent can't emit them outbound to us. Customers in this bucket have used Kommit's on-prem deployment as a fallback, but that's Enterprise-only.
See [#connecting-your-first-agent] for the connect walk-through and [#engagement-shapes] for which sources are available on which engagement.