> 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/may-29-2026-release-notes.md). # May 29, 2026 Release Notes ## New Features 🆕 **Document Liveness Indicator** Documents with auto-refresh enabled now display a liveness indicator — a status pill that shows at a glance whether the document is live, when it last refreshed, and provides quick access to adjust the refresh cadence. Instead of a binary toggle buried in settings, you get a persistent, visible signal of how current your data is — and one-click control to change it. 🆕 **Rhythms in Your Favorite Tool** Connect to Rhythms directly from Claude Desktop, Cursor, or any MCP-compatible client — including signing up for the first time without leaving your tool. Once connected, you can create and reply to goal comments, manage threads, and @mention teammates with full notification routing. The same Rhythms experience, wherever you work. ## Key Improvements * **Full Goal Change History at a Glance** — Every check-in edit and deletion now appears directly in the goal timeline with a side-by-side comparison, so you can see exactly what changed without clicking through entries individually. Deletions remove all related timeline entries automatically, keeping your history clean and accurate. * **Opus 4.7 and GPT-5.5 in Chat** — Two new frontier models are available in chat. GPT-5.5 is configured with extended prompt-cache retention for faster repeated queries. Switch your default model anytime from chat settings. --- # 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/may-29-2026-release-notes.md?ask=&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.