> 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/july-22-2026-release-notes.md). # July 22, 2026 Release Notes ***This week:*** *Per-playbook AI model selection, plus a new Smart Activity Log in every document, chat that preserves your manual edits, and sharper OKR explorer counts.* ## New Features 💻 **Choose Your AI Model Per Playbook** Different playbooks have different needs. You can now set a specific AI model for each playbook — or leave it on Auto and let Rhythms choose. Every run records which model powered it, so you have full provenance when reviewing results or debugging unexpected behavior. *Try it: Open any playbook → Configuration → Playbook model → pick a model or leave it on Auto.* ## Key Improvements * **Smart Activity Log** — Every document now has an activity log panel showing recent changes, comments, and access. Open any document and look for the Activity Log in the side panel. It replaces the old version-history view and is on for all workspaces. * **Chat preserves your manual document edits** — Edit a document by hand, then ask chat for another change: your edits stay. Chat detects when its context is stale and stops rather than overwriting your work. * **Rename solution-installed playbooks** — Edit the title of any solution-installed playbook right from its detail page. New solution installs also get unique per-install names automatically, so multiple installs of the same solution stop looking identical. * **Solution hub pages are fully editable** — Edit the title, add comments, view version history, and take all the same actions you can on any document. The read-only restriction is gone. * **Stale Slack quick replies clear automatically** — When you start a new Rhythms turn in Slack, old quick-reply buttons from the previous turn are removed. Your thread stays clean without any manual cleanup. * **OKR explorer group counts and time period ordering** — Group-by count badges now show the true total across all pages, not just the rows currently loaded. The current time period also appears first in the list. --- # 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/july-22-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.