> 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/april-9-2026-release-notes.md). # April 9, 2026 Release Notes ## New Features πŸ†• **Goal Type Conversion**\ Changed your mind about how a goal is structured? Convert any goal between Objective, Key Result, and Initiative without losing anything. Check-ins, comments, ownership, labels, and progress all carry over. Restructure freely β€” your history comes with you. πŸ†• **Dashboard Auto-Refresh**\ Set a schedule β€” daily or weekly β€” and your dashboard pulls fresh data from connected integrations automatically. No one needs to remember to refresh it. Leadership always sees current numbers, not last Tuesday’s. ## **Improvements** * **Billing via Stripe** β€” Manage your subscription, seats, and payment methods directly through Stripe Checkout. Everything in one place, no back-and-forth with the 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/april-9-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.