before 09:12not observed
Version history for work done in the browser.
Pebbleback records how your browser work actually unfolded, then hands it back: a searchable Trail, checkpoints you name, and a clean context pack when you need to hand off. No account, no server.
Below is one example day. Select any time or pebble to stand at that point in it.
Browser state reconciled after an observation gap.
Pebbleback noticed the window had changed while it wasn't watching, and recorded the reconciliation rather than guessing. A Trail shows its gaps. The dashed line above is one.
You open three tabs while chasing a bug.
An issue tracker, a Stack Overflow thread, and the file you're actually editing. Nothing is saved yet. Pebbleback is already watching, locally.
Recorded: title, URL, domain, pinned state, and tab order, nothing else. No page content, no keystrokes, no form values.
The tab is open somewhere. Pebbleback gets you back to it.
Search every open tab by title, site, URL, name, or window. Copies of the same URL group together without hiding where each one actually lives.
- Every window
- one search, all tabs
- Grouped copies
- destinations stay visible
- Safe close
- Undo and Recently closed recovery
You name a checkpoint: “before the migration.”
A note and the active tab references are saved on demand, so this exact moment is retrievable later by name, not by luck.
Or save the whole window as a research set, searchable by project, note, title, URL, or domain.
check upgrade path before touching schema
What changed since this point?
Two checkpoints, side by side. Pebbleback marks what opened, what's absent, what moved, and it says plainly when a tab's identity is uncertain after a restart instead of pretending to know.
- openedMDN — IDBOpenDBRequest: upgradeneeded eventdeveloper.mozilla.org
- absentStack Overflow — IndexedDB versionchangestackoverflow.com
- movedsrc/trail-storage.jslocal file · position 3 → 1
- pinnedIssue tracker — PEBB-142issues.example.dev · unchanged
- ambiguousUnable to confirm whether this is the same tab after restartone candidate, not assumed
One checkpoint, five ways to hand it off.
Every Context Pack is metadata-only: tab titles, URLs, notes, and checkpoint evidence, never page content.
## Context for the assistant
Working on: "before the migration" checkpoint
3 tabs · 1 note
1. Issue tracker — PEBB-142 (pinned)
2. Stack Overflow — IndexedDB versionchange
3. src/trail-storage.js (active)
Note: "check upgrade path before touching schema"## Bug investigation summary
Checkpoint: before the migration
Compared against: after the migration
Opened: src/trail-storage.js:112 (new)
Moved: Stack Overflow tab → window 2
Pinned: Issue tracker (unchanged)
Absent: none## Research handoff
Set: "before the migration"
Sources: 3 · Domains: 2
- Issue tracker (PEBB-142)
- Stack Overflow thread
- Local file reference
Note: check upgrade path before touching schema### before the migration
| Tab | Source | State |
|---|---|---|
| PEBB-142 | issues.example.dev | pinned |
| IndexedDB Q&A | stackoverflow.com | open |
| trail-storage.js | local file | active |{
"checkpoint": "before the migration",
"tabs": 3,
"note": "check upgrade path before touching schema",
"generatedLocally": true
}Preview only. Nothing leaves your browser until you copy or download it.
Close the window. Keep the work.
Park previews the impact, saves a recovery record, and keeps Undo before anything closes. Resume after a restart through whole-checkpoint restore.
- before closingPark previews exactly what will changekept
- recovery recordSaved before tabs actually closekept
- undoPreserved so a close can be reversedkept
- after a restartResume through whole-checkpoint restorekept
- everything elsePage content and full browser history stay untouchednot captured
Everything stays in your browser unless you export it yourself.
No account. No Pebbleback server. No page-content capture. No history indexing. No analytics, and no telemetry on what you save.