When the browser forgets,
start here.

Use Chrome's own recovery first. Accept the Restore pages prompt if it appears, open History and check Recently closed, or press Ctrl + Shift + T on Windows and Linux—or ⌘ + Shift + T on macOS—more than once. Also confirm Chrome opened the expected profile.

For future interruptions, Chrome's “Continue where you left off” setting can reopen the previous session. Re:Stack complements native recovery with automatic recovery points and named backups; it cannot reconstruct a session lost before Re:Stack recorded it.

Browser history primarily records visited pages, not every part of the workspace around them. After a crash, URLs may return while group names, colours, collapsed state, window boundaries or tab order are incomplete. Re:Stack records those relationships so a recovery point can preserve more context than a flat history list.

Re:Stack records tabs within their source windows and restores window boundaries from a selected recovery point or backup. Browser restrictions and changes since capture can affect the result, so the interface previews counts and restores deliberately rather than promising an exact operating-system snapshot.

Re:Stack is designed to compare recovery targets with tabs already present and recover missing work instead of blindly reopening everything. No comparison can infer every intention—the same URL may legitimately belong in two windows—so review a recovery point before applying it.

Incognito persistence is off by default and Chrome must separately allow the extension to run in incognito. If enabled, Re:Stack can record eligible incognito session information according to its settings. Enable it only when the continuity benefit matches your privacy expectations.

The latest automatic recovery point represents the recently observed browser session and is intended for interruption recovery. A named backup is a deliberate snapshot kept for a meaningful moment, such as before closing a research workspace or reorganising many tabs. Native browser history remains separate from both.

Re:Stack supports parked or background restoration so a large workspace does not have to consume the memory and processor load of fully active pages immediately. Browser support determines how inactive tabs are handled, and restricted browser pages may not be restorable.

Yes. Re:Stack brings open tabs, pinned or starred items, tab groups and bookmarks into one management interface while preserving the distinction between those different browser objects.

You can export encrypted continuity data or enable an available cloud provider. Cross-device restoration is user-controlled: another device does not silently replace its local session merely because a newer cloud file exists.

Re:Form records compatible fields while you work, then lets you review encrypted recovery entries by website and time. If a compatible value was captured before the interruption, you can inspect and restore or copy it. Re:Form cannot recover text entered before installation, before capture was allowed, or in a field the browser prevented it from observing.

Re:Form is designed to support ordinary inputs, text areas and compatible rich-text editors, including the kind used for substantial Jira descriptions. Complex editors can change their internal structure, so Jira and other web applications require compatibility evidence rather than a blanket guarantee. Recovery never submits the issue or comment for you.

No. It reacts to eligible field changes and stores allowed field values as encrypted recovery records. It is not designed as a keylogger and does not retain a chronological record of every key, mouse movement or scroll action.

Recovery is deliberate. Re:Form shows the saved form and fields so you can inspect them before restoration. It does not silently submit a form, and recovery controls should not replace non-empty live work without the user's choice.

Yes. You can maintain reusable encrypted values and website-specific rules for fields you choose. Autofill supplies a saved reusable value; recovery returns a value captured from unfinished work.

Payment-card numbers, expiry details, card-security codes and payment PIN fields are always excluded. Password and one-time-code categories are disabled by default and require explicit higher-risk opt-in. Ordinary billing names and addresses can remain eligible under general capture settings.

The current release work targets Google Chrome and Chromium extension APIs. Firefox, Safari and other browsers remain later portability work and should not be treated as supported until their permissions, storage, grouping and recovery behaviour has been validated.

Browsers protect internal pages such as extension settings, the Chrome Web Store and some privileged URLs. Extensions cannot inject into or reopen every restricted target like a normal website. OddWorks keeps those browser security boundaries instead of bypassing them.

Re:Form includes support for ordinary fields, contenteditable surfaces and complex-editor patterns, but websites implement them differently. Multi-page recovery groups compatible records into a form-oriented view; exact visual reproduction of the original site is not required for saved values to remain useful.

No account is required for the core local functionality in each product's free capability set. An OddWorks account is used for entitlement and subscription management and is separate from browser-workspace content, form text and encryption material.

Both extensions are local-first and use browser extension storage for working data. If you deliberately enable a supported cloud provider, the extension transfers an encrypted file to storage associated with your provider account. See the Privacy Policy for current product and provider details.

OddWorks account services receive account and entitlement information, not Re:Stack URLs, titles, bookmarks or backups, and not Re:Form field values or page content.

OddWorks cannot recover an encrypted local export or cloud file without the required password or key material. Re:Form's master password is not stored by the extension and must be entered again after the browser session ends.

No. Both products are designed to remain useful in local-only mode. Cloud sync is an optional continuity layer for devices you control, not a dependency for core local capture and recovery.

Google Drive is the enabled provider in the current release configuration. OneDrive and iCloud remain disabled until their registrations, authentication flows and production behaviour are proven.

The extension continues using its local copy where browser storage remains available. A failed cloud sync should be shown as a sync problem rather than preventing local operation. Resolve provider quota or connectivity before relying on the cloud copy from another device.

No. The design uses identifiable records, event history and controlled encrypted snapshots, but it is not a blockchain and does not claim blockchain consensus or immutability. Conflict handling must protect local data and avoid silently replacing a newer workspace with an older one.