> 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/october-23-2025-release-notes.md).

# October 23, 2025 Release Notes

We've enhanced how teams share progress updates with a feature requested by Viva Goals customers.

## Check-in Attachments

Add files directly to your check-in updates to provide richer context and documentation. Upload supporting materials like screenshots, spreadsheets, or reports alongside your progress narrative, helping your team understand not just what changed, but why. This brings Rhythms to parity with Viva Goals attachment functionality, addressing a key need for migrating teams who relied on this capability to share comprehensive progress updates.

Learn more about what makes an effective check-in [here](/goals-and-okrs/managing-and-tracking-goals/write-and-submit-check-ins.md)

***

## Improvements

* **Saved View Preferences:** Customize your OKR filters and layout, and Rhythms remembers them the next time you open the app, even after logging out or closing your browser.
* **Workspace Layout Memory**: Your panel sizes stay consistent when opening links from Slack, switching between browser tabs, or starting new sessions—no more readjusting your workspace every time.

## Fixes

* **Progress Metric Display**: Auto-created "Progress" metric fields now consistently apply 0%-100% formatting from the start, improving clarity when creating Key Results.


---

# 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/october-23-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.