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

# Release 3.0.5

Published to the Chrome Web Store on December 17, 2025

#### :bug: Bug Fixes

* Page Editor: fix active node not found error after clearing mod changes
* Page Editor: fix search result jitter when searching integration library
* Integration Library: fix handling of empty responses from integration actions

#### :sparkles: Enhancements

* Automatically start tab audio capture if extension has [activeTab permission for current tab](https://developer.chrome.com/docs/extensions/develop/concepts/activeTab)
* Support Flow: add support for recording Chat Copilot conversations for audit
* Support Flow: add support for custom summaries
* Page Editor: render integration library documentation Markdown
* Page Editor: show integration action title in Page Editor instead of generic integration action title

#### :race\_car: Performance

* Lazily fetch packages for deployments


---

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