> 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/july-3-2026-release-notes.md).

# July 3, 2026 Release Notes

## Jun 25–Jul 1, 2026

***This week:*** *Set per-goal check-in cadences, rename OKR statuses to match your team's language, and invite teammates by @mentioning their email anywhere. Plus request access to any document in one click, a smoother invite flow, and comments that survive AI edits.*

## New Features

🆕 **Per-Goal Check-in Reminders**

Set a different check-in cadence for each goal instead of one rhythm for everything. A weekly sales goal and a monthly ops goal can each prompt on their own schedule. You can also adjust cadence directly from chat.

*Try it:* Open any goal → Check-in settings → set a custom rhythm.

🆕 **Custom OKR Status Labels**

Rename OKR statuses so the labels match your team's language — "On Track" can become "Green," "Behind" can become "Off Pace," whatever fits. Only the display name changes; reports, filters, and automations keep working without any reconfiguration.

*Try it:* Admin → Model Customization → edit any status label.

🆕 **Invite Teammates via @Mention**

@mention an email address anywhere — in a document, comment, or chat — and Rhythms invites that person to your workspace inline. No jump to admin settings, no separate invite flow. The new user appears as a mention immediately after the invite is sent, so the conversation keeps moving.

*Try it:* Type `@` followed by any teammate's email in a document, comment, or chat message.

## Key Improvements

* **Request access to any document** — Land on a document you can't open? Ask for access right from the page instead of tracking down the owner. Owners get a notification and grant access from the Share modal they already use.
* **Invite people from the Share modal** — Add teammates who aren't in the workspace yet by entering their email in the Share modal. Set their permission level and invite them in a single step.
* **Comments survive AI edits** — Your document comments stay attached when an AI agent rewrites the doc, so feedback you've captured doesn't get lost as content evolves.
* **Choose your landing page** — Pick where Rhythms opens by default — Inbox, OKRs, Command Center, or Library — from your profile settings. The choice is saved to your account and applies across devices.
* **Live status in the Slack bot** — The Rhythms Slack bot now shows what it's actually doing ("Searching OKRs…", "Reading document…") instead of a generic "Thinking…", so you can see progress in real time.
* **Draft OKRs from chat** — OKRs created through chat or MCP now support a Draft status, letting you review before publishing. Ask Rhythms to draft goals for you and refine them before making them visible to your team.


---

# 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/july-3-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.