Prefer Arti for managed Tor browser setup

This commit is contained in:
jwinterm
2026-07-07 16:14:32 -04:00
parent cd60935f95
commit f0ffc039d1
9 changed files with 75 additions and 19 deletions
+3 -3
View File
@@ -1,6 +1,6 @@
# Transport Management
> Status: draft | Updated 2026-07-05 | Applies to: AMPB transport adapters
> Status: draft | Updated 2026-07-07 | Applies to: AMPB transport adapters
Transport management follows one rule: use what is already healthy, and manage missing
transports only after the user opens a URL that needs them and approves setup.
@@ -15,7 +15,7 @@ Transport policy comes from `.ampb/config.toml` or an explicit `--config` path.
2. Adopt running transports that match the selected URL.
3. For missing transports, show a prompt that names what will be installed or started.
4. Resolve a configured binary and state directory only after consent.
5. Start the daemon with AMPB-owned state.
5. Start the daemon, library runtime, or foreground service with AMPB-owned state.
6. Wait for the health endpoint.
7. Launch the browser profile only after the transport is ready.
8. Stop only AMPB-owned daemons.
@@ -30,7 +30,7 @@ leases, tunnels, and daemon logs in that tree are local state and must not be co
## Current Adapters
- Tor: detect SOCKS on `127.0.0.1:9050`; managed start planned.
- Tor: detect SOCKS on `127.0.0.1:9050`; managed setup prefers Arti/Tor runtime ownership.
- I2P: detect HTTP proxy on `127.0.0.1:4444`; managed start planned.
- IPFS: detect HTTP gateway on `127.0.0.1:8080`; managed gateway start planned.
- Gemini: built-in route and render path; no daemon required for static browsing.