> For the complete documentation index, see [llms.txt](https://docs.bluerock.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluerock.io/release-notes/bluerock-2.6.2-26.23.2.md). # BlueRock 2.6.2 (26.23.2) ### Purpose of this Document This document provides information about the features, enhancements, and known issues in BlueRock Release 2.6.2 (26.23.2). It applies to both new deployments and upgrades from earlier versions. This release introduces the new telemetry forwarder, comprehensive Platform as a Service (PaaS) gateway support for the desktop connector, and robust connection recovery mechanisms across all client applications. *** ### Revision History | **Release Version** | **Release Date** | | ------------------- | ---------------- | | v26.23.2 (2.6.2) | | *** ## Supported Platforms / Distributions BlueRock Release 26.23.2 (2.6.2) supports deployment across major public cloud providers. The following operating systems have been validated for this release. ### AWS | **Distribution** | **Kernel** | | ----------------------------------- | ---------- | | Amazon Linux 2023 | 6.12.89 | | Amazon Linux 2023 (Kubernetes 1.34) | 6.12.89 | ### GCP | **Distribution** | **Kernel** | | ---------------- | ---------- | | Ubuntu 24.04 | 6.12.89 | ### Azure | **Distribution** | **Kernel** | | ---------------- | ---------- | | Ubuntu 24.04 | 6.12.89 | *** ## New Features and Enhancements This release introduces the new `blueotel` telemetry forwarder, comprehensive Platform as a Service (PaaS) gateway support for the desktop connector, and robust connection recovery mechanisms across all client applications. ### BlueRock Connector Application (for Claude and Codex Desktop IDEs) * **PaaS Gateway Support**: * **PaaS Gateway Access**: \ The BlueRock Connector now supports connection to remote BlueDev Sandbox container running on BlueRock PaaS via Gateway. * **Remote Onboarding**: \ The BlueRock Connector supports enrollment using the single sign-on (SSO) URL provided by the PaaS console and automatically discovers the target host to launch the remote sandbox. * **Workspace Selection**: \ The application menu bar features a new workspace picker tailored for PaaS environments. * **Connection Recovery**: \ The BlueRock Connector application automatically restores dropped connections to the remote sandbox container as soon as the system resumes from hibernation or the network interface reconnects. * **Startup Configuration:** \ The BlueRock Connector desktop application now provides configuration to automatically start the application on system startup. * **Support Diagnostics**: \ Users can export structured, owner-readable logs directly from the system tray. The export process automatically masks sensitive credential values. * **Catalog Template Consolidation:** \ The release consolidates the catalog to two BlueRock sandbox container templates: `coral-console` and `ubuntu` (the default template for deployments).

Important:

BlueRock version 2.6.2 lacks backward compatibility. BlueRock sandbox containers deployed via the BlueRock Connector Application require BlueRock cloud instances running 2.6.2 cloud images, and vice versa.

*** ### BlueRock Connector Extensions (for VS Code and Cursor) * **Network Resilience:** \ The extension comprehensively handles wireless network drops. The application suspends credential renewals during network outages and automatically reconnects attach sessions when the network interface is active again. * **Environment Parity**: \ The attach mechanism now fully supports editors running on a shared system Electron, enabling full compatibility with the Cursor editor. * **Container Visibility**: \ The user interface automatically displays the Containers tab when active containers exist and prompts the user for sandbox selection when initiating actions. *** ### Forwarding Native OTLP Events to External Collector * **Event Forwarding**: \ When AI coding agents run inside the remote sandbox container, the platform forwards native OpenTelemetry Protocol (OTLP) events from the AI agent session to the external collector alongside the BlueRock Sensor OTLP events. * **Supported Agents**: \ Native OTLP event forwarding is supported for Claude, Codex, and Gemini code agents. *** ### **Package Path Update** Installation packages and tar files are now deployed exclusively to the `~/bru_packages/bluedev` directory. *** ## Fixed Issues ### BA-2927 SSH connection failure on macOS Monterey SSH connections to BlueRock hosts using the Bluedev VSCode Extension or the Cobalt application may fail on **macOS Monterey** because of domain socket path length limitations. *** ## Known Issues ### BC-3371 Restarting bluerockd disrupts existing sensor connections Restarting the BlueRock Control Plane service disconnects existing BlueRock sensor connections, interrupting active AI agent and MCP applications. **Workaround** Restart all affected AI agent and MCP applications after restarting the `bluerockd` service. *** ### BC-3381 Source-address ingress firewall rules not enforced Source-address-based ingress firewall rules are not correctly enforced for BlueRock Sandbox containers. **Workaround** No workaround is currently available. *** ### CP-1333 Tooltip overlaps page content and renders outside the visible window On the Home page, tooltips for alert or trigger data in the Flagged Alerts section expand over the underlying UI and extend beyond the visible viewport when they contain a large amount of data. **Workaround** No workaround is currently available. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bluerock.io/release-notes/bluerock-2.6.2-26.23.2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.