> 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/june-5-2026-release-notes.md). # June 5, 2026 Release Notes ## New Features 🆕 **Tag your check-ins with labels** Keep your check-ins organized the same way you organize goals and documents. Add labels when you check in from any surface — the create modal, the edit popover, chat, or MCP — and filter or group by them later. Need a new label? Create it inline while you're checking in and it's instantly available everywhere else. 🆕 **Share playbooks with your team** Playbooks aren't just yours anymore. Grant view, edit, or manage access to teammates so the whole team can run, refine, and collaborate on the automations you build. You can also point a playbook at someone's existing connections instead of asking them to set up new ones — making it dramatically faster to roll an automation out across a team. 🆕 **LogRocket MCP** LogRocket joins the library of one-click integrations. No setup required — it's already wired up for your tenant, so you can start pulling session data and product insights into Rhythms right away. ## Key Improvements * **Rhythms remembers more of your history** — If your tenant has Intelligence enabled, Rhythms now learns from your past chat threads and meeting notes (starting with Granola) — not just new activity going forward. That means smarter answers, better context, and more accurate connections across people, projects, and decisions from day one. New meeting connections also backfill automatically. * **Faster, more reliable Power BI queries** — Asking Power BI questions through Rhythms is now noticeably more dependable. Rhythms explores your data model first — tables, columns, measures, relationships — so queries are grounded in what actually exists, instead of looping on bad field names. If you're on Microsoft Copilot, you can now generate Power BI queries in plain English directly through the connector. * **Smoother setup for custom MCP connectors** — Setting up a custom MCP connector via OAuth is now far more forgiving. If a popup closes early or a provider takes an extra step, Rhythms waits and lets the callback complete instead of dropping the connector. Retries also reuse the same connector, so you don't end up with duplicates. * **@mentions in MCP check-ins now render as links** — When you post a check-in note through the Rhythms MCP, @mentions of people, goals, or documents now appear as clickable entity chips — not plain text — so notes stay connected to the things they reference. --- # 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/june-5-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.