Wave Sidekick v2
From Wave Wiki — the open reference for the Wave OS ecosystem.
1. About
Wave Sidekick v2 is a Chrome/Firefox browser extension (Manifest V3) that brings Wave OS intelligence to any webpage. It upgrades v1's side-panel chat with multi-tab enumeration, real page actions (click, fill, scroll on live browser tabs), cross-tab report compilation, and Surf Cloud v2 integration. The floating orb provides instant access to the Wave Assistant from any site. Voice input, TTS, and memory persist from v1.
1a. What's New in v2 (vs v1.3.1)
Multi-tab enumeration via chrome.tabs.query + scripting.executeScript to scan all open tabs. Page actions execute clicks, fill forms, and scroll on real browser tabs from the side panel. Cross-tab report compilation aggregates data across multiple tabs into a single summary. Surf Cloud v2 integration routes complex automation tasks to Surf Cloud's AI-powered headless browser when local page actions aren't enough. Also includes improved Theta API key auto-capture and management, and enhanced Chief of Staff quick actions.
1b. v1.3.1 Features (still included)
Side panel chat with Wave Assistant (Theta EdgeCloud GLM-5.2), voice input via the Web Speech API, text-to-speech responses, conversation memory, Theta API key auto-capture from Wave OS, Chief of Staff quick actions (triage alerts, summaries), and a floating orb on all pages for instant access.
1c. Flows Tab
A new "Flows" tab in the side panel (alongside Assistant, Notes, Wallet, and Edge) lists your Wave Flows pipelines with their status (active/draft) and trigger type. You can run a pipeline directly from the side panel with a live run log, or click "Open in Builder ↗" to edit the full pipeline in Wave OS. Chrome-only for now — the Firefox build doesn't have Flows yet.
2. Tech Stack
Manifest V3 browser extension (Chrome + Firefox compatibility). Side Panel API for the chat interface, with tabs for Assistant, Notes, Wallet, Edge, and (Chrome-only) Flows. chrome.tabs API for multi-tab enumeration. chrome.scripting.executeScript for page actions. Web Speech API for voice input and SpeechSynthesis API for TTS. Backend: waveChat, waveChiefOfStaff, and thetaKeyManager functions on app.oswave.io. AI: Theta EdgeCloud GLM-5.2. Surf Cloud v2 API for headless automation tasks. The Flows tab reads and runs pipelines via Wave OS's Flows integration endpoint. GitHub: xBuildy/wave-mcp-proxy (extension directory).
3. Install
Download the extension package from Wave OS or the GitHub repo. Chrome: navigate to chrome://extensions, enable Developer mode, click "Load unpacked", and select the extension folder. Firefox: navigate to about:debugging, click "Load Temporary Add-on", and select manifest.json. The floating orb appears on all pages after installation — click it to open the side panel chat. Wave OS login auto-detects the Theta API key.
4. Pricing & Credits
Free to install. AI chat requests consume Wave OS credits via Theta EdgeCloud GLM-5.2 inference. Surf Cloud v2 automation tasks consume additional credits based on browser session duration and AI operations performed.
5. Known Limitations
Manifest V3 service workers can be suspended by the browser when idle, which may cause a delayed first response. Multi-tab page actions require host permissions for each tab's domain. Surf Cloud v2 integration requires network connectivity to the Railway container. Firefox compatibility uses browser.* namespace polyfills — some edge cases may differ. Voice input requires browser microphone permission. Not available on mobile browsers. The Flows tab is v1 and Chrome-only: Trigger and AI-type pipeline nodes run correctly from the extension, while other node types (browser actions, logic, etc.) are marked as not-yet-supported in the run log without failing the whole run — more node types are being added.
6. Privacy & Data
All AI processing happens on Theta EdgeCloud, not on local servers. Conversation memory is scoped to the authenticated Wave OS user. Page content is only read when explicitly requested by the user — no passive scraping. Surf Cloud sessions are ephemeral with per-user isolation. No telemetry or analytics are collected by the extension itself. API keys are stored in chrome.storage.local (encrypted at rest on supported platforms).
7. Published
Published: August 13, 2026.