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

# Release 1.2.11

### 🐛 Bug Fixes

* Google file picker shows a blank screen ([#1048](https://github.com/pixiebrix/pixiebrix-extension/issues/1048))
* Brick `logger.debug` calls not flowing through to logs (To see debug logs, toggle "Log Values" in the Developer Settings) ([#1145](https://github.com/pixiebrix/pixiebrix-extension/issues/1145))
* Selector error when saving/creating page load trigger from the Page Editor ([#1172](https://github.com/pixiebrix/pixiebrix-extension/issues/1172))
* Can't install bricks from the marketplace that have a period in the id ([#1181](https://github.com/pixiebrix/pixiebrix-extension/issues/1181))
* Duplicate context menu entries were sometimes being created in Chrome and the Page Editor ([#1169](https://github.com/pixiebrix/pixiebrix-extension/issues/1169))
* New configurations created in marketplace activation wizard weren't immediately available for use ([#1047](https://github.com/pixiebrix/pixiebrix-extension/issues/1047))
* You had to restart the extension to see changes to service definitions made in the workshop ([#1171](https://github.com/pixiebrix/pixiebrix-extension/issues/1171))

### ✨ Enhancements

* Personal extensions are automatically synced to your PixieBrix account. You can delete synced extensions from the Active Bricks page ([#1150](https://github.com/pixiebrix/pixiebrix-extension/issues/1150))

### 🎨 User Experience

* Improve onboarding redirect sequence ([#1028](https://github.com/pixiebrix/pixiebrix-extension/pull/1028))


---

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