> 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-15-2026-release-notes.md). # May 15, 2026 Release Notes ## Key Improvements * **Filter by Delegate** — You can now filter any OKR view or report by delegate — the person actually doing the work on a goal. Use "is" or "is not" to quickly find delegated work across your team. * **Atlassian Connection Updated** — We've updated how Rhythms connects to Atlassian (Jira & Confluence) ahead of a platform change Atlassian is making on June 30. No action needed on your end — everything continues working as before. * **Edit Documents from Claude or Any MCP Client** — Previously, saving documents through external tools like Claude would fail due to a format mismatch. That's fixed — documents now accept standard markdown, so any MCP-connected tool can write and edit them without errors. * **Todo Plans Stay in Place** — The inline todo plan in chat now stays pinned where it was created instead of jumping around as new content streams in. Active tasks also show a cleaner "in progress" label. * **Custom Connector Icons** — Custom MCP connectors now show their actual icons in the chat input bar instead of generic initials, making it easier to see which integrations are active. --- # 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-15-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.