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

# Release 1.6.0

Released to the Chrome Web Store on 4/27/2022

### ✨ Enhancements

* Create and modify blueprints from the Page Editor
* Warn users if they’re inputting a JSON string for the payload of the `@pixiebrix/http` brick ([#3192](https://github.com/pixiebrix/pixiebrix-extension/pull/3192))
* New “top” target for running brick in the top-level frame of the window ([#3200](https://github.com/pixiebrix/pixiebrix-extension/pull/3201))
* PixieBrix now suggests selectors relative to elements with id-like attributes, e.g., `data-cy`, `data-test-id`, etc. ([#3161](https://github.com/pixiebrix/pixiebrix-extension/pull/3161))
* Support for including images in the sidebar and form description ([#3256](https://github.com/pixiebrix/pixiebrix-extension/pull/3256))

### 🐛 Bug Fixes

* Page Editor Preview Panel not showing previews for non root-aware brick ([#3219](https://github.com/pixiebrix/pixiebrix-extension/issues/3129))
* Fix appearance of the “Delete” button for installables on the Blueprints Screen ([#3166](https://github.com/pixiebrix/pixiebrix-extension/pull/3168))
* Blueprints Screen slow to load for admins of large organizations ([#3165](https://github.com/pixiebrix/pixiebrix-extension/pull/3165))
* Blueprints Screen not indicating which deployments are paused ([#3174](https://github.com/pixiebrix/pixiebrix-extension/issues/3174))


---

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