Choose the interface that matches the moment, not a fixed workflow.
- Dashboard for full control plane and diagnostics
- Extension for page-native actions and wallet review
- Telegram and API for remote command and automation
SURFACES
Every control layer speaks the same runtime, but each serves a different operating tempo.
WhiteOwl is not tied to a single app shell. The dashboard, browser extension, Telegram channel, and API layer all expose different entry points into the same underlying decision engine.
ENTRY POINTS
Four operator surfaces, one runtime contract.
Full control plane for sessions, positions, diagnostics, analytics, and live state.
Use the dashboard when the operator needs breadth: streams, health checks, portfolio posture, charts, controls, and persistent oversight.
Field surface inside the browser
Stay on the feed or dApp while token context, inspection, and wallet actions happen next to the page itself.
Remote command and alert channel
Use it when the operator is away from the main shell but still needs status, alerts, and intervention paths.
Programmatic orchestration and event streams
Health routes, token queries, chat endpoints, metrics, and WebSocket events for custom clients and automation layers.
OPERATING MODES
Each surface is tuned for a different time pressure.
Deep oversight
Dashboard mode is for long sessions: health, metrics, active positions, strategy posture, and portfolio review.
Page-native action
Extension mode is for fast browsing contexts where token review, wallet safety, and on-page decisions need to stay near the source.
Remote command
Telegram and the API are for alerts, delegated workflows, and headless orchestration when the operator is not inside the dashboard.
SHARED CONTRACT
The interfaces differ. The underlying data contract does not.
WebSocket streams keep all clients anchored to the same runtime state.
Positions, alerts, health changes, and execution updates can be pushed to any surface that is listening.
Runtime posture should not depend on which client happened to issue the request.
Risk walls, strategy thresholds, and execution routes stay centralized even when the operator moves between interfaces.
What starts in one surface can continue in another without losing the problem state.
The extension can feed the runtime, the dashboard can oversee it, and alerts can escape to Telegram or API listeners.
NEXT
The extension is the fastest field surface in the stack.
Open the extension page for token intake, Signal Chat, Inspector, Wallet OS, guardian flow, vaults, and private send.