> 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-8-2026-release-notes.md). # May 8, 2026 Release Notes ## New Features 🆕 **Give feedback right where the work happens** Highlight any text in a document, leave a comment, and your thread stays anchored exactly where you put it — even as the document evolves. Jump between the sidebar and the highlighted passage in one click, @mention teammates to pull them in, and resolve threads when the conversation is done. No more lost context or orphaned comments. 🆕 **Preview documents without losing your place** Open any Library item in a side panel while keeping chat, your current page, or another document visible alongside it. Resize the panel to fit your workflow, or expand to full page when you need to go deep. Cmd/Ctrl-click still opens a new tab if you prefer. 🆕 **Get comment notifications where your team already works** When someone @mentions you in a comment — on an OKR or a document — you'll now see it in Microsoft Teams with full context and a direct link back. No need to check email or remember to open the app; the conversation finds you. ## Key Improvements **AI assistant works reliably with your documents** — @mentions you've added to documents are preserved when the AI reads or edits them, chat search filters (by name, team, etc.) return accurate results again, and conversations recover gracefully if something goes wrong mid-task. The assistant can now be trusted with your real documents without silent data loss. **All built-in templates are now available to everyone** — MBR, Weekly Engineering Team Sync, and other system templates now appear in the layout picker and Library for all workspace members, so you can start from a proven structure without asking an admin to share it. --- # 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-8-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.