# Release 3.2.3 ### :sparkles: Enhancement * Chat Copilot / Mod Builder: * Assistant messages now span the full panel width, removing unnecessary card borders and horizontal dead space * Chat Copilot / Mod Builder > Improved table styling in assistant messages with proper header\ borders * AI Mod Generation > Improved Document Builder color contrast guidance * Bricks: Throw Error brick now supports a cause input for chaining error causes through Try-Catch blocks, with auto-expanded cause chains in the error detail modal * Deployments > Heartbeat now uses Chrome Alarms for more reliable scheduling in service workers, and respects server Retry-After headers on rate-limited responses #### :bug: Bug Fixes * Page Editor > Analysis Warnings: Fix annotation path filtering using incorrect string match causing annotation to appear on incorrect brick in outline view * Chat Copilot / Mod Builder: suggested prompt buttons now stay within the message input area width * AI Mod Generation: * Automatically derives Automation Anywhere bot search queries from the user's description instead of asking a clarifying question * AI Mod Generation > Reuses bot/API task names already provided in the user's prompt instead of redundantly requesting them * Added guardrail preventing text selection event from being suggested as a starter brick * Deployments: * Fix server error when a user is removed from a deployment during the heartbeat check * Deployments > Fix mismatch between server and extension in determining changed deployments, preventing unnecessary reactivation cycles * Fix duplicate deployment display when a user is assigned to two deployments of the same mod --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.pixiebrix.com/release-notes/release-3.2.3.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.