Agent session forensics

Build a shareable audit trail from agent session logs

When a Cursor or Claude Code session goes wrong, IncidentScribe parses the JSONL export into a forensic timeline — surfacing destructive commands like DROP DATABASE and force pushes with evidence you can paste into tickets, postmortems, and stakeholder updates.

30-day satisfaction guarantee · Instant ZIP download after checkout — no account required for the pack · Use the filled sample in your next incident tonight

The post-incident grep spiral

After an agent deletes a database or force-pushes main, your team is left scrolling raw JSONL exports or chat logs — hunting for the destructive command among thousands of lines. Manual grep is slow, error-prone, and hard to share with stakeholders who need a clear sequence of facts, not raw JSON.

Manual grep vs forensic export

Raw JSONL grep finds strings; IncidentScribe produces a structured audit trail with critical highlighting and export formats your team can share.

CapabilityManual grepForensic export
SpeedHours scrolling chat logs and piping JSONL through ad-hoc scriptsDrop a file — timeline, digest, and critical events in seconds
Critical highlightingRegex misses context; destructive commands buried in noiseDestructive patterns flagged automatically (DROP, force push, recursive delete)
Export formatsCopy-paste fragments; no consistent structure for stakeholdersMD, HTML, JSON, CSV, and critical-summary MD from CLI or browser

Supported agents

IncidentScribe uses tolerant JSONL parsing for each export shape — malformed lines produce warnings instead of aborting the run.

Agent / sourceWhat we parse
CursorNative JSONL export; shell, apply_patch, write, and StrReplace tool shapes mapped to file edits with paths in summaries.
Claude CodeClaude Code session export lines normalized to shell, file edit, and message events.
OpenCodeOpenCode export format with tool and terminal activity preserved in the timeline.
Codex / Agents SDKCodex and OpenAI Agents SDK JSONL — shell commands and file edits from agent tool invocations.
MCP tool callsMCP server invocations surfaced as tool_call events with server and tool names in summaries.
WindsurfCascade transcript JSONL and hook events — shell commands, code_action file edits, and planner messages from agent sessions.
GitHub Copilot ChatCopilot CLI and agent-mode events.jsonl — tool executions, terminal commands, and user/assistant messages.
Generic JSONLAny JSONL with recognizable type or kind fields; unknown lines are skipped with warnings.

Export formats

Download or render from the browser or CLI (incidentscribe render --format) without uploading session data to a server.

FormatTierBest for
MarkdownFreeTicket paste, docs, and blameless postmortem drafts
HTMLFreeShareable read-only timeline in email or wikis
JSONFreeProgrammatic replay and custom integrations
CSVFreeSpreadsheets and SIEM correlation
Critical summary MDFreeCritical-only excerpt for incident channels
Slack Block KitFreePost critical events to Slack via incoming webhook or workflow
incident.io JSONFreeImport timeline events into incident.io with severity flags
PDFTeamPrint-ready forensic report with git commit correlation

Team exports (PDF and git correlation) require the Shopify subscription — see the Team pricing card below.

Proof: sample session timeline

This read-only preview is built from the committed cursor-sample.jsonl fixture — including a critical DROP DATABASE event.

Drop a JSONL file, paste below, or try the sample timeline

What the pack turns evidence into:
Raw critical event: DROP DATABASE production;

Rendered (timeline row + filled section):
| +13168920s | ... | shell | DROP DATABASE production; | critical |
## Impact
Production database outage observed after agent session. Service unavailable following the critical shell commands in the timeline.

## Root Cause
Agent executed `DROP DATABASE production;` followed by `rm -rf /tmp/build-cache`. The session message requested investigation of the outage; `read_file` and follow-up message located the issue in the deploy script.

Why IncidentScribe

Pricing

Free

$0

  • Web timeline viewer with forensic digest
  • Markdown, HTML, JSON, and CSV export
  • Critical summary MD for ticket paste
  • Basic CLI (render, validate)
Try free timeline

Postmortem Pack

$12 one-time

Complete stakeholder postmortems from your timelines

Produce a complete blameless postmortem with timeline evidence you can paste into tickets and stakeholder updates in minutes.

Free surfaces the facts. Pack finishes the report in minutes.

  • Filled sample shows real DROP DATABASE + rm -rf events turned into a ready-to-use report.
  • Templates, forensic checklist, rollout guide and GitHub Action included.
Example from filled sample:
| +13168920s | ... | shell | DROP DATABASE production; | critical |
## Root Cause
Agent executed `DROP DATABASE production;` followed by `rm -rf /tmp/build-cache`.
Get Pack — instant download, use in your next incident

Secure Stripe checkout via Hermes Plant · Instant download · Use immediately

30-day satisfaction guarantee · Instant ZIP download after checkout — no account required for the pack · Use the filled sample in your next incident tonight

After checkout — your next 5 minutes:

  • Download the ZIP immediately
  • Open README.md → 2-minute quick start
  • Copy templates/ or use with the CLI
  • Later: add Team subscription for cloud archive + webhooks