>_ exfiltr
Updates → EN⌄
// tab/session recovery · internal prototype

TabRest: save and restore Chrome sessions after crashes.

TabRest saves Chrome tab sessions locally so unfinished browser work can be backed up, exported, reviewed, and restored after crashes, restarts, project switches, or failed session tools.

Request updates → Privacy posture
// Workflow preview

Save a session. Back it up. Restore it predictably.

TabRest is being tested around the parts that make session tools feel risky: readable JSON export/import, restore ordering, pinned tabs, large session limits, storage visibility, and clear local behavior.

TabRest
Save current window
Launch QA7 tabs
Reader research4 tabs
internal prototype · CWS prep pending
// Product basics

What it does.

  • Category: crash recovery, session continuity, and backup.
  • Workflow pain: browser working memory gets lost across crashes, restarts, project switches, tool removals, abandoned extensions, or failed imports.
  • Status: internal prototype; CWS prep pending.
  • Trust posture: sessions stored locally and never sent to any server in V1, readable user-controlled backup/export, no page-body reading, no install claim before release review.
// Problem

Tabs hold unfinished work.

TabRest is scoped for users who feel real anxiety when Chrome restarts, imports fail, or a session tool becomes unreliable.

// Workflow

Save, back up, restore.

V1 saves the current window or session locally, shows saved sessions clearly, supports readable JSON export/import, restores predictably, and makes deletion obvious.

// Not this

Not a tab-management platform.

TabRest V1 will not ship accounts, cloud sync, AI tab grouping, productivity scores, project boards, shared spaces, or team features.

Product notes

TabRest is being built to reduce tab/session loss anxiety without becoming dashboard-heavy productivity software.

  • Core action: save a browser session and restore it later.
  • Recovery: readable export/import, pinned tabs, restore order, storage visibility.
  • Trust: stored locally in V1, no page-body reading, no tracking, no account.
  • Status: internal prototype; CWS prep pending.

Expected V1 Permissions

  • tabs: read tab titles and URLs so the user can save and restore sessions.
  • storage: store saved sessions locally in the browser.
  • sessions: only if V1 uses Chrome session APIs for recently closed tab or window recovery.

Trust posture

TabRest handles sensitive browser context. V1 should avoid host permissions, avoid reading page content, avoid external sync, make backup/export visible and user-controlled, store sessions locally, and explain tab access clearly before submission.

View TabRest permission registry →