WhiteOwl emblem
WHITEOWL Autonomous Solana Trading Shell
Runtime SkillHub Open Dashboard

SETUP

Start from the shell you already have, then wire the layers that matter.

WhiteOwl is designed for local-first operation. Installation, provider routing, wallet risk, and runtime mode selection are separate steps so the operator can harden each one deliberately.

Open Dashboard Extension Stack
Boot sequence

Install, connect models, define wallet walls, then pick the operating mode.

  • API server defaults to port 3377
  • OAuth and API-key providers can coexist
  • Risk limits remain operator-defined and non-negotiable

BOOT FLOW

Move through install, auth, wallet, and runtime mode without mixing concerns.

Boot the shell locally

git clone https://github.com/yourname/WhiteOwl.git
cd WhiteOwl
npm install
npx tsx src/index.ts server

The API and dashboard default to port 3377. Keep the runtime local and use the dashboard as the control plane.

CHECKLIST

Four checks before the shell is trusted with real flow.

01

Provider redundancy

At least one fast model, one strategic model path, and a fallback route should be configured before sessions go live.

02

Wallet boundaries

RPC, signing material, and position caps need to be aligned with the actual risk budget of the operator.

03

Surface readiness

Dashboard, extension, and alert channels should be reachable before autonomous flow is allowed to continue unsupervised.

MODEL ACCESS

Use what you already trust.

WhiteOwl can route across OAuth-backed and API-key-backed providers without changing the operator surface.

READY

Once setup is complete, the dashboard becomes the live control plane and the rest of the surfaces plug into it.

Use the runtime page for deeper system logic and the extension page for the browser-side wallet and inspection stack.

Open Dashboard Inspect Runtime