> 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/july-9-2026-release-notes.md).

# July 9, 2026 Release Notes

## New Features

🆕 **Grant access from an @mention**

@mention someone who can't see the document and a **Grant view access** button appears inline. One click, they're in.

## Key Improvements

* **Continue interrupted chats** — When a chat hits its turn limit or gets cut off, click **Continue** to resume where it stopped. No re-runs, no duplicate work.
* **Move document sections cleanly** — Reordering sections now happens in one atomic step. No duplicate headings, no error loops.
* **Same person can be owner and delegate** — Assign one person to both roles on the same goal. The old restriction is gone.
* **@mentions always reach your inbox** — Turning off notifications now only silences Slack and email. Mentions still land in your Rhythms inbox.
* **Images survive Word exports** — Embedded images now render correctly in exported .docx files.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://help.rhythms.ai/release-notes/july-9-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 `build a script that syncs our docs to a CMS` 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.