> 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/december-4-2025-release-notes.md). # December 4, 2025 Release Notes ## Import OKRs from Chat ⚠️ **Limited Beta - Contact Rhythms Customer Support to Enable** [Watch the video](https://www.loom.com/embed/b0665109889d40afa2b55202301d869d) Teams can now upload Excel or CSV files directly into chat and use natural language to bulk import OKRs, eliminating hours of manual data entry. The AI-powered import agent validates your data, handles missing information intelligently (auto-filling metric names and types), and creates structured OKRs ready for your review. Processing typically takes a few minutes depending on the size of your import, and you'll receive a custom view of your imported objectives once complete so you can verify everything before publishing. This capability supports enterprise migrations and regular program updates, handling anywhere from small batches to 250+ OKRs in a single import. Whether you're migrating from another platform or loading quarterly objectives from planning spreadsheets, the natural language approach makes bulk operations accessible to everyone on your team, not just technical administrators. ## Report Sharing & Interactive Analytics 📊 **Report Sharing: Generally Available** | 🔍 **Interactive Cells: Available Upon Request** ![](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-cb5bdba50de9295a2ce2659b184c5da331735bf5%2F2aa29346-d49b-469e-ad32-56a2cfde8c9d-cmitlsyyu0mrf0s0ifpyegwvb.png?alt=media) Reports now support consistent sharing controls, making it easier to collaborate on program health insights with stakeholders across your organization. Every user automatically gets access to the system-generated "Organization OKR Program Pulse" report, and you can create and share custom reports that focus on specific teams, time periods, or program metrics. When interactive analytics is enabled for your organization, report cells become clickable. Spot a trend or issue in any report table, click the cell, and drill down into a filtered view showing the exact OKRs behind that data point. This transforms reports from static snapshots into exploration tools, making it faster to identify which objectives need attention and take immediate action. Contact the Rhythms Customer Support team if you'd like to enable interactive analytics for your reports. See [Reports in Rhythms: Monitoring and Improving OKR Program Health](/goals-and-okrs/monitoring-and-reports/monitor-okr-program-health-with-reports.md) for more. *** ## Improvement * **Dashboard Comment Resolution**: You can now mark individual dashboard comments as resolved or unresolved with a dedicated filter to show only open items, maintaining a clear audit trail while focusing on active feedback during dashboard review processes * **Enhanced Goal Management**: Improved weight distribution accuracy across child Key Results, better metric recognition during check-ins, and more reliable roll-up calculations that properly aggregate actual metrics * **Metric Format Flexibility**: Added the ability to switch OKR metrics between percentage and number formats for all metric types, providing more flexibility in how you track progress * **Chat Window Persistence**: Your chat window size preferences are now preserved across sessions, maintaining a consistent experience * **View Management**: After saving a new view, you now stay on that newly created view instead of being redirected to "All OKRs," making it easier to immediately use your custom views * **Date Range Filter**: Improved organization with clearer month/year/quarter labels displayed inline for easier time period selection * **Default Views**: Updated Key Results and Initiatives views with optimized display preferences, and added new status-based views for "On Track - Current Quarter" and "At Risk/Behind - Current Quarter" * **Enhanced OKR Metric Generation**: Improved LLM-powered metric generation using batch processing to reliably handle up to 250 OKRs * **Parallel Chat Functionality**: You can now initiate multiple chat conversations simultaneously without waiting for streaming responses to complete * **Curated OKR Views**: Added support for views with fixed OKR ID lists, enabling precise display of specific OKR sets without relying on filter matching * **Non-Admin User Access**: Non-administrators can now view other users' OKRs by clicking on usernames in the Users section * **Check-in Cycle Timezone Support**: Check-in cycles now properly handle timezone differences, ensuring accurate timing for global teams ## Fixes * **Integrations & Data Quality**: Improved accuracy of integration progress calculations and notification formatting, resolved automatic status rollup issues for integrated Key Results, and enhanced search system reliability by fixing indexing race conditions * **Navigation & Display**: Fixed team name truncation in sidebar, label column visibility toggles, guest user profile menu access, eliminated unnecessary page reloads when toggling columns, corrected time period filter display on first render, resolved scrolling issues in OKR views, and fixed view navigation errors to show clear error messages instead of silent redirects * **Performance & Reliability**: Enhanced calculation accuracy for goal metrics and system stability, improved secrets management with encrypted configurations, upgraded security dependencies to address vulnerabilities, and streamlined prompt management for better AI summary performance --- # 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/december-4-2025-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.