> 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/february-18-2026-release-notes.md). # February 18, 2026 Release Notes ## New Features 🆕 **Chat Check-Ins** Checking in on a goal used to mean leaving what you're doing, navigating to the goal, filling out a form, and saving. Now just ask in chat. Rhythms presents a pre-filled form — value, status, and a draft note — based on how the goal tracks progress. Review, adjust if needed, save. You never leave the conversation. **Improvements** * Resolve comment threads — Mark a thread as resolved to collapse it out of the active view. The full history stays accessible if you need it later. * Scheduled playbooks — Set a playbook to run on a daily, weekly, or custom cadence and it executes automatically. No more remembering to trigger it yourself. --- # 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/february-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.