> 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/august-18-2026-release-notes.md). # August 18, 2026 Release Notes ***This week:*** *new MCP connectors for Wispr Flow and Slack's official server, direct links to any heading or comment in a document, yearly billing for the Team plan (in development), and the ability to see what your OKRs roll up into — plus a smarter default chat model, visible model reasoning, sharper Library search, and more reliable Slack conversations.* ## New Features 💻 **New Connectors, More Tools** Your connector catalog just grew. You can now connect Wispr Flow and Slack's own official remote MCP server directly from Rhythms, putting their tools to work right alongside everything else you've already connected. No custom setup, no workaround — just pick them from the catalog like any other connector. *Try it: Open your connector catalog and connect Wispr Flow or Slack's official MCP server.* 💻 **Link Directly to Any Part of a Document** Long documents make it hard to point a teammate to the exact spot you mean — you'd end up describing “scroll to the third section” instead of just sharing a link. Now you can hover any heading or any comment thread and copy a link that opens straight to that spot, the same way you'd link to a specific block in Notion. It's a small thing that saves real back-and-forth every time you're pointing someone at feedback or a specific section. *Try it: Hover a heading or a comment thread in any shared document and click the link icon that appears.* 💻 **See What Your OKRs Roll Up Into** Graph view could only show you what rolled down from your objective — never what it rolled up into. If you wanted to see your VP's objective or their SVP's from your own goal, there wasn't a way to do it without pinning a view to specific goals ahead of time. Now you can expand upward from any goal in graph view, so the full chain of alignment above you is one click away instead of a workaround. *Try it: Open graph view on any goal and expand upward from it.* ## Key Improvements * **Sonnet 5 is now the chat default** — Rhythms chat now defaults to a more capable model, so longer conversations and bigger documents stay coherent without you having to switch models manually. * **See the model's reasoning as it thinks** — Chat with GPT, Claude, or Gemini now shows a summarized view of the model's reasoning as it works through your request, so it's clearer how an answer was reached. * **Sharper, more relevant Library search** — Search results now weigh exact-term matches higher, so documents matching everything you typed surface above partial matches. * **Chat only offers to do what it can actually do** — The chat agent no longer offers actions like sending an email unless it can actually complete them, so you won't get an offer that quietly falls through partway. * **Slack conversations no longer stall mid-reply** — A rare timing issue that could leave a Slack reply stuck on “Thinking...” indefinitely is fixed, so responses reliably make it back to your thread. * **The Rhythms Slack agent now works in group chats** — Group DMs with multiple people no longer block the agent from participating correctly, so it responds the same way it does in one-on-one conversations. --- # 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/august-18-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.