Engine Mode

The app at full power — server.py running locally, ● engine live in the sidebar.

What unlocks

• Setup pipeline — seed generation, wallet derivation, balance checks, plan + execute
• Vault wallets — the Wallets view lists every bundle wallet with live balances and per-wallet sell
• Funder — relay.link plan/execute controls
• Launch — launchAndBuy from vault wallet 0 with bundle snipe-tax exemptions
• Bot controls — auto-buy, stop, emergency dump, per-wallet exits
• Activity — the engine's own log stream rendered live

Detection

assets/js/engine.js probes GET /api/state on load. A response within ~1.2s means engine mode; anything else and the app stays standalone. No configuration, no flags.

Session flow

Engine mode still starts at the wallet gate — your connected wallet is your identity for browsing and solo trades. The vault password is only asked when a signing operation needs it (ensureUnlocked), not at page load.

Everything writes through the API

The UI never signs bundle transactions itself — it calls /api/* and the engine decides whether to simulate or execute. That is why the pipeline gates are real: /api/launch checks plan completion server-side no matter what the page thinks.