BugJar
A local-first browser session recorder that preserves what happened within a scope the user defines.
2026·Browser extension·in progress
BugJar began with the gap between a reported issue and the context needed to understand it. I wanted a browser session to carry its own evidence: console logs, network activity, DOM changes, and the sequence that connected them, instead of leaving the investigation to memory and guesswork.
The recorder only runs where the user allows it to. Sessions stay on the local machine unless they are deliberately exported; there is no background telemetry or cloud upload built into the recording flow.
The harder problem was not capture alone, but trust. Every boundary had to remain visible: where recording can happen, when it is active, and what is allowed to leave the device.
- Role: Product direction and development
- A capture preserves console logs, network activity, DOM changes, and the sequence that led to an issue.
- Recordings stay on the device unless the user explicitly exports them.
- Trust grows when a tool behaves consistently and makes its limits visible.
- Data sovereignty means little unless the architecture enforces it.
- extension
- architecture
- tooling