> 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/march-11-2026-release-notes.md). # March 11, 2026 Release Notes *** ## New Features 🆕 **Dashboard Version History**\ Every edit to a dashboard is now tracked. See exactly what changed, compare versions with inline diffs, and restore any previous version in one click. When you restore, the current version is saved first — so nothing is ever lost. 🆕 **Unified Filter Search**\ Instead of hunting through separate dropdowns for Owner, Team, Status, Labels, and Time Period, there’s now one search bar that covers all of them. Type what you’re looking for, see matching values with counts, and apply in one click. 🆕 **Trending Reports**\ A snapshot tells you where goals stand. Trending tells you where they’re going. Track OKR momentum week-over-week to spot goals that are accelerating, stalling, or slipping — before it’s too late to course-correct. Slice by team, manager, or user, just like other reports. ## Improvements * **Keyboard shortcuts** — Press `?` anywhere in Rhythms to see all keyboard shortcuts, organized by context. Power users, this one’s for you. * **Chat as your home base** — The full-page chat experience is now the default landing page. Start every session ready to ask, create, or update — without navigating first. --- # 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/march-11-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.