May 2026
Bluebricks Release Notes
Sharper agent context, alert-driven threads
This release brings quote-reply and paste-to-quote to the agent, introduces Coralogix-powered alert threads, and ships a batch of agent and UI fixes.
🚀 New features
Quote-reply chips and paste-to-quote in the agent
Two new ways to attach context to an agent message. Select text on the page to get a "Reply" tooltip, or paste long or multiline content and it auto-wraps as a quote chip. The quoted text is sent with your message so the agent knows exactly what you're referencing.
What does it mean for you? You can point the agent at the precise text you want it to consider, without copy-pasting paragraphs into the prompt. Answers stay grounded in what you actually meant.
View thread button on user messages
Each user message now has a "View thread" button that takes you back to the original conversation context.
What does it mean for you? Jumping between message references and full threads is a single click. Easier to pick up a paused conversation or trace where a question came from.
Coralogix integration setup flow
We added a new integration that turns Coralogix alerts into agent threads. The setup flow walks you through connecting a Coralogix workspace, including region, credentials, validation, and edit-after-the-fact behavior.
What does it mean for you? Incidents and alerts from Coralogix can now flow into Bluebricks as investigation threads, so on-call work and infra context live in the same place.
Alert threads section in the agent side menu
Threads created from external alerts (starting with Coralogix) now have their own "Alert threads" section in the agent side menu, separate from regular conversations. Coralogix branding shows on the alert row and the thread header.
What does it mean for you? You can spot alert-driven investigations at a glance and keep them visually separate from your day-to-day agent conversations.
⚡ Improvements
Better handling of stale active threads
When you open an agent thread that's marked active but has no live connection (for example, after a backend timeout), the UI no longer hangs on "Processing" forever. It now surfaces a "This response timed out" message with a retry option.
What does it mean for you? No more waiting indefinitely on threads that are silently dead. You see what happened and can retry without leaving the page.
🐛 Bug fixes
Fixed stream resume errors after multiple page reloads: Refreshing the browser repeatedly during agent streaming would surface "Unable to connect to the agent due to an issue on our end." This was a multi-pod scoping issue and is now resolved.
Fixed agent threads stuck on "Processing" indefinitely: A thread whose tool call never produced a final answer would hang on "Processing" forever after a refresh. The thread now resolves to a proper timeout state.
Fixed feedback submission after a stopped response: After stopping a streaming response, clicking "No" in the helpfulness prompt and submitting feedback failed with "Something went wrong." Feedback now submits correctly even when the response was stopped mid-stream.
Fixed run name and PR misalignment on the run plan page: Opening a plan URL directly (with no back-button context) caused the run name and PR data to render misaligned. Now aligned regardless of how you got there.
Fixed subdir and ref fields cleared on URL edit when adding artifacts: In the "New Package" flow, pasting a git URL with subdir/ref and then editing the URL was wiping the parsed subdir and ref fields. They're now preserved.
Fixed agent scope "select/unselect all" ignoring active filters: With a filter active in the agent scope dropdown, "select all" and "unselect all" only applied to the filtered subset. They now consistently apply to all collections regardless of filter.
Last updated
Was this helpful?