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

# Release 1.7.29

Published to the Chrome Web Store on June 6, 2023

### ✨ Enhancements

* Improve select widgets in Form Builder and Document Builder forms
* Add a persistent “Home” tab to the sidebar with Mod listing
* Add support for passing pipelines as closures to custom bricks built in the workshop

### 🐛 Bug Fixes

* Fix losing keypresses for embedded forms in panels attached to page state
* Error logging into Admin Console using magic links if you’ve logged in with Google or Microsoft before
* Show Marketplace Icon during Extension Console activation
* Brick pipelines do not appear in the Page Editor mod layout for custom bricks
* The Google Sheet File Picker button is stuck as disabled if you canceled out of the File Picker

### 🧱 New Bricks

* The new `Run Bricks` brick enables running one or more bricks asynchronously


---

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