> For the complete documentation index, see [llms.txt](https://help.zipcaptions.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.zipcaptions.app/change-log/zip-captions-online-and-pwa-changelog/build-2026-10-02t02-38.md).

# Build 2026-10-02T02:38

Released on: 02/10/2026

Release Build 2026-10-02T02:38 includes the following updates/new features:

* **Picture in Picture (PiP) Mode**:
  * Pop out live captions into a native floating window that stays on top of all other desktop applications.
  * Built using the browser's Document Picture-in-Picture API with zero external extensions required.
  * Convenient one-click toggle right from the Quick Access sidebar on the captioning screen.
  * Automatically inherits your custom Zip Captions theme, font, and display styling.
  * Seamless return to the main captioning screen when closed or toggled off without disrupting your session.
  * Learn more in our [Picture in Picture guide](/getting-started/picture-in-picture.md).


---

# 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://help.zipcaptions.app/change-log/zip-captions-online-and-pwa-changelog/build-2026-10-02t02-38.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.