Adaptive Multi-Protocol Browser, or AMPB, is a transport-aware browser shell. It routes URLs to the right network, adopts transports that are already healthy, and manages missing transports when configured to do so.

AMPB is Firefox-first for normal web browsing. The initial product should control a hardened Firefox runtime, transport-specific profiles, and AMPB-owned transport setup before graduating into a deeper Firefox or Tor Browser fork.

The first fixture is Wownero across clearnet, Tor, I2P, Gemini, and Reticulum-oriented targets generated by AMPG. Interactive fixtures include ai-gen-bot and the Medusa multi-tenant platform.

Goals

Route URLs by protocol and address family.
Adopt existing Tor, I2P, Reticulum, and Gemini-capable tools when healthy.
Prompt on first visit before installing or starting a missing transport.
Manage approved transports through isolated AMPB state.
Keep browser profiles isolated by transport.
Present transport health in plain language.

Non-goals

Forking a browser engine before the orchestration model is proven.
Mixing clearnet, Tor, I2P, and Reticulum cookies/storage in one profile.
Publishing private transport state, keys, or host inventory in public docs.

Local Commands

python3 -m ampbrowser route https://wownero.org/
python3 -m ampbrowser route http://example.b32.i2p/
python3 -m ampbrowser route gemini://wownero.org/
python3 -m ampbrowser route ipfs://bafyexample/
python3 -m ampbrowser inspect
python3 -m ampbrowser plan gemini://wownero.org/
python3 -m ampbrowser open https://wownero.org/
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 fixture check ../adaptive-multi-protocol-gateway/dist/wownero/ampg-fixture-manifest.json
python3 -m ampbrowser docs generate
python3 -m ampbrowser docs generate --check
python3 tools/docs_check.py
python3 -m unittest discover -s tests

Documentation

Reusable checklist

Route URL to transport.
Inspect whether transport can be adopted.
Prompt before installing or starting a missing transport.
Use isolated profile state for each transport.
Spawn/manage only after a dry-run plan.
Keep private notes under docs/private/.