> 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-30-2026-release-notes.md). # April 30, 2026 Release Notes ### New Features 🆕 **Export Documents and OKR Grids from Chat** Need a Word doc or PowerPoint deck? Just ask the AI assistant. You can now export any document to Word or any OKR Grid view to PowerPoint or Word — right from the chat. No more navigating through menus. The assistant can work from a saved view, your current grid, or custom filters, and you'll get the file delivered straight to the conversation. ### Key Improvements **Faster Document Editing** Document edits are now up to 50% faster. Creating a full document dropped from \~5 minutes to \~2 minutes, and section rewrites are twice as quick. Everything works the same from your end — just noticeably snappier. **More Polished PowerPoint Exports** — Exported slide decks now look significantly better. Slides use proper visual hierarchy, accent colors, card layouts for key data, and prominent KPI callouts — no more walls of bullet points. If you upload a branded template, your colors, fonts, and visuals are applied consistently throughout. **Batch Layout Generation** Layouts with repeating sections — like per-goal summaries or per-team breakdowns — now generate all at once instead of one at a time. This means faster results and no more losing context halfway through a long report. **Guided Question Cards** — Typed responses now show as selectable options so you can review before continuing. Answers no longer disappear if the card loads at the same time you're typing. @mentions in your answers now render as clickable links, and post-submission stalls are resolved. **Smarter Bulk Check-ins** — When you ask the assistant to check in on goals you don't own, it now tells you upfront instead of starting the work and failing partway through. It also stops retrying when a goal can't be found and clearly reports which items were skipped and why. --- # 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-30-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.