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

# Release 3.0.6

#### :sparkles: Enhancements

* Mod Deployments: support for per-user Personal Integration Configurations
* Chat Copilot: support for parallel tool calls

#### :bug: Bug Fixes

* Fix CSS conflict on pages with `.autocomplete` class name
* Page Editor: integration dropdown: fix bug where requiring configuration to be selected 2x from dropdown&#x20;
* Page Editor: design view: fix padding to prevent element actions from being cut off at top of design view
* Page Editor: show editor session as stale if mod deployment is updated by the background heart beat
* Extension Console > Share Mod Modal: fix duplicate organization entry for owning organization


---

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