BridgesLLM Portal 4.0.5
This release also carries 4.0.4. 4.0.4 shipped to bridgesllm.ai but was
never mirrored here, so there is nov4.0.4tag — its source landed in the
commit this tag points at. Its notes are in
CHANGELOG.md.
No tag was backfilled, because no commit in this repository holds that tree
and a tag that did not build the release it names is worse than a gap.
Hotfix. If your Portal update failed with "The existing OpenClaw gateway is not stably ready in the standard state layout", this release fixes it. Update from the Dashboard as usual.
The problem
Before replacing the pinned OpenClaw core package, the installer proves the running gateway is healthy so it has a rollback baseline to return to. It sampled that state instantly.
The Portal, however, restarts the gateway from its own startup path when it reconciles visible-browser agent defaults — and the installer reaches this step within seconds of restarting the Portal. On any host with Remote Desktop or a visible-browser agent configured, the gateway was reliably mid-restart at exactly the moment it was measured.
The result: a completely healthy machine was reported as unsafe, and the update failed after the Portal had already been upgraded. The Dashboard then offered the same update again.
The fix
The installer now waits for the gateway unit to settle before sampling it, and retries the baseline probe rather than condemning the host on a single miss. A gateway that has genuinely failed is still refused immediately, and one that never stabilises still fails closed — the rollback guarantee is unchanged.
Verified end-to-end on a test box by restarting the gateway at the exact instant the installer reached this step: the update completed, and OpenClaw converged normally.
Upgrading
Portals on 4.0.0 through 4.0.4 can update straight to 4.0.5 from the Dashboard. The updater fetches its installer from the release it is moving to, so no manual step is required.
Full changelog: https://github.com/BridgesLLM-ai/portal/blob/main/CHANGELOG.md