> 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/september-18-2026-release-notes.md). # September 18, 2026 Release Notes *This week:* Archive OKRs without losing their history, share presentation templates across your workspace, bring multiple document passages into one chat, see exactly when integration updates will run, and make AI work more private, faster, and better informed. ## New Features ### 🖥️ Archive OKRs Keep your OKR workspace focused without deleting the history you may need later. Archive abandoned drafts, duplicates, or outdated goals to remove them from your working lists, rollups, and reminders while preserving check-in history, timelines, and provenance. Restore an archived OKR with one click whenever it becomes relevant again. *Try it:* Open an OKR you no longer need in your working set → choose Archive. ### 🖥️ Workspace Templates Give everyone on your team a consistent starting point for presentations. Admins can upload and manage shared PowerPoint templates, and everyone can find and use enabled workspace templates alongside document and HTML templates in the Library. You can also favorite the templates your team uses most. *Try it:* Open the Library → filter to Templates → choose a shared presentation template. ### 🖥️ Multiple Chat Passages Bring more of the right context into a single conversation. Add several passages—or selected table cells—from a document to chat, keep each quote visible, and remove any one of them without losing the rest. Rhythms keeps the selections together as you continue working in the document. *Try it:* Select a passage in a document → choose Add to chat → select another passage and add it too. ## Key Improvements * **See your next integration update.** View the last successful sync, recurrence, timezone, and next scheduled run directly in the integration panel, so you know when fresh data will arrive. * **Reconnect OAuth integrations faster.** Repair an eligible, errored OAuth connection directly from Playbook connections without hunting through Integrations or changing the existing connection. * **Know where ambient AI work will happen.** Before accepting an ambient offer, see whether it will continue privately in a DM or in a channel thread. If the destination changes, the offer refreshes and asks you to confirm again, helping prevent unintended sharing. * **Start chats faster.** Chat startup no longer waits on a serial profile lookup, removing an observed \~744 ms delay while preserving authorization checks. * **Get more complete AI answers.** AI search now returns compact, bounded evidence with summaries and pagination, reducing truncated results and helping agents produce better answers. --- # 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/september-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.