> 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-21-2026-release-notes.md). # May 21, 2026 Release Notes ## New Features 🆕 **Command Center *****(Beta)*** A personalized daily briefing, private to you, that surfaces the risks, opportunities, and signals most relevant to your work. Command Center pulls from everything connected to Rhythms and distills it into what matters today: items that need your attention, changes worth knowing about, and moments to act before they become problems. It refreshes automatically each morning — open Rhythms, and your most important context is already waiting. *Currently in beta — we welcome your feedback.* 🆕 **Documents Auto-Refresh** Keep your documents always up to date without lifting a finger. Auto-refresh lets you set any document to regenerate its content on a schedule — daily, weekly, or at whatever cadence fits your workflow. You can keep a single document live (refreshing in place at a set interval) or set up a time-based series that automatically creates a new edition each period. Generate the first version the way you like, configure the cadence, and Rhythms handles the rest. 🆕 **115 New Connectors Available** 115 built-in MCP connectors have been added to the catalog, including Slack's official MCP server. If you've been waiting for a specific integration, there's a good chance it's now available. ## Key Improvements * **Compact Goal IDs for Easy Reference** — Reference any goal with a stable short ID like `OBJ-001` or `KR-042` — ideal for Jira tickets, spreadsheets, and Slack threads. Show the Short ID column in the OKR grid, include it in CSV exports, or search by it directly. * **Instant Integration Break Alerts** — Get notified immediately when a connected integration stops working, so you can fix it before it impacts your data — not days later when you notice auto-updates went silent. * **Smarter Goal Creation** — Create Objectives, Key Results, or Initiatives from a single unified flow. An intelligent layer recognizes what you're trying to achieve and pre-fills the right goal type, alignment, team, and metrics. AI chat now drafts complete proposals for your review before saving, so goals come out cleaner and better structured. * **Expand All OKRs Instantly** — Press `Shift+R` to expand or collapse every OKR on the page at once — all levels, all descendants. Full tree view in one keystroke. * **Structured Check-in Prompts** — The check-in note field now suggests a Highlights / Lowlights / Next Steps structure, nudging toward more consistent and actionable updates across your team. --- # 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-21-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.