Repository navigation
fleet serve: built-in supervised local proxy endpoints — replaces sandbox proxy-supervisor (docs migration stay-item R3) #5974
Description
Part of the docs migration (hatch-personal/hatch → code). Stay-until-replaced register item R3.
What exists today
hatch-personal tools/proxy-supervisor/ (proxy-supervise.mjs, proxy-relay.mjs, proxy-port.mjs, config.json) plus proxy-supervisor.service, proxy-supervisor.timer, and install-proxy-supervisor-service.sh supervise local proxy endpoints that non-fleet tools dial. The supervisor is currently dormant (its config proxy list is empty) but is still installed and service-checked on every boot.
What the built-in must do
fleet serve provides built-in supervised local proxy endpoints: declared endpoints with health checks, drain semantics (config carries drainSeconds / healthTimeoutSeconds today), and state under the fleet state dir — so ad-hoc tools get a stable local proxy without a separate supervisor service living in the sandbox home repo.
Exit condition
When this ships (or when a deliberate decision records that the dormant supervisor is retired rather than replaced), the 7 hatch files above become historical copies only.
Activity
developing-today commentedon Nov 5, 2026
CODE-1640
dezren39 commentedon Nov 5, 2026
Drew's review + outcome — 2026-11-05 00:05 CST
Drew's recollection, confirmed against the tree: proxy-supervisor was built to fix a problem and then never used. What it is: a small supervisor (
~/tools/proxy-supervisor/proxy-supervise.mjs) that health-gated the standalone provider proxy relays (muse / agy / commandcode / claude-code / codex). Every relay was removed from its config on 2026-10-25, so it has managed zero proxies since. Fleet direction per Drew: the standalone proxies are being removed and baked into the fork, so the supervisor has no future role.Two checks/actions from his review:
~/tools/in the dezren39/hatch repo:tools/proxy-supervisor/{proxy-supervise.mjs, proxy-relay.mjs, proxy-port.mjs, config.json},tools/proxy-supervisor.{service,timer},tools/install-proxy-supervisor-service.sh— all tracked, working tree clean, HEAD == origin/main (nothing unpushed). Last change: 9cc630ac2 "sandbox: disable remaining provider relays + proxy-supervisor (Drew 2026-10-25 20:52)". No uncommitted proxy-supervisor work exists. (One stray: an ignored.bak-20261025221719-hardeningcopy of the installer sits beside it — a backup of the committed file, nothing unique.)proxy-supervisor-servicestep in~/tools/init.sh, already commented out since 2026-10-25 (the units are not installed or active in the current boot —systemctlreports them not-found). Per Drew's "stop checking for it on every boot," the dead block is now removed from init.sh entirely, leaving a 3-line tombstone pointing here: commit ca2c32864 in dezren39/hatch, pushed to main ("sandbox: remove proxy-supervisor from boot machinery entirely (Drew 2026-11-05) — code#5974", tools/init.sh −4/+3,bash -nclean). A sweep of the rest of the boot path (init-ensure.sh, verify-services.sh, current cron definitions, the boot goal workspace) found no other proxy-supervisor check. The dormant code stays in-tree as history; nothing at boot installs, enables, or verifies it.dezren39 commentedon Nov 5, 2026
🤖 Agent note · handed off