BridgesLLM Portal 4.0.8

Portal 4.0.8 is a hotfix release.

Fixed

• A new project can start Project Chat again. The panel claimed its 15-minute automatic-qualification backoff before sending the qualification request, and a first qualification on a new project takes far longer than a person will wait. Reloading or switching projects during that window left the backoff behind for an attempt that never returned a verdict, so the project came back permanently unqualified with no retry and no failure to explain it. Only a real qualification failure records a backoff now.
• Stop actually stops an Agent Chat run. The abort route treated any response that was not an explicit refusal as a successful cancellation, so a missing or unexpected payload cleared the composer while the run kept going. Portal now requires a confirmed abort, reports which runs were cancelled, and says the run may still be active instead of reporting a cancellation that did not happen.
• Opening Agent Chat session settings no longer mutates or interrupts the active session. The settings panel now reads canonical OpenClaw metadata without silently patching thinking or reasoning defaults, avoids an unrelated command-catalog request, and stays disabled while a turn or model transition owns the session.
• Portal-created OpenClaw chats have recognizable names. New Portal sessions receive a stable agent label and the first prompt upgrades it to a concise conversation title. Naming now also covers sessions Portal's own records show you own, which previously displayed Portal's internal gateway client identity instead of a title and made conversations impossible to tell apart. Existing chats created outside Portal keep their own labels, and chats that already exist are not renamed retroactively.
• One chat action creates one session. Selecting or reconnecting to an existing new-* OpenClaw chat no longer triggers a second background session-create call after the explicit creation path already completed.
• Expired idle tabs stop hammering the server. A failed refresh now clears falsely persisted login state, including the browser-only WebSocket-upgrade 1006 case, and gateway question polling backs off to 30 seconds during restart windows.
• New Project Chat waits for verified OpenClaw model readiness. The browser no longer asks for an embedded model catalog before automatic provider qualification completes, and a transient empty catalog cannot poison the server cache.
• Legacy projects can enter Project Chat without unsafe in-place promotion. Portal makes a manifest-verified copy under a new Portal 4 identity, proves the copy remained stable, and leaves the legacy inode, older agent state, shares, apps, and deployment untouched.
• Project deletion recovers cleanly after an OpenClaw runtime was prepared. A first Project agent can no longer capture default routing on a fresh installation, and Portal removes a large sandbox policy in verified stages so OpenClaw's config-size guard cannot strand the project in DELETING.
• Backups run again on a PostgreSQL server that is behind on patches. The backup runner applied its client security floor to the database server as well, so a supported server one patch release below that floor was refused outright and no backup could be taken at all. The floor now governs the client toolchain that Portal runs, while any supported server major is still backed up — the archive is the prerequisite for safely patching the server, so refusing it left an installation with neither. Portal also omits only OpenClaw's reproducible managed npm runtime, retries bounded live-state capture races, and preserves durable sessions, config, and extensions.
• Native provider sign-in is no longer blocked by its own credential attestation. A symlink inside an attested directory is recorded by its target instead of refused, so a provider CLI that rewrites a log file on every run can still sign in. An attested path that is itself a symlink still fails closed.
• A failed xAI sign-in no longer locks the provider until the Portal restarts. The operation gate expires, and Cancel waits for the login process to exit before judging the credential instead of failing with a conflict and leaving the gate held.
• A successful sign-in is reported as connected. Authorization profiles that OpenClaw keeps in its own auth store now count as provider configuration, instead of being reported as credentials with a missing provider config.
• Provider setup failures name the cause. A missing CLI says which tool to install and how to install it; an unreadable credential file says which path to check.
• App pages that load from a directory URL open again. The App API proxy treats a trailing slash as a legitimate upstream path rather than an empty segment, so a request like /api/<app>/app/ reaches the app instead of failing with a misleading "App API backend is not configured". Traversal, backslash, null-byte, and internal empty-segment rejection are unchanged, and a doubled trailing slash is still refused rather than silently collapsed into a different path.

Install or update: https://bridgesllm.ai/install.sh