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

# Release 3.3.3

Published to the Chrome Web Store on October 6, 2026

#### :sparkles: Enhancements

* Activity & Security Policies:
  * A new Info severity sits below Low: it never raises an agent's risk score and is available as a rule severity and to the Record Security Event, Security Warning, and Soft Block bricks.
  * Smart Redaction now redacts detected entities from captured button captions, and records a click that navigates the page as a selector-only event instead of dropping it.
  * New AI Tool Access rule category to control access to unapproved AI tools.
* Activity Tracking & DLP:
  * Button clicks, field edits, protected-field edits, references, interaction matching, and AI-tool detection now apply inside iframes and embedded apps (such as CKEditor-style editors and claude.ai artifacts), not just top-level pages.
* Bricks:
  * Custom Form: a new Custom Clear Handler runs an onClear pipeline when an agent clears a text area.
  * Rich Text field: toolbar buttons now highlight to match the formatting under the caret and announce their on/off state to screen readers.

#### :bug: Bug Fixes

* Activity Tracking & DLP:
  * Fix bug where URL on SFDC was recorded as the original app-shell URL instead of the current URL
  * Field DLP rules keep working after an editor replaces the frame's document
* Bricks:
  * Custom Form: an autoSave form inside a panel that refreshes on state change no longer loses or restores characters while an agent is typing.
  * Custom Form: a form that hits a render error now shows a dismissible "Form Error" with a Close button instead of stranding the agent in a modal.
* Page Editor:
  * An edit made just before Save (such as a Sidebar Panel's Tab Title) is no longer occasionally dropped from the saved mod.
  * Editing a Pipedream configured property no longer refetches every property's remote options after the debounce.
  * Mod Builder: the ⋮ actions menu in the sidebar Mod Builder opens on top of the panel and is clickable again.
  * Integrations: restored the Jira Create Issue and Update Issue dropdowns in the Page Editor
* Sidebar: Show Sidebar now refreshes an already-open panel again when the open is gesture-blocked, instead of leaving stale content.
* Extension reliability:
  * Fixed a content-script crash when the loading spinner rendered in a frame with no document head yet.
  * A blocked IndexedDB upgrade (telemetry, trace, activity, or package registry) now fails with an error instead of hanging every caller indefinitely.
  * The background service worker file name is now version-stamped, so an updated extension reliably runs the new background code (for example, the URL soft-block overlay) instead of a stale worker.


---

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