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

# Release 3.3.2

Published to the Chrome Web Store on September 22, 2026

### :sparkles: Enhancements

* Activity & Security Policies:
  * Page Element redaction: conceal a configured page region on-device by selector
  * Site Access rules: a new "Prompt for each record" option re-prompts agents when they open a different record under a per-record soft-block rule, instead of only on the first record
  * Button caption capture: the activity timeline now shows readable button captions (e.g. Save, Send report) by default
  * URL exceptions: each site-scoped rule takes an "Except these URLs" carve-out, so an admin can restrict a whole domain while still allowing specific pages (e.g. one approved document)
  * Event severity: every reporting rule can now set a custom severity for the events it records, instead of always inheriting the severity implied by its action
  * Soft-block acknowledgements: a rule can remember an agent's acknowledgement for the page session, tab, browser session, or never — so an agent moving between records isn't re-prompted on every switch
  * Smart Redaction for button captions: a caption containing a name, email, or number is now captured with only the sensitive parts masked (e.g. \[NAME], $##.##) instead of being dropped, so more captions stay readable in the timeline
  * Task tracking: two opt-in options auto-close a policy-opened task after a maximum duration, and start a new task when the agent opens a different record in the same tab — so a long-lived single-page-app session records separate tasks instead of one that spans everything (off by default)
* Bricks:
  * Security Warning: a new brick that shows a warning notice and records a security event without blocking the user, completing the monitor / warn / block security-brick family

### :bug: Bug Fixes

* Bricks:
  * Insert Text, Form Fill, and Set Input Value: correctly insert text into ProseMirror rich-text editors (Jira, Confluence) — paragraph breaks are no longer doubled.
  * Assign Mod Variable: a blank Variable Name now fails with a clear "Variable Name is required" error instead of silently writing an unreadable variable, and the Page Editor flags a literal blank name.
  * Button: an empty Location now reports a clear missing-location-selector error instead of a cryptic failure.
  * Fixed watch-mode Button containers accumulating page watchers over a long-lived single-page-app session, which degraded button attachment over a shift.
* Forms:
  * Fixed an intermittent "Form Error" panel showing a raw ID instead of the Form Modal.
  * Custom Form: fixed "Persist Unsubmitted Values" reopening a form with already-submitted values, and two forms on one mod component losing each other's fields.
* Page Editor: fixed a crash when opening Find in Mod with a blank search query.
* Integrations: fix bug when using HTTP Request brick with Integration Library integrations
* Activity & Security Policies: fixed page-pattern and page-element soft-block prompts forcing a reason even when "Require a reason" was off


---

# 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.2.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.