> 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-notes-archive/release-2.3.5.md).

# Release 2.3.5

### :frame\_photo: User Experience Improvements

* Add support for synchronizing extension UI settings across browser extension installs (enabled by default for new extension installs)
* Page Editor: "Jump to design view\..." affordance in toolbar is now generally available to jump to form/panel design views

### :bricks: New/Updated Bricks

* Add Open Copilot brick, with support for showing copilot in floating panel
* Render Document/Form: support inline CSS styles in Advanced: Theme configuration group 

### :race\_car: Performance Improvements

* Ignore unrelated state change events for triggers and panel updates

### :bug: Bug Fixes

* Fix bug where Mod Launcher showed "No panels available" if the copilot was the only available sidebar panel
* Make Page Load/Navigation event firing consistent during [backward/forward cache (bfcache) navigation](https://web.dev/articles/bfcache)


---

# 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-notes-archive/release-2.3.5.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.