Open Flow

Status: draft | Updated 2026-07-05 | Applies to: AMPB users and implementers

ampbrowser open prepares a safe launch plan for one URL. It routes the URL, checks only the selected transport, and reports whether the browser can open immediately or needs a first-use setup prompt.

AMPB does not install or start Tor, I2P, IPFS, Reticulum, or other optional transports when the application starts. Setup is lazy:

The user opens a URL.
AMPB selects the required transport.
If the transport is already running, AMPB adopts it.
If the transport is missing, AMPB shows a prompt naming what will be installed or started.
AMPB proceeds only after approval.

By default, open output is a dry-run launch spec. Use --launch to create the isolated profile and launch the configured browser runtime when the selected route is already ready. Transport install/start remains gated by first-use approval and readiness checks.

Examples

python3 -m ampbrowser open https://wownero.org/
python3 -m ampbrowser open http://example.b32.i2p/
python3 -m ampbrowser open http://example.b32.i2p/ --yes
python3 -m ampbrowser open http://example.b32.i2p/ --config examples/config.toml
python3 -m ampbrowser open http://example.b32.i2p/ --platform android
python3 -m ampbrowser open https://wownero.org/ --launch

1.3 KiB Raw Blame History

Open Flow

Consent Model

Examples

1.3 KiB

Raw Blame History