Many of us who work all day in the browser need to run 10+ profiles simultaneously to stay signed in and up-to-date. We also need to work across web apps in different profiles—this is simply not possible in Chrome, Edge, Vivaldi, Brave, etc.
This is the main reason we built Wavebox. Cookie Containers were the driving force behind our conception (Wmail originally offered multiple Gmail sign-in), and read on to find out how they work and how they will transform how you work on the web. 🙌
How do Cookie Containers work?
Wavebox Cookie Containers are used to isolate or share cookies between apps. They allow you to work across an unlimited number of different 'personas' all within the same browser window. Here are some factoids about Containers:
- You can create as many Containers as you like in Wavebox.
- Using Containers, you can stay signed in to every account e.g., multiple Gmails, Slacks, Discords, etc.
- You can seamlessly work across all your Containers without signing in and out.
- You can easily create, edit, manage and delete Containers in 'Settings > Cookie Containers.'
- Any Containers you set up can be synced with Wavebox on other computers.
- Containers can be shared across teams of Wavebox users.
Now let's take a look at an example. I've set up Wavebox with a few apps in my webdock. I've used dividers to group them into Work and Home (dividers don't have anything to do with Containers, but it helps illustrate the example.
Everything under 'WORK' lives in my Work Container, and everything under 'HOME' lives in my Home Container. This means that my Work and Home Gmail apps are completely isolated, the stuff in my work ClickUp never leaks out into my Home Discord, and so on. I can navigate between all these apps by simple clicking on the webdock icon, with no need to sign-in and out. Wavebox Cookie Containers act like clever mini browser profiles all the same window.
But it gets even better. Containers are linked to the apps themselves, which means that wherever you move the apps to e.g., webdock group, workspace collection, it will stay in the same Container.
So in the example above, I've created a collapsable 'SOCIALS' divider to keep all my social media apps together in the webdock. Under the divider are my two Twitter accounts—one is in the Work Container, and the other is in the Home Container. Even though these accounts are under the same divider, they will stay correctly signed in, and I can switch between them to get stuff done.
How do I create/choose a Cookie Container?
When you add an app to Wavebox, it automatically picks what it thinks is the most suitable Container for your new app. Usually, that's the Default Cookie Container, but you can choose any Container. When you try to add a second app of any type, e.g., a second Gmail account, Wavebox will generally suggest a new Container. For example, in the screenshot above, I'm trying to add a third Gmail app, but since I already have two, Wavebox prompts me to create a new Container or use an existing Container that doesn't include any Gmail apps.
What is the Default Cookie Container?
Wavebox has a concept of a Default Cookie Container, which is used when Wavebox doesn't have enough context to make a better decision on which Container to use. If you're using Wavebox mostly for work, the default cookie container will include all your work apps. If you primarily use Wavebox at home, the Default Container will include all your 'home' apps.
Which Cookie Container am I using?
Once you've got your Cookie Containers set up, you'll occasionally need to check which container the current app or tab is using. Wavebox always shows the current Cookie Container icon next to the right of the address bar (small circle). You can click on the icon to get more details about that Container and carry out some useful actions.
How do I rename and edit my Cookie Containers?
You can use as many Cookie Containers as you like in Wavebox, so we've made it easy to manage them. Go to 'Settings > Cookie Containers' to see a list of all your Containers, and change the name and icon for each. 👍
If you want to check which apps are in each Container, and maybe move them around a bit, then you can do this using the Drag and Drop Cookie Container Manager. The short video above shows how this works. Click on a Container in the list, and it will highlight all the apps in that Container. Drag a Container icon and drop it over any group/app icon to add it to that container. Go to: Containers in Settings > Cookie Containers > Drag and Drop Container Manager (button).
Cookie Containers and Extensions
Extensions work across all Cookie Containers, but under the hood, they store their extension cookies in your Default Container cookie jar. We are looking to provide support for running the same extension in multiple Containers sometime in 2023 e.g., HubSpot for a client and Hubspot for yourself. We currently support locking an extension to just one Container, e.g., locking Grammarly to your 'work' container will show the Grammarly prompts on every page, but not in other Containers.
What about Profiles?
Yes, Wavebox has Profiles too, but they are slightly different than in Chrome. Wavebox Profiles enables you to create multiple instances of Wavebox, e.g., an isolated Wavebox for home and another for work, each with its settings, theme, groups/apps/tabs/workspace, Containers, and webdock.