> 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.3.6.md).

# Release 3.3.6

Published to the Chrome Web Store on November 16, 2026

#### :sparkles: Enhancements

* Bricks:
  * Hide Elements / Insert HTML Element: these bricks now support the `>>>` shadow-root selector marker, so they can reach elements inside open shadow DOM
  * Local AI: Local AI bricks now offer all seven sampling modes in the dropdown

#### :bug: Bug Fixes

* Chat Copilot: Fixed a side-panel error when sending a new message while the previous answer was still streaming.
* LLM Response Streaming: A dropped or aborted streaming response now surfaces an error instead of presenting the cut-off reply as complete; mod generation retries once first.
* Activity & Data Loss Prevention:
  * Page Text Pattern: a hidden form field stays hidden after a rich-text editor (CKEditor 5) rewrites its attributes on blur.
  * Acknowledging a URL soft block or AI Tool Access soft block no longer re-prompts on the next page load of the same rule.
* Accessibility: the Extension Console navbar now reports a busy state while the theme loads, so screen readers announce it correctly.


---

# 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.pixiebrix.com/release-notes/release-3.3.6.md?ask=<question>&goal=<user_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.
