Extensions
One library of browser extensions, assigned per profile. What Ant0 accepts and how updates reach running profiles.
Updated Sep 7, 2026
The library
Extensions holds every extension once. Add it from a file or folder, then pick it in a profile’s Advanced settings. The list shows each extension’s name, version and how many profiles use it.
Accepted inputs:
- an unpacked extension folder (the one with
manifest.jsonat its top level); - a .zip of such a folder;
- a .crx file as downloaded from a store.
Ant0 keeps its own copy under the data folder, so the original file can be moved or deleted afterwards. There is no store browser inside Ant0: download the extension you need, then add it.
Assigning to profiles
Open a profile’s editor, expand Advanced, and tick the extensions to load. The extension is loaded when the profile next starts; a running profile picks up changes after Stop and Start.
Extensions are loaded from the shared copy, but their settings and data are per profile: what you configure in one profile does not appear in another, as with any other cookie or storage.
Removing
An extension that is still assigned to a profile cannot be removed; untick it there first. Removing deletes the library copy; profiles keep their own settings until they are next started without it.
Command line
ant0 extensions add ./my-extension # folder, .zip or .crx
ant0 extensions ls
ant0 extensions rm <id>
ant0 profiles edit "Shop DE" --set launch.extensions=<id>,<id>