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

# Release 1.8.5

Released to the Chrome Web Store on December 18, 2023

### ✨ Enhancements

* Can now add Activation Instructions to mods to help guide users when activating mods that require additional configuration (#[7044](https://github.com/pixiebrix/pixiebrix-extension/pull/7045))
* Reorganized form builder fields. Temporary form builder fields are separated into sections and all form-level fields are listed above field definitions (#[7060](https://github.com/pixiebrix/pixiebrix-extension/pull/7060))

### 🐛 Bug Fixes

* Fixed a broken docs link for troubleshooting nework errors (#[7073](https://github.com/pixiebrix/pixiebrix-extension/pull/7073))
* Fixed optional chaining in variable expressions, e.g., `@mod.foo?.data` (#[7074](https://github.com/pixiebrix/pixiebrix-extension/pull/7075))
* Fixed issue where viewing the `Append to Google Sheets Brick` cleared variable expressions for data in the Page Editor (#[7076](https://github.com/pixiebrix/pixiebrix-extension/pull/7078))
* Fixes messing element key in brick outline for map values brick and adds the variable to the variable popover (#[7118](https://github.com/pixiebrix/pixiebrix-extension/pull/7118))
* Fixes issue where the mod launcher would be shown in addition to the mod activation panel when there were no other available sidebar mods (#[7119](https://github.com/pixiebrix/pixiebrix-extension/pull/7120))

### 🧱 New/Updated Bricks

* We've added a new `Comment` brick to assist developers in documenting their Mod Components (#[7027](https://github.com/pixiebrix/pixiebrix-extension/pull/7028))
* Dropped the `@pixiebrix/uipath/app` brick as it is nolonger necessary or used (#[7068](https://github.com/pixiebrix/pixiebrix-extension/pull/7068))
* Removed the `[Experimental]` flag on the JavaScript brick (#[7079](https://github.com/pixiebrix/pixiebrix-extension/pull/7079))
* Adds new `HTML` argument to the `Copy to Clipboard` brick (#[7098](https://github.com/pixiebrix/pixiebrix-extension/pull/7099))
* Adds `Map Automation Anywhere Co-Pilot Data` brick to set host data to pass to the AA Co-Pilot (#[7104](https://github.com/pixiebrix/pixiebrix-extension/pull/7109))
* The `Identity` brick now uses `property` as the default property name instead of `value` (#[7116](https://github.com/pixiebrix/pixiebrix-extension/pull/7116)) 
* Updated the `Show Sidebar` configuration: Panel Heading is now Tab Title to better match the starter brick configuration terminology (#[7117](https://github.com/pixiebrix/pixiebrix-extension/pull/7117))

### 🎨 User Experience

* The new Page Editor Walkthrough is now triggered on the developer welcome page (#[6944](https://github.com/pixiebrix/pixiebrix-extension/pull/7026))
* Clarified the `Remove` actions in the Page Editor by renaming the actions to `Deactivate` or `Delete` as appropriate. (#[7061](https://github.com/pixiebrix/pixiebrix-extension/pull/7082))


---

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