Isolated Containers???

[enesehs]

I want to create a Firefox/Zen container that keeps its own browsing data and cookies, but whose history is completely isolated. The browsing history from this container should only be visible while I’m using that container, and should be completely hidden when I’m outside of it. Ideally, the container’s data (like cookies or session info) would remain intact, but its history entries wouldn’t appear in the global history or be accessible from other containers. A form of encryption or local isolation for that container’s history would be perfect.

[dosubot[bot]]

Hi @enesehs! I'm Dosu and I’m helping the desktop team.

Zen Browser and Firefox containers isolate cookies and session data per container, so you can keep logins and site data separate. However, browsing history is still managed globally—history entries from all containers are visible outside the container, and there’s no built-in way to hide or encrypt container-specific history from other containers or the global history view (source, source).

Some users have requested true per-container history isolation, and there’s discussion about possibly modifying how history is stored (using userContextId in places.sqlite) to achieve this, but it’s not currently implemented (source). For deeper isolation—including history, cookies, extensions, and settings—using separate Firefox profiles is the only reliable solution right now (source).

If you want to manage cookies per container, you can use extensions like Firefox Multi-Account Containers or Cookie AutoDelete (source). For history isolation or encryption, there’s no native support or extension available at this time. This feature is on the Zen Browser community’s radar, so it may appear in future updates.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}