Open-source browser wallet, side panel, and page-context layer for WhiteOwl
Manifest V3 companion extension that runs next to the main WhiteOwl panel and brings wallet flows, provider bridge, inspector, token context, and browser-native controls directly into Chromium.
Install • Highlights • Companion Stack • Screenshots • Development • Releases
Open preview video • Latest release • Main WhiteOwl panel
| Surface | What it does |
|---|---|
| Browser Wallet | Local wallet flows, connected-site state, approvals, and signing surfaces inside Chromium |
| Token Launcher | One-click token deployment to pump.fun with metadata, social links, and advanced launch modes (Mayhem, Tokenized agent, Cashback) |
| Twitter Scanner | Automatic detection and scanning of Solana contract addresses (CA) directly from Twitter/X posts with one-click analysis |
| Side Panel | WhiteOwl chat, token context, quick actions, settings, and operator controls next to the page |
| Page Context | Inspector and capture tools that move structured browser context back into the WhiteOwl desk |
| Panel Bridge | Local integration with the main WhiteOwl runtime for chat, token enrichment, image scanning, and wallet-related flows |
This repository is intended to be the standalone split of the extension layer that works next to the main WhiteOwl panel/backend. It contains the Chrome Manifest V3 extension, side panel UI, provider bridge, wallet flows, token context overlays, page inspection tools, and local integration points for the WhiteOwl runtime.
WhiteOwl is split into two repositories that are designed to run together:
- Main panel and backend:
https://github.com/whiteowl-engine/WhiteOwl - Browser wallet and side panel extension:
https://github.com/whiteowl-engine/WhiteOwl-Extension
The main WhiteOwl repo is the dashboard, local backend runtime, AI agent layer, automation surface, market data plane, and chat server. This extension repo is the in-browser wallet, provider bridge, site connection layer, inspector, and page-aware side panel. Together they form the full WhiteOwl operator workflow.
WhiteOwl Extension is the browser-native half of the WhiteOwl stack. It takes the runtime, models, and backend services exposed by the main panel and puts the wallet, provider bridge, page inspector, and side panel directly next to the site you are operating on.
The result is a local-first workflow where WhiteOwl can combine panel-side intelligence with real browser context, connected-site state, and in-page actions without turning the extension into a separate hosted product.
- Start the main WhiteOwl panel/backend from
https://github.com/whiteowl-engine/WhiteOwl. - Download the latest packaged build from
https://github.com/whiteowl-engine/WhiteOwl-Extension/releases/latestor clone this repository for unpacked installation. - Open
chrome://extensions, enable Developer mode, then load the unpacked repository or extracted release archive. - Keep the default server target
http://localhost:3377or pointwo_server_urlto your running WhiteOwl panel. - Pin the extension, open the side panel, and use the wallet, chat, inspector and page-aware WhiteOwl flows directly in the browser.
- Manifest V3 browser extension for Chrome and Chromium-based browsers
- Side panel UI for token analysis, chat, inspector, and wallet flows
- Provider bridge injected into supported Solana and trading surfaces
- Site approval and connection management logic
- Page data inspection and safety/scanner flows
- Local-first wallet and keystore logic stored in extension storage
- The main WhiteOwl panel/backend application
- Backend API implementation
- Hosted infrastructure or cloud deployment config
- A packaged Web Store release artifact
By default the extension expects a WhiteOwl panel/backend at http://localhost:3377. The backend URL can be changed through extension storage by setting wo_server_url.
manifest.json- extension manifest and permissionsbackground.js- background service worker, message relay, backend bridgecontent.js- page overlays, page analysis, scanner and capture logicprovider.js- injected wallet/provider bridge for supported sitessidepanel.html- side panel markupsidepanel.css- side panel stylessidepanel.js- side panel application logic and wallet UI flowsi18n-ext.js- runtime translation helper_locales/en/messages.json- English store metadata stringslightweight-charts.js- bundled third-party chart library with preserved license headerscripts/validate.mjs- repository hygiene and syntax validator
- Twitter Contract Scanner - Automatic detection of Solana contract addresses (CA) in Twitter/X posts with one-click "Scan CA" button for instant token analysis, security checks, and market data
- Token Launch Console - One-click token deployment to pump.fun directly from browser with advanced launch modes:
- Mayhem mode - Route fees to reserved recipients for higher price-action velocity
- Tokenized agent - Attach fee-sharing config for automated buyback
- Cash back - Enable on-chain cashback flag for creator reward redistribution
- Token context side panel for live market and page-aware analysis
- WhiteOwl chat entry point inside the browser side panel
- Page inspector for capturing structured on-page context into the panel
- Local wallet flows for PIN, keystore, signing, import and recovery
- dApp/provider bridge for supported Solana surfaces
- Safety-oriented site connection review and page scanning
- Local bridge to the WhiteOwl panel for token, image, scanner and wallet actions
- Chrome or another Chromium browser with Manifest V3 support
- Node.js 20 or newer for validation scripts
- WhiteOwl panel/backend running locally or reachable through a configured backend URL
- Open
chrome://extensions. - Enable Developer mode.
- Select Load unpacked.
- Choose this repository root.
- Pin the extension and open the side panel.
Run the repository validation before publishing or tagging:
npm run checkThe validator checks:
- JavaScript syntax for the extension entry files
- Presence of Cyrillic characters across tracked text files
- Comment markers in extension source files
The bundled lightweight-charts.js file is intentionally excluded from the comment check because its Apache 2.0 license header must remain intact.
Tagged versions publish a packaged browser-extension archive into GitHub Releases.
- Releases page:
https://github.com/whiteowl-engine/WhiteOwl-Extension/releases - Release asset format:
whiteowl-extension-v<version>.zip - Packaging command:
npm run package:release
The release archive is built from the runtime extension files only, so it can be downloaded and loaded directly as an unpacked extension after extraction.
This repository also publishes the source package to GitHub Packages.
- Package name:
@whiteowl-engine/extension - Registry:
https://npm.pkg.github.com
Preview the publish payload locally:
npm run package:previewThe extension is not a fully isolated product. It is a companion layer for the WhiteOwl panel.
- Default API target:
http://localhost:3377 - Local override key:
chrome.storage.local.wo_server_url - Expected backend responsibilities include token enrichment, image scanning, panel chat/runtime integration, and selected wallet-related server endpoints
If the backend is offline, the extension UI still loads, but features that depend on the panel runtime will degrade or stay unavailable.
activeTab- current page interactions initiated by the usersidePanel- browser side panel UIstorage- local extension state, approvals, keystore and settingstabs- tab messaging and active page coordinationwebRequest- request inspection or compatibility logic used by the extension runtimecookies- site/session interoperability where required by the extension flowsalarms- background timing and retry flows
The extension also injects content scripts and provider logic into the trading, wallet and social domains listed in manifest.json.
- This repository includes wallet-related code and local signing flows.
- The codebase should be reviewed carefully before using it with real funds.
- Keep the backend local unless you explicitly trust the configured WhiteOwl server.
- Review
SECURITY.mdbefore publishing production builds.
- The extension stores operational state locally in extension storage.
- Data collection and provider-side activation are consent-gated in the UI.
- Review
PRIVACY.mdfor a concrete breakdown of storage and network behavior.
This repository currently vendors TradingView Lightweight Charts in lightweight-charts.js.
- License: Apache License 2.0
- Notice file:
THIRD_PARTY_NOTICES.md







