> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/release-notes/october-28-2026-release-notes.md).

# October 28, 2026 Release Notes

*This release:* Add images from chat directly into documents, reconnect personal connectors without rebuilding setup, and read assistant replies more comfortably.

## New Features

### 🖥️ Add Chat Images to Documents

Turn a chat attachment into document content without manual copying. Attach a PNG or JPEG image in chat and ask the assistant to place it under a named section; the image stays in the document even if the chat attachment is later deleted.

*Try it:* Attach a screenshot in chat and ask the assistant to add it under a named section.

[Learn more: Add an image from chat to a document](https://help.rhythms.ai/documents-and-library/add-an-image-from-chat-to-a-document)

## Key Improvements

* **Reconnect personal connectors without rebuilding setup.** Renew a personal connector's authorization while keeping its connection and associated automatic updates, playbook bindings, triggers, and schedules. If authorization fails, your existing credentials are preserved.
* **Read assistant replies more comfortably.** Follow assistant responses more easily with readable spacing and line lengths for prose, while tables, code, and interactive content keep their available width.


---

# 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.rhythms.ai/release-notes/october-28-2026-release-notes.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.
