CrumbtrailCrumbtrail
How it works

From a ticket to an answer your agent can act on

Six stages, none of which need a person to click anything in Crumbtrail.

The loop

  1. Capture

    Capture runs before the ticket exists

    The browser and server SDKs keep a rolling record of sessions and backend events. If you already run OpenTelemetry, point your exporter at Crumbtrail instead and skip the SDK. Evidence cannot be attached to a failure after the fact, which is why this runs continuously rather than on demand.

    Correlation keys
    • sessionId
    • requestId
  2. Ticket

    A ticket arrives

    Crumbtrail connects to Jira Cloud over OAuth and reads new tickets as they are filed. Your tracker stays the system of record for assignee, status, and service level. Crumbtrail never becomes a second place to manage work.

    • issueKey
  3. Correlate

    Symptoms are correlated to a window

    The ticket text is matched against captured evidence to locate the incident window: which sessions, which requests, which backend spans. Correlation keys are stamped during capture, so the join already exists rather than being guessed at query time.

    • traceId
    • sessionId
  4. Assemble

    One bundle is assembled

    Interface steps, console output, network calls, database row diffs, and the repository code involved, collected into a single incident bundle.

    • bundleId
  5. Opinion

    An opinion is attached, clearly separated

    Alongside the neutral evidence sits a ranked advisory opinion across regression, data, infrastructure or configuration, client side, and intentional change. It is marked as advisory, it never blocks, and inconclusive is a valid answer.

  6. Recall

    The next occurrence is remembered

    Recurring failures resolve to one canonical issue, so a repeat surfaces the earlier incident and whether the previous fix held.

    • canonicalIssueId

You choose how far it goes

Three levels, set per project, and you move the dial.

  1. Level 1

    Detect and alert

    Crumbtrail tells you a silent failure is happening and gives you the reproduction. Nothing is filed.

  2. Level 2

    Ticket to bundle to agent

    A ticket produces a bundle and a link your coding agent can pull. This is the common setting.

  3. Level 3

    Fix pull requests

    Crumbtrail opens a pull request against the repository. This is off by default and stays off until you turn it on.

Walk through it on a real ticket

Bring a failure from your own stack and we will show the bundle it produces.

Book a demoSee every capability