Browser Extension
WarpDL supports browser extension integration through the Native Messaging Host protocol. This allows browser extensions to communicate directly with the WarpDL daemon.
Supported Browsers
Section titled “Supported Browsers”| Browser | Protocol | Status |
|---|---|---|
| Chrome | Native Messaging | Supported |
| Firefox | Native Messaging | Supported |
| Chromium | Native Messaging | Supported |
| Edge | Native Messaging | Supported |
| Brave | Native Messaging | Supported |
Installation
Section titled “Installation”Package Manager Install (Automatic)
Section titled “Package Manager Install (Automatic)”If you installed WarpDL via Homebrew, Scoop, or a Linux package manager (deb/rpm), the native messaging host is configured automatically during installation.
Manual Install
Section titled “Manual Install”For manual installations, run:
warpdl native-host install --autoThis uses default extension IDs. For custom extension IDs:
warpdl native-host install \ --chrome-extension-id "your-chrome-extension-id" \ --firefox-extension-id "your-firefox-extension-id"Single Browser Install
Section titled “Single Browser Install”warpdl native-host install --browser chrome --chrome-extension-id "extension-id"warpdl native-host install --browser firefox --firefox-extension-id "extension-id"Check Status
Section titled “Check Status”warpdl native-host statusThis shows installation status for all supported browsers.
Uninstallation
Section titled “Uninstallation”warpdl native-host uninstallOr for a specific browser:
warpdl native-host uninstall --browser chromeHow It Works
Section titled “How It Works”Browser Extension → Native Messaging → warpdl native-host run → Daemon- Browser extension sends download requests via Native Messaging protocol
- WarpDL’s native host binary receives the message
- Request is forwarded to the WarpDL daemon
- Download proceeds with all WarpDL features (parallel segments, resume, etc.)
Manifest Locations
Section titled “Manifest Locations”The native messaging manifests are installed to browser-specific locations:
Chrome/Chromium/Edge/Brave
Section titled “Chrome/Chromium/Edge/Brave”- macOS:
~/Library/Application Support/Google/Chrome/NativeMessagingHosts/ - Linux:
~/.config/google-chrome/NativeMessagingHosts/ - Windows: Registry +
%LOCALAPPDATA%\Google\Chrome\User Data\NativeMessagingHosts\
Firefox
Section titled “Firefox”- macOS:
~/Library/Application Support/Mozilla/NativeMessagingHosts/ - Linux:
~/.mozilla/native-messaging-hosts/ - Windows: Registry +
%APPDATA%\Mozilla\NativeMessagingHosts\
Troubleshooting
Section titled “Troubleshooting”Extension can’t communicate with WarpDL
Section titled “Extension can’t communicate with WarpDL”-
Check if the daemon is running:
Terminal window warpdl list -
Verify native host installation:
Terminal window warpdl native-host status -
Reinstall native host:
Terminal window warpdl native-host uninstallwarpdl native-host install --auto
Permission Denied
Section titled “Permission Denied”Ensure the WarpDL binary has execute permissions:
chmod +x $(which warpdl)