Feature request: in-memory storage that persists across extension reload/update

[crunk1]

I started with a request at the chromium project and they rightfully pointed me here.

Could we get another StorageArea similar to storage.session that persists during extension update/reload? Currently, when an extension updates (or otherwise reloads), storage.session clears.

My usage: we manage some authentication state in storage.session. When the extension updates/reloads, we lose that state. We'd prefer to not do it in local storage; we want memory to clear on browser close.

Spitball proposal: storage.browserSession

[dotproto]

We discussed this request in today's public meeting. At the moment, we feel like the in-progress discussions around introducing a secure storage API are probably a better fit for this use case than introducing a bespoke API for this use case.

For reference 1Password is working on a proposal for this capability (2026-01-15 minute). See also #154.