> 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-1-2026-release-notes.md).

# January 1, 2026 Release Notes

## OKR Check-in Rollup Visual Indicators

[Watch the video](https://www.loom.com/embed/f3aef1bc8aa94515ad9af5a0a1e9e38b)

When you check in on a child OKR, parent and ancestor goals now display visual indicators that show rollup calculations are pending or actively processing. This improvement provides immediate feedback during the check-in workflow, helping you understand when higher-level progress metrics are being updated. You can see the calculation status in real-time without needing to refresh or wait to verify that your check-in data has propagated through the goal hierarchy. This transparency is particularly valuable for teams managing multi-level OKR structures where understanding data propagation timing is critical for accurate reporting.

***

## Improvements

* **Chat Reliability**: Chat now preserves partial responses if streaming is interrupted, with enhanced error handling that provides clear feedback when operations encounter issues
* **Search Performance**: Improved search speed and accuracy through optimized filtering mechanisms
* **Check-in Window**: Extended the default check-in window from 2 to 3 days, giving you more flexibility for late check-ins

## Fixes

* **Data Quality**: Improved handling of invalid calculation values to prevent data corruption, and eliminated duplicate team entries during goal creation
* **Connector Setup**: Resolved a critical issue preventing users from adding new integrations


---

# 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-1-2026-release-notes.md?ask=<question>&goal=<user_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.