Skip to content

BridgesLLM Portal 4.0.11

Choose a tag to compare

@Robertmonkey Robertmonkey released this 04 Aug 01:59

This release also carries 4.0.9 and 4.0.10. Those two shipped to
bridgesllm.ai but were not mirrored to this repository at the time, so there
is no v4.0.9 or v4.0.10 tag here — the source for both landed in the
commit this tag points at. v4.0.4 has the same gap. Every version's notes
are in CHANGELOG.md.
No tag was backfilled, because no commit in this repository holds those
trees and a tag that did not build the release it names is worse than a gap.


Added

  • Ask Questions now works through every embedded provider, not only native Codex. When an agent needs a decision in the middle of a run it can raise a clarification card in Project Chat whatever model is driving that run. Project Chat admits the single named clarification tool without exposing the rest of the plugin surface, and every question stays bound to the authenticated user, session, run, and tool call. A provider that reuses a tool-call ID across overlapping runs fails closed rather than letting one run consume another run's answer, and a question already answered in another browser reconciles quietly instead of surfacing a generic failure.
  • Files an Agent links to now open somewhere useful. Links to Portal-managed uploads navigate to Files and select the exact file. Links to real files in that Agent's own workspace, or in a Project generation, are copied into a private bounded Remote Desktop handoff, opened in the appropriate desktop viewer, and the Portal switches to Remote Desktop to show them. Traversal, symlinks, authority changes, oversized files, and cross-Agent or cross-Project paths all fail closed, and each handoff copy expires on a managed lifetime.

Changed

  • The workspace refresh screen now belongs to the Portal. The opaque privacy curtain uses the installation's uploaded logo as a desaturated translucent mark, layers a restrained radial dot matrix and a slow light sweep over Portal colors, and presents status in a glass pill. It scales down to mobile, degrades cleanly when no logo has been uploaded, and becomes static under reduced-motion preferences. Its first frame is fully opaque, so the workspace behind it is never briefly legible.

Fixed

  • Agent Chat recovers when a provider stream drops. The visible amber reconnect control now exercises the same real socket-recovery path the tests cover, a manual refresh reloads history and reconnects, and a run that finishes while the browser is offline leaves an authoritative terminal snapshot so the yellow rail clears without a hard page reload.
  • Agent Chat shows the right sessions and an honest account of what a run is doing. Provider and agent sessions are restored on return instead of collapsing into another agent's history, live activity reflects the actual state of a turn rather than an optimistic guess, a final reply split across several frames is reassembled instead of being truncated, a stale replay from an earlier run is fenced off rather than replacing current output, and a gap in the runtime event sequence quarantines that stream instead of rendering a silently incomplete conversation.
  • Codex sign-in finishes cleanly and no longer puts an existing login at risk. The OAuth wizard completes finalization instead of stalling at the last step, credentials are attested before they are committed so a partial or malformed grant cannot be written, and a setup attempt that does not complete leaves any Codex login already on the box untouched.
  • OpenClaw state backups are smaller and internally consistent under live use. Reproducible Codex sessions, caches, shell snapshots, operational state databases, and logs no longer churn the recovery archive, while Codex configuration, memories, and goals remain included. The live OpenClaw SQLite database is captured through SQLite's online backup API, so committed write-ahead data lands in one standalone database at the original restore path; stale outbound delivery rows are removed so a restore cannot replay them, and linked, replaced, or otherwise unsafe WAL, SHM, and journal sidecars are refused.

Security

  • Dependency advisories are patched on the shipped backend and frontend graphs. Undici, ip-address, PostCSS, socket.io-parser, and brace-expansion are updated to fixed releases. The remaining React Router advisory is limited to React Server Components, which this client-only Vite build neither imports nor bundles and which the release gate proves unreachable.