1.9 KiB
Desktop Vertical
Status: draft | Updated 2026-07-11 | Applies to: AMPB desktop builders
The first AMPB browser proof is desktop-first with mobile constraints kept in view. The
vertical is a bundled Gecko desktop runtime, AMPB-owned profile state, and a managed Tor
runtime for .onion browsing. Android and iOS follow the same routing and transport
contracts after the desktop path is proven.
Build Path
Use the external build workspace:
sh tools/browser-build-workspace.sh
sh tools/browser-source-sync.sh
AMPB_DESKTOP_BUILD_PROBE_MODE=build sh tools/browser-desktop-build-probe.sh
The desktop probe keeps Gecko source, object files, downloaded toolchains, Python
virtualenvs, pip cache, and logs under /tmp/ampb-browser-build.
The default build flavor is the verified source build. Use
AMPB_DESKTOP_BUILD_FLAVOR=artifact only as a faster optional probe when upstream
artifacts are available for the selected checkout.
Transport Path
The first transport target is Tor through an AMPB-owned Arti/Tor runtime. The current desktop vertical can launch a bundled Gecko runtime, start the isolated transport broker, and keep its token-gated helper tied to the broker process. Tor and I2P destinations launch in their own browser profiles after route validation and consent. Reticulum follows after the resilient-network adapter and renderer handoff are concrete.
Desktop Shell
ampbrowser shell <url> is the first desktop shell bridge. It prepares the same open plan
as ampbrowser open, renders first-use transport consent as a desktop dialog when a
prompt is required, and then launches the bundled browser through the shared runner after
approval. Use --yes for scripted verification without showing the dialog.
python3 -m ampbrowser shell http://example.onion/
python3 -m ampbrowser shell http://example.onion/ --yes
python3 -m ampbrowser shell https://ampgateway.site/ --broker