Standalone Mode

The original engine in bundler/ — plain Python, runs on your machine, independent of the web app. This is the advanced path; the browser engine covers the same pipeline with a UI.

What it is

• pons_terminal.py — the CLI: token 0x… to track, auto for progressive buys, holders for the sniper table, sell / dump / dumpnow for exits, approve to stage sell approvals
• plan_funding.py / fund_execute.py — the relay.link distribution: plan, then autonomous journaled execution
• wallets.py — vault generation and address export
• server.py — optional: the same engine behind a local JSON API on 127.0.0.1:8787 (see the Local API reference), serving the frontend with live controls

What works for real

Everything the browser engine does, with the same discipline: the 24-word phrase shown once, the encrypted vault, Poisson-spaced funding with randomized amounts, the gated launchAndBuy, marginal-rate dump math. State lives in bundler/out/ and the CLI and server share it — start a plan in one, watch it in the other.

When to pick it

• You want shell access, scripting, or your own automation around the pipeline.
• You prefer a long-running process over keeping a browser tab open through the funding window.
• You are auditing the engine — the Python is the reference implementation the browser modules were ported from.

Design rule

Standalone never phones home. Keys stay in out/vault.json, signing happens in the process, and every mutating command requires the vault unlocked plus an explicit execute flag. The server binds localhost only — do not expose the port.