> 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/march-4-2026-release-notes.md).

# March 4, 2026 Release Notes

***

## New Features

🆕 **Exclusion Filters**\
Sometimes it’s easier to say what you *don’t* want. Any filter — status, owner, team, time period, type, or label — now has an “is not” option. Build views like “everything except Closed” or “all goals not owned by me” in one click, and save them like any other filter.

🆕 **Generate Key Results and Child Objectives**\
You could already generate Initiatives from an Objective. Now you can generate Key Results and Child Objectives the same way. Start with a goal, hit Generate, and Rhythms suggests the structure beneath it — ready to review, edit, and publish.

## Improvements

* **Progress bar drill-down** — The progress bar now shows status labels and percentages inline. Click it to see a breakdown of what’s contributing — no need to open each goal individually.
* **Instant navigation** — Tab-switching and view-opening now happen without any perceptible delay. If you noticed it before, you won’t anymore.
* **Fuller progress history** — Parent objective graphs now show one check-in per unique date, going back up to 365 days. A full year of momentum, visible at a glance.


---

# 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/march-4-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.