You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Save the complete workspace locally with encrypted backup and restore #6
Users should retain their browser testing work on their own PC and move or recover it using a complete downloadable backup.
Acceptance criteria
Automatically save history, tool drafts, requests, responses/snapshots, collections, environments, results, findings, frames and recoverable paused edits in local IndexedDB.
Restore workspace data on reopening without restoring live debugger handles.
Download a complete backup and support optional password encryption using AES-GCM and PBKDF2.
Validate imported data and show a summary before explicit replacement.
Preserve a local undo copy; reject malformed imports without changing current work.
Import/restore sends no requests and leaves Auto mode off.
Preserve an unreadable saved workspace instead of overwriting it automatically.
Document local browser-profile storage, credentials in backups, preview/disk limits and uninstall behavior.
Implementation status
Implemented and verified in PR #1 on feat/v1.1-workbench. PR #1 was merged into main on 2026-10-03, merge commit eeb65009fa6e343cf6dd1f67386be0afc5bbb3e5. GitHub automatically closed this issue as completed through the PR's closing reference. The source changes are now on main; the Chrome Web Store release remains pending.
Verification
Node tests cover backup validation, unfinished drafts, encryption round trips, wrong passwords and tampering. Brave integration verifies full reload, file-picker preview/restore, malformed imports and zero HTTP requests during restore.
Related v1.1 work is tracked through PR #1. Follow-up improvements or bugs should use their own issue and PR.
Completion record
The implementation commits are 7b76001, 3ee1668, 4f1d89c, 504051e, and test follow-up 619736d. Relevant verification is described above and in PR #1. All 29 Node regressions and JavaScript syntax checks pass; GitHub CI passes on Node 22. The workbench/browser features were checked with isolated local HTTP/WebSocket fixtures; shortcut labels were also checked for Mac/Windows/Linux platforms. The maintainer merged PR #1, and GitHub closed this issue automatically; new bugs or follow-up scope should use a separate issue, or reopen this one if its original criteria fail.
User problem
Users should retain their browser testing work on their own PC and move or recover it using a complete downloadable backup.
Acceptance criteria
Implementation status
Implemented and verified in PR #1 on
feat/v1.1-workbench. PR #1 was merged intomainon 2026-10-03, merge commiteeb65009fa6e343cf6dd1f67386be0afc5bbb3e5. GitHub automatically closed this issue as completed through the PR's closing reference. The source changes are now onmain; the Chrome Web Store release remains pending.Verification
Node tests cover backup validation, unfinished drafts, encryption round trips, wrong passwords and tampering. Brave integration verifies full reload, file-picker preview/restore, malformed imports and zero HTTP requests during restore.
Relevant source
local-store.js,lab.js,lab-ui.js,PRIVACY.md,tests/browser-integration.mjsRelated v1.1 work is tracked through PR #1. Follow-up improvements or bugs should use their own issue and PR.
Completion record
The implementation commits are
7b76001,3ee1668,4f1d89c,504051e, and test follow-up619736d. Relevant verification is described above and in PR #1. All 29 Node regressions and JavaScript syntax checks pass; GitHub CI passes on Node 22. The workbench/browser features were checked with isolated local HTTP/WebSocket fixtures; shortcut labels were also checked for Mac/Windows/Linux platforms. The maintainer merged PR #1, and GitHub closed this issue automatically; new bugs or follow-up scope should use a separate issue, or reopen this one if its original criteria fail.