Four parts that talk to each other
SDKs that record, a cloud that correlates, a dashboard for people, and an MCP server for agents.
SDKs
Published on npm and installable today.
crumbtrail-coreThe browser SDK. Zero dependencies. Collectors, redaction, and silent failure detection.
crumbtrail-nodeThe server side. Capture ingest, an OTLP receiver for traces and logs, Express middleware for request correlation, and the MCP server.
crumbtrail-reactReact bindings, including an error boundary that captures the session and a hook that records component state.
crumbtrail-react-nativeReact Native and Expo support for errors, network, navigation, and view tree snapshots.
crumbtrail-tauriA Tauri v2 plugin for desktop sessions over native interprocess communication, with no server process required.
crumbtrailThe setup wizard. It detects your framework, wires in the SDK, and verifies the first event arrives.
Cloud
Ingest, correlation, diagnosis, and metering.
Session ingest
Session start and end, batched events, and flags. Every write is key authenticated, ownership checked, and privacy scrubbed.
OpenTelemetry ingest
Traces and logs over OTLP in JSON and protobuf, joined to the owning session through a durable trace join store.
Canonical issues
Detector signals are grouped into incidents and resolved to one canonical issue through an alias table, so a later session with partial signals resolves back to the same issue.
Diagnosis on your code
Analysis reads the customer repository, so a recommendation points at real files rather than generic advice.
Data protection
Envelope encryption for hosted artifacts, per project redaction levels, deletion jobs with receipts, and a retention purge keyed to your plan.
Ticket connection
Jira Cloud over OAuth. The tracker stays the system of record and Crumbtrail mirrors its state.
Dashboard
Where a person looks when they want to look.
Triage the issue queue, inspect the evidence behind any claim, compare sessions, and manage projects, keys, and integrations. The product is designed so the pipeline works without anyone opening this, but the evidence is here when you want to read it yourself.
MCP
The interface your coding agent actually uses.
The MCP server exposes captured evidence to any connected agent, reading from local disk or from the cloud. Two paths work equally well: paste a ticket reference into your agent and the server resolves it to the bundle, or follow the link Crumbtrail posts on the ticket. Tool mapping for Splunk, PostHog, and Cloudflare is built from live discovery and tenant review rather than a certified vendor profile, so treat those three as reviewed rather than warranted.
See it against your stack
Bring your tracker and your telemetry and we will show what correlates.