> 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/june-12-2026-release-notes.md).

# June 12, 2026 Release Notes

🆕 **Shared Connectors**

One person connects an integration; the whole team uses it. No more "I can't run that — I haven't connected Jira yet." The owner of a connection can share it, set defaults per integration in **My Connectors**, and Rhythms automatically picks up the right credentials in chat and MCP calls. Most useful for shared GitHub orgs, team Jira projects, and any integration where everyone hits the same source.

*Try it:* My Connectors → share any connected integration → teammates select it as their default.

🆕 **Documents in Global Search**

Global search now finds documents, not just goals. Use the new **Documents** tab to search across every doc in your Library, or stay on **All** to see goals and documents together in one relevance-ranked list. If you've been navigating the Library tree to find a doc, stop — just search.

*Try it:* `Cmd/Ctrl + K` → type any keyword from a document title or body.

🆕 **Document Checklists**

Keep your notes and your to-dos in the same place. Add a checklist anywhere in a document, check items off inline, and they persist across sessions — no separate tool, no bullet list you forget to revisit. Supports nested sub-tasks for breaking work down.

*Try it:* In any document, type `/checklist` (or `- [ ]` for the GFM shortcut).

## Key Improvements

* **AI reasoning panel is now readable** — The panel that shows Rhythms thinking through a problem now renders full markdown (headers, bold, lists, code blocks) and auto-scrolls as content streams in. Much easier to follow along on complex multi-step tasks.
* **Check-in dates respect your timezone** — Check-in dates now show in your local timezone instead of UTC. If you check in at 11 PM your time, the date shown is your date — not tomorrow's.
* **Check-in label colors** — Labels on check-ins now display their colors in both the picker and the rendered view, matching the behavior you already get on goals and documents.
* **Library group-by works again** — Group-by **Layout** in the Library list is fixed after a regression. Filter and group-by dimensions now share a single source of truth, so they stay in sync going forward.
* **Document breadcrumbs** — The document view header now shows a proper trail: *Library › Documents › \[title]* (or *Library › Layouts › \[title]* for templates) instead of jumping straight from Library to the document title.


---

# 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/june-12-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.
