> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/release-notes/release-3.2.8.md).

# Release 3.2.8

### :sparkles: Enhancements

* Page Editor: 
  * Custom Forms embedded in a Brick (pipeline) element now show an Open in Interface View link to jump straight to the form's design view.
  * The AI mod-editing copilot no longer blocks edits on a mod's pre-existing warnings — only analysis errors and newly introduced warnings block.
* Bricks:
  * Readers: selectors can now cross open shadow DOM boundaries with the `>>>` combinator (e.g. `.host >>> input`), so readers and input paths can reach elements inside web components.

### :bug: Bug Fixes

* Page Editor: Move to mod, Copy to mod, and Duplicate now act on the mod component whose action menu was opened, not the currently-active one.
* Integrations: Automation Anywhere: a transient token-refresh failure (network drop, Control Room downtime, or a 5xx from the refresh endpoint) no longer signs the user out of their Control Room association — only genuinely invalid credentials clear it.
* Sidebar: Fixed an unhandled error when a temporary sidebar panel refreshed after the sidebar had already been closed.
* Bricks: A mod referencing an unavailable brick now reports a clear mod error instead of failing on every run and flooding logs.
* Performance & Stability:
  * Reclaim memory from detached tooltips, popovers, and text-selection menus, and tore down injected panels, widgets, and event listeners when their host elements leave the page
  * Self-heals the extension's local log and registry storage and stops error-retry loops that could otherwise stall the extension (missing IndexedDB stores, storage exhaustion, registry upgrade/resolution loops).
  * Guards against a startup crash on pages that have no document body.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pixiebrix.com/release-notes/release-3.2.8.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.