Skip to main content
Manage browser extensions for use with Kernel browsers.

Extension Management

kernel extensions list

List all extensions in your organization. Output includes:
  • Extension ID
  • Name (if assigned)
  • Created date
  • Size in bytes
  • Last used date
Example:

kernel extensions upload <directory>

Upload an unpacked browser extension directory or zip file.
FlagDescription
--name <name>Optional unique name for the extension. Must be unique within your project.
Example:
Extensions requiring enterprise policies must include update.xml and .crx files. See Extensions requiring enterprise policies for details.

kernel extensions download <id-or-name>

Download an extension archive by ID or name.
FlagDescription
--to <path>Output path for the downloaded zip file.
Example:

kernel extensions delete <id-or-name>

Delete an extension by ID or name.
FlagDescription
--yes, -ySkip confirmation prompt.
Example:

kernel extensions download-web-store <url>

Download and unpack an extension directly from the Chrome Web Store.
FlagDescription
--to <path>Output directory for the unpacked extension.
--os <platform>Target OS: mac, win, or linux (default: linux).
Example:
After downloading, you can upload the extension to Kernel:

kernel extensions build-web-bot-auth

Build Cloudflare’s Web Bot Auth browser extension for signing HTTP requests with RFC 9421 signatures.
FlagDescription
--to <dir>Output directory for the built extension (required).
--key <path>Path to JWK file with Ed25519 signing key (defaults to RFC9421 test key).
--upload <name>Upload the extension to Kernel with specified name (e.g., —upload my-web-bot-auth).
Examples:
This command requires Node.js and npm to be installed on your system.