> 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/november-13-2025-release-notes.md).

# November 13, 2025 Release Notes

This week we focused on reliability and performance, with improvements to chat and status management.

## Improvements

* **Chat Reliability**: Chat automatically recovers when connections drop, preventing stuck operations during cascading and ensuring smooth conversations even in unstable network conditions
* **Status Dropdown**: Key result status options now follow a more intuitive progression (On Track → Behind → At Risk), making it easier to assess risk at a glance
* **Postponed Status**: Change objectives from "Postponed" back to active statuses and make check-ins, allowing you to resume work when priorities shift
* **Progress Popovers**: Popovers now load faster, helping you quickly review check-in details and AI explanations
* **Weight Editing**: Edit key result weights to exclude or adjust AI-powered progress contributions, giving you control when the AI's assessment doesn't match your judgment. *Contact your Rhythms Customer Support Representative if you would like weighted contributions enabled for your organization.*


---

# 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/november-13-2025-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.