Packaging and sharing

Build the package

From the downloaded SDK folder, check and pack your extension. The file is named from the manifest ID and version, and is written beside the extension folder unless you set --out.

sh bin/browse-ext check my-plugin
sh bin/browse-ext pack my-plugin
sh bin/browse-ext pack my-plugin --out packages

A .browseext file is a ZIP with browse.toml at its root, the Python entry point and supporting files. Keep assets inside the extension folder. The packer skips hidden files, caches and virtual environments. Review the archive contents before sharing: other ordinary files in the folder are included.

Install and update

1. In Browse on macOS, open Settings → Extensions → Add… → Add Extension….
2. Choose the .browseext file or an extension folder.
3. Review the name and permissions, then install. Test the installed copy before sharing it.
4. For an update, keep the same manifest id and increase version. New permissions require approval before the extension runs again.

Browse Community

Browse uses its own plugin category in ANTI Community. A Browse plugin is a .browseext package using the Browse SDK; it is not interchangeable with a Clink plugin.

• Browse Community
• Browse development updates

Before sharing

1. Give the plugin a stable ID, clear name and concise description.
2. Request only the capabilities and sites you use. Explain those permissions to users.
3. Test the archive in Browse, including callbacks, reloads, empty states and failure cases.
4. Include your icons and pure-Python dependencies, and verify their redistribution terms.
5. State the tested Browse build and platform. Distinguish intended portability from host support that exists today.