Add to Chrome — free

Browser checkpoints for pull requests and incidents

A useful developer snapshot has a commit-shaped boundary. Before leaving a pull request, collect the diff, CI run, issue, reproduction, and relevant API documentation in one current Chrome window, give the native groups meaningful labels, and save that window under the repository and ticket identifier. Tabwell records the window's tab order, pinned state, and group title, color, collapsed state, and membership in local IndexedDB. It does not capture the code checkout, terminal state, page contents, credentials, or edits inside a web application, so the snapshot complements Git and the issue tracker rather than replacing them. When the defect returns weeks later, Pro search can query a tokenized index of saved titles, URLs, and group names and lead back to the matching snapshot. This page is a workflow for deliberate PR handoffs, not a promise that every browser interruption preserves the last keystroke.

Make the checkpoint match a code boundary

  1. Put one PR or incident in the current window.
  2. Label groups with a repository, ticket, or service name.
  3. Save the window as repo — PR-184 — review.
  4. Record the commit or deployment reference in the issue tracker, because Tabwell does not save it from page content.
  5. Restore a disposable copy and compare tab and group counts before closing the live window.

Retrieve an archived review

Pro search uses indexed saved tab titles, URLs, and native group names. A repository slug, ticket key, documentation domain, or CI job title can locate the snapshot even when those tabs are closed. The query does not inspect source code, rendered page bodies, console output, or local files.

Handle interruptions honestly

A manual snapshot is the precise checkpoint before a branch switch or planned Chrome relaunch. Periodic auto-snapshots provide a recent recovery point; after an unexpected shutdown, Tabwell can offer the latest periodic snapshot when crash recovery is enabled. Free uses a 60-minute timer. Pro offers 5, 15, 30, or 60-minute intervals. Closing Chrome does not create a final snapshot.

Portability and plans

Export JSON when the browser map belongs with a project handoff or off-profile backup. Tabwell does not provide cross-device sync. Install it from the Chrome Web Store. Current prices, purchase options, and terms are listed on the pricing page.

Snapshots, tab titles, and URLs stay in local IndexedDB. Billing and license requests use Tabwell's billing service and Polar without sending tab data. Optional redacted crash diagnostics can be enabled; they are off by default. See the privacy policy.

FAQ

What belongs in a PR checkpoint?

The current window's review pages, CI jobs, issue thread, reproduction, and documentation. Keep the commit and code state in Git and the issue tracker.

Can search find a ticket key in an old snapshot?

Yes, when the key appears in a saved title, URL, or native group name. Pro uses a tokenized local index and does not search page contents.

Does one snapshot capture several Chrome windows?

No. It captures the current window. Save other development windows separately and use names that identify their repository or incident.

What is the safest checkpoint before a relaunch?

Make a manual snapshot and verify it. Shutdown does not trigger a new capture; periodic recovery may be older than the latest work.

Can a browser checkpoint move with a project?

Export snapshots to JSON for a deliberate backup or handoff. This is manual portability, not automatic synchronization.