> 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/august-28-2026-release-notes.md).

# August 28, 2026 Release Notes

***This release:*** *Documents can now export straight to PDF, you can create an account or sign in with Slack, 36 new connectors join the catalog, you can now drag SVGs straight into documents, Slack notifications explain why something matters and offer one-click next steps, and view search shows exactly where a matching OKR sits in your hierarchy.*

## New Features

💻 **PDF Export for Documents**

Documents can now be exported straight to PDF, alongside the existing Word and PowerPoint export options. Everything in the document — text, tables, checklists, images, charts, and diagrams — carries over into a clean, shareable PDF.

*Try it: Open a document, use the export menu, and choose PDF.*

💻 **Sign Up and Sign In With Slack**

“Continue with Slack” now works on both the sign-up and sign-in pages, alongside Google and Microsoft. Create your account straight from Slack and the flow carries right on through installing the Rhythms bot and picking the channels it should join — so you land in a workspace that's already wired to Slack instead of setting that up later.

*Try it: Open the sign-in or sign-up page and choose Continue with Slack.*

💻 **Bigger Connector Catalog**

Chances are a tool you use wasn't in the catalog yet. 36 new connectors just joined — spanning sales and marketing, developer tools, analytics, design, and more — bringing the catalog to nearly 200. Each one connects the same way: pick it from the catalog, sign in, and Rhythms starts pulling context from it right away.

*Try it: Open Settings → Connectors and search for a tool you use — there's a good chance it's already there.*

💻 **Drag SVGs Into Documents**

SVG images now work like any other image in your documents. Drag an SVG file in, or paste one you've copied, and it shows up inline immediately — no more workarounds or blank placeholders.

*Try it: Drag any SVG file straight into a document.*

## Key Improvements

* **Sign Up With Microsoft** — The “Continue with Microsoft” button now shows on the sign-up page, not just sign-in, so a Microsoft account can create a workspace the same way a Google account already could.
* **Smarter Slack Notifications** — Slack notifications now come with context: a sentence on why it matters to you, up to three relevant details, and sometimes a button to act right from the thread.
* **Search Shows You Where Things Sit** — Searching within a view now expands the hierarchy to show exactly where a matching OKR lives, with the match highlighted, instead of just returning a flat list.
* **See Cancelled Playbook Runs on Demand** — Run history now has a toggle to reveal cancelled playbook runs, complete with the reason each one was cancelled.
* **Text and Markdown Files in Chat** — You can now attach .txt and .md files in web chat, alongside the file types already supported.
* **Tagging Multiple People Now Works Reliably** — The @-mention dropdown now appears correctly every time, even when tagging several people in the same message.
* **Chat Remembers Screenshots You Shared in Slack** — Chat now holds onto images you shared earlier in a Slack thread, so follow-up questions about them get accurate answers instead of asking you to resend them.


---

# 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/august-28-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.
