---
schema_version: 1
revision: "22ce5d34dbcb5a78"
id: "factory-tools-state-capture-markers"
title: "Just-in-time state capture (markers)"
---

# Just-in-time state capture (markers)

Tool roles, alternatives, selection tradeoffs, and compatibility caveats.

## Just-in-time state capture (markers)

**John uses:** **agent-markers** (section 09; pattern page at [mindful-mango-accy.here.now](https://mindful-mango-accy.here.now/)) — a \<300-line, dependency-free recorder: console/fetch/error/click patched into a ring buffer, a  Mark keystroke pins one sentence of human testimony to nearby events, and the export renders into a redacted agent-ready debug packet. The differentiator is *testimony as a first-class artifact* and privacy-by-redaction.

| Alternative | What it is | How it differs | License |
|----|----|----|----|
| [rrweb](https://github.com/rrweb-io/rrweb) | Record and replay the web: DOM-level session recording library | Full DOM replay vs markers' redacted event trail; the building block most replay products use | MIT |
| [OpenReplay](https://github.com/openreplay/openreplay) | Self-hostable session replay + product analytics for reproducing issues | Always-on infrastructure with a server; markers is a one-file, moment-of-surprise capture | NOASSERTION (ELv2/MIT mix) |
| [Highlight](https://github.com/highlight/highlight) | OSS full-stack monitoring: session replay, errors, logs, traces | Monitoring-platform scale; check current repository activity | NOASSERTION (Apache-2.0 core) |
| [Sentry Session Replay](https://github.com/getsentry/sentry) | Session replay wired to error tracking in Sentry | Error-first: replays attach to exceptions rather than to human testimony | NOASSERTION (FSL) |
| [Jam](https://jam.dev/) | Chrome extension: one-click bug reports with replay, console logs, network requests, device details | Commercial, human-in-the-loop like markers — the closest 'press a button at the moment of surprise' product; output targets issue trackers, not agent prompts | commercial (free tier) |

### Pick this if…

- **Jam** — the closest commercial "press a button at the moment of surprise" tool; output targets issue trackers rather than agent prompts.
- **rrweb** — you're building your own marker system and want full DOM replay under it.
- **OpenReplay / Highlight** — you want always-on capture infrastructure you control.
- **Sentry** — your entry point is errors, not human testimony.
- Or lift the workshop's recorder itself — it's ~300 dependency-free lines, designed for exactly this.

## Original references

- [Tool comparison reference](https://dewy-sleet-n5zs.here.now/#state-capture-markers)
