> 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/january-8-2026-release-notes.md). # January 8, 2026 Release Notes ## Team Owners Archive and Delete Permissions ![](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-9d1ef965e889cefa3401bd68662eaee912258061%2F5e7ab716-dc43-434e-8876-3f3ae916f346-image.png?alt=media) Team owners can now manage their teams independently throughout the entire team lifecycle. Archive inactive teams to keep your workspace organized, unarchive teams when projects resume, or delete test teams without requiring admin assistance. This change enables team owners to handle common team management tasks directly, reducing administrative bottlenecks and allowing admins to focus on higher-level governance. Team owners maintain the same ownership and permission structure they already have, with these additional capabilities available through the team actions menu. *** ## Improvements * **Closed Status Filter for OKR Tables**: Filter OKRs by closed status in table views, making it easier to manage completed objectives and keep active work visible * **Check-in Actions on Goal Details Page**: Check-in buttons are now accessible directly from goal details pages, enabling you to update progress without returning to table views * **Dynamic Filter UX Improvements**: New rolling time window filters (Last 7 days, Last 30 days) make it easier to focus on recent activity without manual date selection * **Chat Interface Redesign**: Chat interface features a modernized design with improved message display and task cards, making conversations easier to follow ## Fixes * **Check-ins & Progress Tracking**: Improved accuracy and reliability across check-in workflows, including better display of current progress, expanded timezone support, and streamlined scheduling options * **Data Quality**: Search interface now correctly reflects custom terminology for Objectives, Key Results, and Initiatives, and bulk imports automatically create required progress metrics * **Integrations**: Improved connection stability for Linear, Monday.com, and Atlassian integrations by resolving refresh token issues * **AI & System Reliability**: Resolved streaming issues in AI chat conversations, fixed AI summary token overflow on large views, and eliminated duplicate notifications when managing labels --- # 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/january-8-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.