diff --git a/CHANGELOG.md b/CHANGELOG.md
index 542ffaafb..c9724bdbd 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,21 @@
 
 This file tracks product releases for Roomote (single monorepo version). Automated release entries are prepended by `pnpm run version`.
 
+## 1.19.5 (2026-10-29)
+
+Roomote 1.19.5 improves GitHub work across organizations and restores integration-key access for scheduled and manually run custom automations.
+
+### Highlights
+
+- Connect additional GitHub organizations and use HTTPS Git across repositories available to a task.
+- Start pull request reviews reliably when multiple GitHub organizations are connected.
+- Use existing integration keys in scheduled and manually run custom automations.
+
+### Patch changes
+
+- Scheduled and manually run custom automations can now use their creator's available personal and deployment-wide integration keys instead of finding an empty integration list. New key approvals still require a human turn, and webhook-triggered runs do not receive integration keys.
+- Work with GitHub repositories across organizations: Update GitHub now opens the account picker to add another installation, pull request reviews no longer fail to start when multiple organizations are connected, and tasks can clone, fetch, and push available repositories across installations using HTTPS Git. Task API and pull request delivery access retain their existing installation boundaries.
+
 ## 1.19.4 (2026-10-27)
 
 Roomote 1.19.4 expands model choice with GPT-6.1 Terra and Kimi K3.1 Pro, including Highspeed options on supported Kimi providers.
diff --git a/apps/docs/providers/source-control/github.mdx b/apps/docs/providers/source-control/github.mdx
index 6a0bd256e..d658777ce 100644
--- a/apps/docs/providers/source-control/github.mdx
+++ b/apps/docs/providers/source-control/github.mdx
@@ -255,6 +255,24 @@ the deployment's first installation. With more than one installation, scope a
 search to the organization or repository you mean so it runs under the right
 one.
 
+## Task Git access across installations
+
+<Note>
+Cross-installation task Git access is available starting with Roomote 1.19.5.
+</Note>
+
+A task with a primary GitHub repository can clone, fetch, and push other active
+GitHub repositories available to that task even when they belong to another
+installation of the configured app. Roomote supplies repository-scoped Git
+credentials for those additional installations. If an additional installation
+has lost access, its repositories can remain unavailable without blocking work
+on the primary repository.
+
+This applies to HTTPS Git operations. The task's `gh` CLI and primary API
+credential still use one installation; they do not automatically gain access
+to the other organizations. GitHub repositories explicitly listed together in
+an [environment](/environments) must still belong to one installation.
+
 ## Daily GitHub management
 
 Roomote can use GitHub's native tools directly, without starting a coding task:
@@ -262,7 +280,7 @@ pull request and issue edits, comments, replies and reactions, reviews, labels,
 branches, and small file changes. Their discovered descriptions and schemas
 define the supported arguments. These actions use the deployment GitHub App,
 require an active Roomote member, and run under a token that reaches only the
-repositories connected on that installation, the same boundary a coding task
+repositories connected on that installation, the same API boundary a coding task
 has. What the token may do there is set by the App's permissions on GitHub. No
 personal GitHub OAuth connection is required. Ask for the specific change and
 identify the repository and target issue, pull request, or comment. Every call
@@ -309,9 +327,9 @@ An environment-backed task can also push branches and create or update pull
 requests in another active GitHub repository connected to the same GitHub App
 installation, even when that repository is not part of the environment
 workspace. This write access does not automatically add the repository to the
-prepared workspace. Roomote rejects inactive repositories, repositories
-connected through another provider, and repositories that belong to a different
-GitHub App installation.
+prepared workspace. These task delivery tools reject inactive repositories,
+repositories connected through another provider, and repositories that belong
+to a different GitHub App installation.
 
 Read-only requests, creations, and additive label actions run directly. Before
 editing, replacing, assigning, clearing, moving, or deleting an item, Roomote
diff --git a/package.json b/package.json
index b924105bd..ec470dc34 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "roomote",
-  "version": "1.19.4",
+  "version": "1.19.5",
   "license": "FCL-1.0-ALv2",
   "packageManager": "pnpm@10.29.3",
   "engines": {