Release Roomote 1.20.1

CHANGELOG.md

@@ -2,6 +2,23 @@
 
 This file tracks product releases for Roomote (single monorepo version). Automated release entries are prepended by `pnpm run version`.
 
+## 1.20.1 (2026-11-05)
+
+Roomote 1.20.1 restores reliable Copilot task helpers, keeps Slack history reads useful in busy channels, and clarifies how agents carry out Slack replies and GitHub actions.
+
+### Highlights
+
+- Restore GitHub Copilot GPT-5.x task helpers that failed on an unsupported endpoint.
+- Keep available Slack history when a busy channel cannot be read completely in one request.
+- Avoid false lost-access reports for private Slack conversations and false refusals of authorized GitHub actions.
+
+### Patch changes
+
+- GitHub Copilot GPT-5.x task helpers use the correct inference endpoint instead of failing on requests sent to an unsupported endpoint.
+- Coding tasks recognize their authorized GitHub write path when integration tools are read-only, avoiding false refusals to carry out requested pull request updates, comments, or workflow actions.
+- Slack channel history reads return accumulated messages with explicit partial-result and continuation information instead of timing out and losing all results in busy channels.
+- Slack destination guidance distinguishes unlisted private channels from lost access and directs replies, including automation results, to the current conversation without requiring standalone channel discovery.
+
 ## 1.20.0 (2026-11-04)
 
 Roomote 1.20.0 adds MCP connection controls and testing, stops runaway agent activity, and includes security updates for redirects and static-file serving.

apps/docs/fast-sessions.mdx

@@ -380,7 +380,11 @@ channel-access checks. It does not infer access from the originating chat.
 
 Roomote uses one destination lookup and one send action for explicitly requested
 standalone messages. The lookup can return your linked Slack or Telegram account,
-linked people in shared Slack workspaces, and accessible Slack channels. Each
+linked people in shared Slack workspaces, and public Slack channels the Roomote
+app has joined. Private channels are not listed, so a missing channel does not
+mean Slack access was lost. Replies in the current conversation, including an
+automation's configured report channel, do not depend on finding that channel
+in the standalone destination lookup. Each
 lookup names one provider and destination kind. Self lookup resolves only your
 authenticated identity; people and channel lookup requires a targeted search or
 an exact destination reference. Results are bounded and include a continuation

apps/docs/providers/communications/slack.mdx

@@ -232,9 +232,12 @@ for example `@Roomote summarize this thread` or `@Roomote fix the failing CI
 job`. Replies in a Roomote-owned Slack thread continue that session; replies
 in an existing task-only thread continue the task.
 
-Roomote can read a bounded history from the current Slack channel, discover other
-channels in the same workspace, and post standalone updates to channels where
-the Roomote app is authorized. From another session surface, such as Telegram, you
+Roomote can read a bounded history from the current Slack channel, discover public
+channels the app has joined in the same workspace, and post standalone updates to
+authorized destinations. Private channels are not listed in the standalone
+destination lookup; their absence does not mean Slack access was lost. Replies
+in the current conversation, including an automation's configured report channel,
+do not depend on that lookup. From another session surface, such as Telegram, you
 can provide a Slack link or explicitly name Slack to read authorized context,
 then ask Roomote to send an update to an explicit workspace and destination.
 Roomote uses the same destination lookup and send action for your own linked Slack

package.json

@@ -1,6 +1,6 @@
 {
   "name": "roomote",
-  "version": "1.20.0",
+  "version": "1.20.1",
   "license": "FCL-1.0-ALv2",
   "packageManager": "pnpm@10.29.3",
   "engines": {