You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One-click update on a prefix install wrote the new binary where nothing executes it. The update endpoint hardcoded OMNIPROXY_LAYOUT=repo, the layout of the launchd dev box. On a prefix install (systemd user unit, ~/.omniproxy-user) update.sh therefore placed the new binary at ~/.omniproxy-user/omniproxy and the new web/ at ~/.omniproxy-user/web — one level above the bin/ subtree the service actually runs — then restarted the service, which came up on the untouched old binary. Nothing announced the failure: the dashboard reported success, /health kept the old version, and update.state stayed running:true because the wrapper that records the exit code died with the old process. The endpoint now derives the layout from where the running binary lives (installed web/ or scripts/ beside it with version.json one level up → prefix; version.json beside it → repo), and unit tests pin all three shapes.