> 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-19-2026-release-notes.md). # June 19, 2026 Release Notes ## πŸ†•New Features πŸ†• **Four New Connectors: Mixpanel, Aha, Outlook Calendar** Four more tools are now available as connectors. Mixpanel and Aha are live in the connector catalog. Outlook Calendar joins Google Calendar as a fully supported calendar source, so your meetings and events show up in Rhythms regardless of which calendar you use. Connect any of them from the Connectors page. πŸ†• **Check-in Mention Notifications** When you @mention someone in a check-in note, they now get notified. Before this, mentions in check-ins were purely cosmetic β€” the person you tagged had no idea they'd been called out. Now the mention is tracked and a notification goes out through the same delivery path as comment mentions. Tag a teammate in a check-in and they'll actually see it. ## Key Improvements * **Plan Beyond This Year** β€” Time period creation was silently capped at December of the current year, making it impossible to set up periods for 2027 or later. That cap is gone. You can now create time periods as far out as you need β€” useful for annual planning cycles that start before the year turns. * **More Reliable Agent Document Edits** β€” The AI agent now reads and writes documents in markdown β€” a cleaner, more predictable path than the previous approach. Edits land more accurately, edge cases that used to cause garbled output are gone, and the agent handles complex document structures without losing formatting. * **Team Selection Auto-fills Owners** β€” When you pick a team in an OKR or initiative creation form, the owner field now auto-populates with the team's owners. One less thing to fill in manually β€” and it defaults to the right people. --- # 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-19-2026-release-notes.md?ask=&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.