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

# Release 1.8.6

Released to the Chrome Web Store on January 9, 2024

### ✨ Enhancements

* The Mod Launcher now displays title emojis in black of the brick icon when provided in the panel title (#[7145](https://github.com/pixiebrix/pixiebrix-extension/pull/7146))
* When closing the last panel of the Sidebar, the Sidebar now only closes if the last panel was a temporary form panel. Otherwise, the Mod Launcher is shown instead. (#[7192](https://github.com/pixiebrix/pixiebrix-extension/pull/7195))
* Mods listed in the Mod Launcher are now sorted alphabetically (#[7225](https://github.com/pixiebrix/pixiebrix-extension/pull/7226))

### 🐛 Bug Fixes

* Fixed a bug where some Brick Configuration warnings were not being displayed above the affected fields in the Page Editor (#[7167](https://github.com/pixiebrix/pixiebrix-extension/pull/7194))
* Fixed bug where the Variable Popover was not being defaulted to on for users (#[7175](https://github.com/pixiebrix/pixiebrix-extension/pull/7176))
* Fixed bug where the HTML Renderer was throwing errors if the `Allow IFrames` was not toggled on (#[7157](https://github.com/pixiebrix/pixiebrix-extension/pull/7156))
* Prevent typing `@` in `Mod Options` from erroneously triggering the Variable Popover (#[7143](https://github.com/pixiebrix/pixiebrix-extension/pull/7156))

### 🧱 New/Updated Bricks

* Updated the `@pixiebrix/convert` brick to now support converting markdown to text (#[7161](https://github.com/pixiebrix/pixiebrix-extension/pull/7161))
* Implemented new `[Experimental] Run Metadata` brick. Developers can read metadata from the brick. (#[7142](https://github.com/pixiebrix/pixiebrix-extension/pull/7142))
* Implemented new `[Experimental] Get Brick Interface` and `[Experimental] Run Brick By ID]` bricks. Developers can get the brick interface (id, name, description, inputSchema, outputSchema) and can run a brick by the registry id (enables bricks to be made available as tools to ChatGPT and other LLMs). (#[7125](https://github.com/pixiebrix/pixiebrix-extension/pull/7125))

### 🎨 User Experience

* New Comments Tab added to the Data Panel. Developers can now add comments to any non-starter brick. Comments can be previewed in the Brick Configuration pane (#[7102](https://github.com/pixiebrix/pixiebrix-extension/pull/7123), #[7103](https://github.com/pixiebrix/pixiebrix-extension/pull/7163). #[7210](https://github.com/pixiebrix/pixiebrix-extension/pull/7230))


---

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