From 87babac0df5f5ee5ccd14f9f44198017ec3702a3 Mon Sep 17 00:00:00 2001
From: "claude[bot]" <41898282+claude[bot]@users.noreply.github.com>
Date: Sat, 24 Oct 2026 18:27:03 +0000
Subject: [PATCH] docs: Claude Code v2.1.310 - Code Review includes skills from
 REVIEW.md, mod images draw inside tmux

Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
---
 content/.metadata.json                        | 244 +++++++++---------
 content/en/docs/claude-code/artifacts.md      |   4 +-
 .../docs/claude-code/claude-apps-gateway.md   |  12 +-
 .../claude-code/claude-code-on-the-web.md     |   2 +-
 .../en/docs/claude-code/cloud-environments.md |   7 +-
 .../docs/claude-code/code-review-customize.md |  68 ++++-
 .../code-review-troubleshooting.md            |   3 +-
 .../claude-code/desktop-scheduled-tasks.md    |  25 +-
 content/en/docs/claude-code/env-vars.md       |   2 +-
 content/en/docs/claude-code/errors.md         |  47 +++-
 content/en/docs/claude-code/fast-mode.md      |  32 ++-
 content/en/docs/claude-code/hooks.md          |  23 +-
 .../docs/claude-code/llm-gateway-connect.md   |   5 +-
 content/en/docs/claude-code/mcp.md            |   2 +-
 content/en/docs/claude-code/model-config.md   |   9 +-
 content/en/docs/claude-code/network-config.md |   4 +-
 .../docs/claude-code/plugins/mods/gallery.md  |  29 ++-
 .../claude-code/plugins/mods/troubleshoot.md  |   2 +-
 content/en/docs/claude-code/routines.md       |  22 +-
 content/en/docs/claude-code/sandboxing.md     |  14 +-
 .../self-hosted-environments-configuration.md |  88 ++++++-
 .../self-hosted-environments-deploy.md        | 173 ++++++++++++-
 .../self-hosted-environments-quickstart.md    |   2 +
 .../self-hosted-environments-reference.md     |  14 +-
 .../claude-code/self-hosted-environments.md   |   5 +-
 .../en/docs/claude-code/settings-reference.md |  48 +++-
 .../en/docs/claude-code/terminal-config.md    |   3 +
 content/en/docs/claude-code/ultrareview.md    |   4 +-
 .../docs/claude-code/web-scheduled-tasks.md   |  22 +-
 ...k-settings-on-team-and-enterprise-plans.md |   2 +-
 .../10593882-share-and-unshare-chats.md       |   6 +-
 ...the-claude-lti-in-canvas-by-instructure.md |   2 +-
 ...being-asked-to-verify-my-payment-method.md |   2 +-
 .../11869629-use-claude-with-android-apps.md  |   2 +-
 ...or-team-and-seat-based-enterprise-plans.md |  10 +-
 .../12157520-claude-code-usage-analytics.md   |   2 +-
 .../support/12260368-use-incognito-chats.md   |   2 +-
 .../support/12293051-use-claude-in-xcode.md   |   2 +-
 ...age-usage-credits-for-paid-claude-plans.md |   2 +-
 ...6728-troubleshoot-claude-error-messages.md |   2 +-
 ...d-using-the-desktop-extension-allowlist.md |   8 +-
 .../12618689-use-claude-code-in-the-cloud.md  |   6 +-
 ...analytics-for-team-and-enterprise-plans.md |  24 +-
 .../12997503-team-plan-billing-faqs.md        |   2 +-
 .../13132885-set-up-single-sign-on-sso.md     |   8 +-
 ...3133195-set-up-jit-or-scim-provisioning.md |   6 +-
 ...1-configuring-session-security-settings.md |   6 +-
 .../13189465-log-in-to-your-claude-account.md |   2 +-
 ...13371040-log-in-to-your-console-account.md |   2 +-
 ...13641943-visual-and-interactive-content.md |   6 +-
 .../support/13837440-use-plugins-in-claude.md |   4 +-
 ...sync-works-for-enterprise-organizations.md |   4 +-
 ...t-a-default-model-for-your-organization.md |   2 +-
 ...nage-model-access-for-your-organization.md |   8 +-
 ...1-get-started-with-1password-for-claude.md |   2 +-
 ...rstanding-your-pro-or-max-plan-invoices.md |   2 +-
 ...16893491-get-started-with-smart-reports.md |  14 +-
 ...claude-in-google-docs-sheets-and-slides.md |   4 +-
 ...ooled-group-budgets-on-enterprise-plans.md |   2 +-
 .../17203415-set-up-claude-for-intune.md      |  22 +-
 .../8114491-get-started-with-claude.md        |   2 +-
 ...8230524-delete-or-rename-a-conversation.md |  16 +-
 .../support/8325618-paid-plan-billing-faqs.md |   2 +-
 ...nt-to-a-team-or-enterprise-organization.md |   2 +-
 ...77-how-can-i-create-and-manage-projects.md |   6 +-
 65 files changed, 804 insertions(+), 307 deletions(-)

diff --git a/content/.metadata.json b/content/.metadata.json
index 81cb82947f..affe3ef58f 100644
--- a/content/.metadata.json
+++ b/content/.metadata.json
@@ -1,7 +1,7 @@
 {
   "metadata": {
     "version": "2.0",
-    "fetch_date": "2026-10-24T14:09:44.424199Z",
+    "fetch_date": "2026-10-24T18:25:24.303414Z",
     "section": "all"
   },
   "items": [
@@ -5917,15 +5917,15 @@
       "url": "https://code.claude.com/docs/en/claude-code-on-the-web",
       "status": "success",
       "path": "en/docs/claude-code/claude-code-on-the-web.md",
-      "sha256": "ba4ec2855030fb9fcde17563affac810656005570827e369aaaf81cdfdbd3779",
-      "size": 44873
+      "sha256": "048976f7a49faf9e719ef3564f8feb4ad5b917625f4e8b8a7bb1b7fcf7929276",
+      "size": 44897
     },
     {
       "url": "https://code.claude.com/docs/en/routines",
       "status": "success",
       "path": "en/docs/claude-code/routines.md",
-      "sha256": "ade919df147c69b125bf6e2c6f87b913567702151473f7e4dee071cdb5d830cf",
-      "size": 44737
+      "sha256": "e0b273166fea5899fa1c0d898975938cc423eb1c8b0a1d4c0609ee105cf9c53f",
+      "size": 46689
     },
     {
       "url": "https://code.claude.com/docs/en/desktop-quickstart",
@@ -5959,8 +5959,8 @@
       "url": "https://code.claude.com/docs/en/desktop-scheduled-tasks",
       "status": "success",
       "path": "en/docs/claude-code/desktop-scheduled-tasks.md",
-      "sha256": "67a4ae6b458bcc850d10d2b0b2b1386be2a9025c175a1ea00dc42e6485a9cf7d",
-      "size": 14427
+      "sha256": "767737774bca5d317bded5b5363b718e6fa2f9022a54a93665571698b352aae0",
+      "size": 15722
     },
     {
       "url": "https://code.claude.com/docs/en/desktop-ios-simulator",
@@ -5980,8 +5980,8 @@
       "url": "https://code.claude.com/docs/en/ultrareview",
       "status": "success",
       "path": "en/docs/claude-code/ultrareview.md",
-      "sha256": "ede773031b7203c1edc24473d4e46adeb72434e21bfddacd09779565f5f6cb18",
-      "size": 20142
+      "sha256": "ccaee97adab0ddcc3c845cc1ee28eaee379b04e56061031b5b69444c014c22c5",
+      "size": 20120
     },
     {
       "url": "https://code.claude.com/docs/en/github-enterprise-server",
@@ -6008,8 +6008,8 @@
       "url": "https://code.claude.com/docs/en/code-review-customize",
       "status": "success",
       "path": "en/docs/claude-code/code-review-customize.md",
-      "sha256": "5720f8482766549c981d811c498e17d830ee4bda3904f1054a6a765707324d26",
-      "size": 11739
+      "sha256": "b35720423c8de61211f037f4a609b81ab5e41bb43825fda1a6dd7cf855f675ae",
+      "size": 16556
     },
     {
       "url": "https://code.claude.com/docs/en/code-review-pull-requests",
@@ -6029,8 +6029,8 @@
       "url": "https://code.claude.com/docs/en/code-review-troubleshooting",
       "status": "success",
       "path": "en/docs/claude-code/code-review-troubleshooting.md",
-      "sha256": "e0775b42a4b45a9d8793a779a202054f1c9d1d05d7c5afb43dc0e89fa7604fc0",
-      "size": 10563
+      "sha256": "1e82bd95bf6c1d3a3a8c7d6a9e1d909c1255c7876c61c76f93f12195e2dafaed",
+      "size": 10983
     },
     {
       "url": "https://code.claude.com/docs/en/security-guidance",
@@ -6127,8 +6127,8 @@
       "url": "https://code.claude.com/docs/en/mcp",
       "status": "success",
       "path": "en/docs/claude-code/mcp.md",
-      "sha256": "d48319ae5c571ac90820facca519f38b37796799962851ebd1e2545d5c0532c5",
-      "size": 150632
+      "sha256": "191eb66024fcd502afcc304747b84a25e0531a3d9fbdb89c71147f713ec76ba6",
+      "size": 150533
     },
     {
       "url": "https://code.claude.com/docs/en/skills",
@@ -6141,8 +6141,8 @@
       "url": "https://code.claude.com/docs/en/artifacts",
       "status": "success",
       "path": "en/docs/claude-code/artifacts.md",
-      "sha256": "a48ba61f9ef97e86fac25ff00f23e431f912a7aafc0ab3d17b4cc7d761b17f26",
-      "size": 42925
+      "sha256": "e4afc5fb601f82ab2d90def131325fd87ac93448baee1154c96babd16d53a3db",
+      "size": 42863
     },
     {
       "url": "https://code.claude.com/docs/en/hooks-guide",
@@ -6218,8 +6218,8 @@
       "url": "https://code.claude.com/docs/en/errors",
       "status": "success",
       "path": "en/docs/claude-code/errors.md",
-      "sha256": "bf901502940532ed4306a33fedd572ab445919fc401bef5d8ac859ce70809440",
-      "size": 581196
+      "sha256": "e7e040fc79e9742fdcb1c7e8b51a5c7c4fec41bd80919943cbb8357d789b40a1",
+      "size": 583873
     },
     {
       "url": "https://code.claude.com/docs/en/plugins/overview",
@@ -6337,8 +6337,8 @@
       "url": "https://code.claude.com/docs/en/plugins/mods/gallery",
       "status": "success",
       "path": "en/docs/claude-code/plugins/mods/gallery.md",
-      "sha256": "a06f15ccc2a86f34e5600acbec67103aebb555bd2badcf5863061ced8dfe64c3",
-      "size": 18662
+      "sha256": "2e4883e4ac8eb52c669ea8a22793a31fc67e7b87b97cfaeb53b63ca7a3c744bd",
+      "size": 20407
     },
     {
       "url": "https://code.claude.com/docs/en/plugins/mods/events",
@@ -6365,8 +6365,8 @@
       "url": "https://code.claude.com/docs/en/plugins/mods/troubleshoot",
       "status": "success",
       "path": "en/docs/claude-code/plugins/mods/troubleshoot.md",
-      "sha256": "6d342fd66857e982d1754474d471afabc1ddddb806fda145e2e77f181b708e73",
-      "size": 29849
+      "sha256": "3381d30c9ec852d78d38bc442fb1fe117defd3279e75ca06f049518dc4928069",
+      "size": 29821
     },
     {
       "url": "https://code.claude.com/docs/en/plugins/create-marketplace",
@@ -6533,8 +6533,8 @@
       "url": "https://code.claude.com/docs/en/network-config",
       "status": "success",
       "path": "en/docs/claude-code/network-config.md",
-      "sha256": "7644c49bc32233fa798ce796fd0388a8457d553bac6ed2427329a92001f4465d",
-      "size": 34788
+      "sha256": "b19677a0236f0b0fd755bec414a8fddcd46c3f069b5bce9939bf581d16f8dfcc",
+      "size": 34534
     },
     {
       "url": "https://code.claude.com/docs/en/corporate-launcher",
@@ -6561,8 +6561,8 @@
       "url": "https://code.claude.com/docs/en/claude-apps-gateway",
       "status": "success",
       "path": "en/docs/claude-code/claude-apps-gateway.md",
-      "sha256": "2661b44b59919124a99459f34e51aac73b5e38f14add593bd329caad8bf22c25",
-      "size": 62575
+      "sha256": "16a45584b9c31f06bbd9b84a18c35ea2371cc2efc08c1c4c032d35d5b090c351",
+      "size": 62597
     },
     {
       "url": "https://code.claude.com/docs/en/claude-apps-gateway-config",
@@ -6610,8 +6610,8 @@
       "url": "https://code.claude.com/docs/en/llm-gateway-connect",
       "status": "success",
       "path": "en/docs/claude-code/llm-gateway-connect.md",
-      "sha256": "27aef76484d6fddd9415a6b7c042fb3cd146d5ea566326d46e72de40d879e46f",
-      "size": 46254
+      "sha256": "712e0f6b85b2155e80fb6116dca1e8c2e1f0401980589cf0145cccc9c330ad63",
+      "size": 46707
     },
     {
       "url": "https://code.claude.com/docs/en/llm-gateway-rollout",
@@ -6701,8 +6701,8 @@
       "url": "https://code.claude.com/docs/en/settings-reference",
       "status": "success",
       "path": "en/docs/claude-code/settings-reference.md",
-      "sha256": "d359aa89b2adba5cdf14d3e2f57f51d57629cfec56732bffcb4e1b586589fc2c",
-      "size": 437384
+      "sha256": "01b3aacd50865f3146b7bb489e506a380573bf41a3176ec4e334d8e2b7d06330",
+      "size": 440010
     },
     {
       "url": "https://code.claude.com/docs/en/settings-example",
@@ -6736,8 +6736,8 @@
       "url": "https://code.claude.com/docs/en/sandboxing",
       "status": "success",
       "path": "en/docs/claude-code/sandboxing.md",
-      "sha256": "fc1b2dbb7cf8546c9212c9565f0be0827a898f7d03e1ad603a6f5bca183215ac",
-      "size": 103114
+      "sha256": "589325fa4c7318fcaea12da6f2c4fd0ee26633f2c43898fcebbd248e75f7de11",
+      "size": 104561
     },
     {
       "url": "https://code.claude.com/docs/en/sandbox-environments",
@@ -6750,36 +6750,36 @@
       "url": "https://code.claude.com/docs/en/cloud-environments",
       "status": "success",
       "path": "en/docs/claude-code/cloud-environments.md",
-      "sha256": "51d5be1ded0518c1423877743b6c4f53db7409cd2cc2b37629a3de9fedb6707e",
-      "size": 66129
+      "sha256": "762444b0dff275a0a511c374b0fe37a6a4c5f7fe30486836c4cfe1a4c6c5bd5a",
+      "size": 66332
     },
     {
       "url": "https://code.claude.com/docs/en/self-hosted-environments",
       "status": "success",
       "path": "en/docs/claude-code/self-hosted-environments.md",
-      "sha256": "583b13cb76e652503040e238bc23e9a81035c6ce76742c722cb4304654bed863",
-      "size": 21029
+      "sha256": "900ff49d19bd0c11eb1b3560b7ca0ad0b19699ce7ce668c01bba62ab6a68e08d",
+      "size": 21326
     },
     {
       "url": "https://code.claude.com/docs/en/self-hosted-environments-quickstart",
       "status": "success",
       "path": "en/docs/claude-code/self-hosted-environments-quickstart.md",
-      "sha256": "2463dedcfea04c720b2a7b1224ffaf9f502bb3368b4c9704f6fc72b5461e105b",
-      "size": 16094
+      "sha256": "677aca6a348047b5b4e475c199770ed6ea98aec12b388deb3bfddc65e181f33a",
+      "size": 16669
     },
     {
       "url": "https://code.claude.com/docs/en/self-hosted-environments-deploy",
       "status": "success",
       "path": "en/docs/claude-code/self-hosted-environments-deploy.md",
-      "sha256": "f731e29130d469a0e15283a2196b4d4d4261895ea59bca74bdff98ec4ff20c53",
-      "size": 102596
+      "sha256": "bcf39a81c00e9cf2af1216505ee1c7f92d13152142f75c99e1e83bed026c0136",
+      "size": 118848
     },
     {
       "url": "https://code.claude.com/docs/en/self-hosted-environments-configuration",
       "status": "success",
       "path": "en/docs/claude-code/self-hosted-environments-configuration.md",
-      "sha256": "136b34059dbb645b226b4ae6bfc4a568a5382605d1d9213348a36d94cfd0ed12",
-      "size": 88305
+      "sha256": "406a98f6564f4b91c6051777c2c3e11cefe3740a20f79f190f59d89ad2bc4213",
+      "size": 95195
     },
     {
       "url": "https://code.claude.com/docs/en/self-hosted-environments-testing",
@@ -6792,8 +6792,8 @@
       "url": "https://code.claude.com/docs/en/self-hosted-environments-reference",
       "status": "success",
       "path": "en/docs/claude-code/self-hosted-environments-reference.md",
-      "sha256": "8747211cf05bdb6e85499e26f7b054b2a5ff6ddf2028d42e5e36866187361e42",
-      "size": 54735
+      "sha256": "3b6710e0e7ba52f3a3539a46a963b064de2b2ab5cc140b845200ed4b5e56f753",
+      "size": 55083
     },
     {
       "url": "https://code.claude.com/docs/en/self-hosted-environments-identity",
@@ -6806,15 +6806,15 @@
       "url": "https://code.claude.com/docs/en/model-config",
       "status": "success",
       "path": "en/docs/claude-code/model-config.md",
-      "sha256": "8588cd62b893b3ac21c956e7cd979f32ba3380185be3714446aa0476df0da804",
-      "size": 125779
+      "sha256": "f67741ef4d7da190388917e978c5087839f5eebdd3723d19b7569abfdbfbe656",
+      "size": 126218
     },
     {
       "url": "https://code.claude.com/docs/en/fast-mode",
       "status": "success",
       "path": "en/docs/claude-code/fast-mode.md",
-      "sha256": "78f92b24b84c18fbc5bec23cef0e3dd9bc0ae89eea858370ab6f317aa18cb066",
-      "size": 21532
+      "sha256": "30d85ba4e84e96881fa0582e34fa1a7c916bb71d8e7bcbf69d0f6f07aa0f369e",
+      "size": 20980
     },
     {
       "url": "https://code.claude.com/docs/en/advisor",
@@ -6834,8 +6834,8 @@
       "url": "https://code.claude.com/docs/en/terminal-config",
       "status": "success",
       "path": "en/docs/claude-code/terminal-config.md",
-      "sha256": "2fbc85c440ada3cf559080ea8832589f806d11526c6fb36cd4ef20958dc19713",
-      "size": 26548
+      "sha256": "72ababcba94144866583daa723b17d737a583e73f2af6f039b3550e1b3054841",
+      "size": 26942
     },
     {
       "url": "https://code.claude.com/docs/en/fullscreen",
@@ -6890,8 +6890,8 @@
       "url": "https://code.claude.com/docs/en/env-vars",
       "status": "success",
       "path": "en/docs/claude-code/env-vars.md",
-      "sha256": "103e5e521a7f0893b65f93fd4184e1b06220a54b51bb3b6ad1070d24706a97d7",
-      "size": 185475
+      "sha256": "30e7f4222de5bbc8080db9634d9423a4a1e54100710ee6e9f94c2c6cbfbfdc7b",
+      "size": 185453
     },
     {
       "url": "https://code.claude.com/docs/en/tools-reference",
@@ -6918,8 +6918,8 @@
       "url": "https://code.claude.com/docs/en/hooks",
       "status": "success",
       "path": "en/docs/claude-code/hooks.md",
-      "sha256": "47ffc799070326108bbd3811db73d26f9a4cd68168078095d923a2ba710fdd8a",
-      "size": 279626
+      "sha256": "f81d3d61cd42f7892bee96084a09be6283bac1be09bc544b17f76545f5bed90c",
+      "size": 280780
     },
     {
       "url": "https://code.claude.com/docs/en/channels-reference",
@@ -9921,8 +9921,8 @@
       "url": "https://support.claude.com/en/articles/8114491-get-started-with-claude",
       "status": "success",
       "path": "support/8114491-get-started-with-claude.md",
-      "sha256": "405adc6010244556b70efce4fb2a255a815c47c77826bec6bb119760583d3b29",
-      "size": 5203
+      "sha256": "bb9a5fd808f3ecc6b35d0cbcf8e9c48b9438b353b1b4092830f16315d7380a5c",
+      "size": 5209
     },
     {
       "url": "https://support.claude.com/en/articles/8114494-how-up-to-date-is-claude-s-training-data",
@@ -9998,8 +9998,8 @@
       "url": "https://support.claude.com/en/articles/8230524-delete-or-rename-a-conversation",
       "status": "success",
       "path": "support/8230524-delete-or-rename-a-conversation.md",
-      "sha256": "5a4b9e17f60a067853e38c14a75d5ff4edbf210d7b561a5fff00c6fcf97636b5",
-      "size": 5883
+      "sha256": "1f2161e8e634c53e2d6f2b0115b89d6df9c4082c89442681f244bb5777f9c923",
+      "size": 5873
     },
     {
       "url": "https://support.claude.com/en/articles/8241126-upload-files-to-claude",
@@ -10068,8 +10068,8 @@
       "url": "https://support.claude.com/en/articles/8325618-paid-plan-billing-faqs",
       "status": "success",
       "path": "support/8325618-paid-plan-billing-faqs.md",
-      "sha256": "0349063bb1da8a0466be4b4e2493f7b026e3f6784404db99cfca117226ccf980",
-      "size": 4949
+      "sha256": "5081515f67b1d0411fca72628195151b0a4a3cdf6253fdefb59be4920f5003b8",
+      "size": 4955
     },
     {
       "url": "https://support.claude.com/en/articles/8325621-i-would-like-to-input-sensitive-data-into-my-chats-with-claude-who-can-view-my-conversations",
@@ -10306,8 +10306,8 @@
       "url": "https://support.claude.com/en/articles/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization",
       "status": "success",
       "path": "support/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization.md",
-      "sha256": "3894ef8d11206b926499a81aeb00d3682fecf0ec5b1b00569dd31ad0bcd44607",
-      "size": 10266
+      "sha256": "d0d1e083ff70c5fca1a982cf34c0518f7c6fe96bfa27e0dfcd47504b46aa3eae",
+      "size": 10268
     },
     {
       "url": "https://support.claude.com/en/articles/9301722-updates-to-our-acceptable-use-policy-now-usage-policy-consumer-terms-of-service-and-privacy-policy",
@@ -10348,8 +10348,8 @@
       "url": "https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects",
       "status": "success",
       "path": "support/9519177-how-can-i-create-and-manage-projects.md",
-      "sha256": "a92a2767ead6f36bf42a1ba4995b53422d99db8a606e60ee94b0ca61a99cbcd4",
-      "size": 9205
+      "sha256": "2b6c5492949d93411d25a9fe661b54afc322181efdf528e8df1bc6ad156a6d26",
+      "size": 9201
     },
     {
       "url": "https://support.claude.com/en/articles/9519189-manage-project-visibility-and-sharing",
@@ -10649,7 +10649,7 @@
       "url": "https://support.claude.com/en/articles/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans",
       "status": "success",
       "path": "support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md",
-      "sha256": "6a87cf29e348014852ad50d50d89dd126f80d2572d37080801b4501e9d1fe8dc",
+      "sha256": "f062d3f5e0af30b94e86f10ec865422d3c95978d4f5a44abb210a16bb9c31011",
       "size": 1036
     },
     {
@@ -10670,8 +10670,8 @@
       "url": "https://support.claude.com/en/articles/10593882-share-and-unshare-chats",
       "status": "success",
       "path": "support/10593882-share-and-unshare-chats.md",
-      "sha256": "12512e85d4802d1f9b66d22272e3a6b00976dc4cd315411890d786c8287d4636",
-      "size": 4016
+      "sha256": "5363692215f7b5c0033d34ac660cd01ebd7b8cf7d79fbe0555d4d582f8d43466",
+      "size": 4008
     },
     {
       "url": "https://support.claude.com/en/articles/10684626-enable-and-use-web-search",
@@ -10866,8 +10866,8 @@
       "url": "https://support.claude.com/en/articles/11725453-set-up-the-claude-lti-in-canvas-by-instructure",
       "status": "success",
       "path": "support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md",
-      "sha256": "0988a4a01a4aac9469ef01e7d99a06561099e076d2c5e5b6e941aa9e978ed618",
-      "size": 2748
+      "sha256": "3834e461d5c7cc7b98893ddc37e2391995dad87bddb75b2f967dba8967128676",
+      "size": 2754
     },
     {
       "url": "https://support.claude.com/en/articles/11732894-who-owns-and-manages-the-data-of-my-claude-for-education-account",
@@ -10887,8 +10887,8 @@
       "url": "https://support.claude.com/en/articles/11818288-why-am-i-being-asked-to-verify-my-payment-method",
       "status": "success",
       "path": "support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md",
-      "sha256": "7ea8ef89fbb082215905213e08e34f2c62a365f997af47a05f3e5e52423f8927",
-      "size": 814
+      "sha256": "864dcddea9cc8763c5210be2b88d24f759d47481a7aa3271f98891fe8a8d65e8",
+      "size": 816
     },
     {
       "url": "https://support.claude.com/en/articles/11825384-how-to-update-claude-for-ios",
@@ -10922,8 +10922,8 @@
       "url": "https://support.claude.com/en/articles/11869629-use-claude-with-android-apps",
       "status": "success",
       "path": "support/11869629-use-claude-with-android-apps.md",
-      "sha256": "28b47b56a4b4037dff13a7f6350d957a8ae993f4dd356bdf33167e5a2ec4809d",
-      "size": 13997
+      "sha256": "cb924b43966cbdb1eeecbc918f3357d42adcca6652512008fcc3904ff79fe5b7",
+      "size": 13991
     },
     {
       "url": "https://support.claude.com/en/articles/11932705-automated-security-reviews-in-claude-code",
@@ -10957,8 +10957,8 @@
       "url": "https://support.claude.com/en/articles/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans",
       "status": "success",
       "path": "support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md",
-      "sha256": "6d5e5d2a04903bbca644d2dc5637b27557a63c77c7aa5e7f79f3c5f2d361c0ea",
-      "size": 9707
+      "sha256": "e14451bbe633bd66478094f48833f07c45fa34672a0118ea421b6a577938f919",
+      "size": 9713
     },
     {
       "url": "https://support.claude.com/en/articles/12012173-get-started-with-claude-in-chrome",
@@ -11020,22 +11020,22 @@
       "url": "https://support.claude.com/en/articles/12157520-claude-code-usage-analytics",
       "status": "success",
       "path": "support/12157520-claude-code-usage-analytics.md",
-      "sha256": "25a64235ed1d8c49573f8ee4348e646cf8a8bb47500143697d17091bd5e718c2",
+      "sha256": "65d3ff91a42fb2f48e0e946cf8719278c42c6e948a41316f31db88ef97bd203a",
       "size": 6368
     },
     {
       "url": "https://support.claude.com/en/articles/12260368-use-incognito-chats",
       "status": "success",
       "path": "support/12260368-use-incognito-chats.md",
-      "sha256": "4bcbf642d35cd52c1896e2d354f1582863d98cd30ac2f92a52bd97a071ca21ca",
-      "size": 4374
+      "sha256": "0dff8bfc16a1f92c5ca0d57016156de44d331d60189b75ee5b05bdc3472bb7f5",
+      "size": 4376
     },
     {
       "url": "https://support.claude.com/en/articles/12293051-use-claude-in-xcode",
       "status": "success",
       "path": "support/12293051-use-claude-in-xcode.md",
-      "sha256": "e16b805d358eabf21ecfdf37d5593c4a10fa52f95e08c117c5cf556c77ac3a3c",
-      "size": 1907
+      "sha256": "6e2cefb77e04235d9b943d3eee8681899f5916d89a6247aa847bf67b42f7e0c9",
+      "size": 1905
     },
     {
       "url": "https://support.claude.com/en/articles/12304248-manage-api-key-environment-variables-in-claude-code",
@@ -11076,14 +11076,14 @@
       "url": "https://support.claude.com/en/articles/12429409-manage-usage-credits-for-paid-claude-plans",
       "status": "success",
       "path": "support/12429409-manage-usage-credits-for-paid-claude-plans.md",
-      "sha256": "d64820d700ac2186b93135524868181f31783e2c4dda251591c5649fda452004",
-      "size": 7968
+      "sha256": "a36a7564b2fb98e675af4de9efc0c199123e88e28ae6f6314af65a1ff9cbcea5",
+      "size": 7970
     },
     {
       "url": "https://support.claude.com/en/articles/12466728-troubleshoot-claude-error-messages",
       "status": "success",
       "path": "support/12466728-troubleshoot-claude-error-messages.md",
-      "sha256": "99b9d33ff0fd8952c2df14e0788417637dfce9b653de6d149f44464d9b7b181c",
+      "sha256": "2ff0eb6dee0abb1b4a6fc8cb04e2fd80a6a2a94e8b7f50bcdaa199d9ae1b2dc1",
       "size": 5141
     },
     {
@@ -11125,7 +11125,7 @@
       "url": "https://support.claude.com/en/articles/12592343-enabling-and-using-the-desktop-extension-allowlist",
       "status": "success",
       "path": "support/12592343-enabling-and-using-the-desktop-extension-allowlist.md",
-      "sha256": "54d2e80d846a74984e21c2fc04881e8953f91b07682a898e03b181fa6751780f",
+      "sha256": "7c4c30e9dbb2b648e488dfd4c0c9e3ac80d1bbdd2a309112390bd0e3f62a7fbe",
       "size": 5720
     },
     {
@@ -11139,8 +11139,8 @@
       "url": "https://support.claude.com/en/articles/12618689-use-claude-code-in-the-cloud",
       "status": "success",
       "path": "support/12618689-use-claude-code-in-the-cloud.md",
-      "sha256": "7f241706f02cd8e1e9aaeae00ae47660f58725a6ee9b51a56dbf600e9259cdb0",
-      "size": 11060
+      "sha256": "ae9bb63668c1da78d5057beee9e51851e6237f2eba7c0f1bd88b1cf675a714dd",
+      "size": 11056
     },
     {
       "url": "https://support.claude.com/en/articles/12622667-enterprise-configuration-for-claude-desktop",
@@ -11195,8 +11195,8 @@
       "url": "https://support.claude.com/en/articles/12883420-view-usage-analytics-for-team-and-enterprise-plans",
       "status": "success",
       "path": "support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md",
-      "sha256": "c2f72534257f1f0e5505beb08b21d29d5d3d42e287123131978fe7ba4035db2b",
-      "size": 15091
+      "sha256": "503e344d2a28885ddeb2dce3fdbee4f3606122319f689e41de2c47e3e10323d7",
+      "size": 15089
     },
     {
       "url": "https://support.claude.com/en/articles/12902405-claude-in-chrome-troubleshooting",
@@ -11244,8 +11244,8 @@
       "url": "https://support.claude.com/en/articles/12997503-team-plan-billing-faqs",
       "status": "success",
       "path": "support/12997503-team-plan-billing-faqs.md",
-      "sha256": "bbd0962d9a0cf086e8f67173c858af77594878cce238a667b07bd53d3b0026e9",
-      "size": 5413
+      "sha256": "988c13ded1f998c9ca0a5fc2f365a03e466e75a8be76649cbec35e99a5513b16",
+      "size": 5415
     },
     {
       "url": "https://support.claude.com/en/articles/13015708-access-the-compliance-api",
@@ -11293,15 +11293,15 @@
       "url": "https://support.claude.com/en/articles/13132885-set-up-single-sign-on-sso",
       "status": "success",
       "path": "support/13132885-set-up-single-sign-on-sso.md",
-      "sha256": "dba5f7c8990b10c68ae6412aa58efb530cad0d2f3644db970de6db9ea6ff2c1f",
+      "sha256": "34c85db3d212c3195fac5e6c29b392979988ae245f8de600fdb8a74c87a37d73",
       "size": 13645
     },
     {
       "url": "https://support.claude.com/en/articles/13133195-set-up-jit-or-scim-provisioning",
       "status": "success",
       "path": "support/13133195-set-up-jit-or-scim-provisioning.md",
-      "sha256": "70af3d6c60994c9f6d0971744a9aba9b2a0ed4e6ca662b8a2fd2846a363fd064",
-      "size": 22529
+      "sha256": "716e5b57f28767e4443f1d30ddf3a05c12225e64e0085d3b45e9df4750464de3",
+      "size": 22533
     },
     {
       "url": "https://support.claude.com/en/articles/13133750-manage-members-on-team-and-enterprise-plans",
@@ -11328,8 +11328,8 @@
       "url": "https://support.claude.com/en/articles/13163631-configuring-session-security-settings",
       "status": "success",
       "path": "support/13163631-configuring-session-security-settings.md",
-      "sha256": "2e1655cd04821815d06912f1dd3f93b7421038b6c79ec71e7ff2156628cc34a2",
-      "size": 3699
+      "sha256": "85465beae109310970585b77beadbf0a6c60e1be22a902369d7436d52fc27f32",
+      "size": 3701
     },
     {
       "url": "https://support.claude.com/en/articles/13171706-crisis-helpline-support-in-claude",
@@ -11342,8 +11342,8 @@
       "url": "https://support.claude.com/en/articles/13189465-log-in-to-your-claude-account",
       "status": "success",
       "path": "support/13189465-log-in-to-your-claude-account.md",
-      "sha256": "918250620ae06e56932797b8dc52bc0f50a4e2f5fc7b3d242dc01e341ecd35c6",
-      "size": 7039
+      "sha256": "e21ff48c94f64f50aeb7062d5e10cad4bd776cfab9847ea13363368b36ef53fb",
+      "size": 7041
     },
     {
       "url": "https://support.claude.com/en/articles/13198485-enforce-network-level-access-control-with-tenant-restrictions",
@@ -11405,8 +11405,8 @@
       "url": "https://support.claude.com/en/articles/13371040-log-in-to-your-console-account",
       "status": "success",
       "path": "support/13371040-log-in-to-your-console-account.md",
-      "sha256": "468d2fe7eccbf71848309dcc2b3fb7c78483a12a316ba659fcaf2f42b2b49cc1",
-      "size": 4609
+      "sha256": "da778405d4d01ff6b099e5188996338ea6202ed85fcc5d778d0977736f23cecc",
+      "size": 4613
     },
     {
       "url": "https://support.claude.com/en/articles/13393991-purchase-and-manage-seats-on-enterprise-plans",
@@ -11461,8 +11461,8 @@
       "url": "https://support.claude.com/en/articles/13641943-visual-and-interactive-content",
       "status": "success",
       "path": "support/13641943-visual-and-interactive-content.md",
-      "sha256": "0e2d03c82db97fa90a378fa21f5fc8c0948be163e520446346453e91802490a2",
-      "size": 6513
+      "sha256": "418fd6002077786752a022be94b6012ea18d553d4557666f79d645aa01ff3ea3",
+      "size": 6511
     },
     {
       "url": "https://support.claude.com/en/articles/13663666-use-visual-and-interactive-content-on-team-and-enterprise-plans",
@@ -11517,8 +11517,8 @@
       "url": "https://support.claude.com/en/articles/13837440-use-plugins-in-claude",
       "status": "success",
       "path": "support/13837440-use-plugins-in-claude.md",
-      "sha256": "7c876c9380981b77ed98189296602b50583732f49f7b4b65fcd776bcc93390c9",
-      "size": 15185
+      "sha256": "b2c01220addb96898906cbcf49b609779d8afe15858af8e6214010d62bfc7d9f",
+      "size": 15189
     },
     {
       "url": "https://support.claude.com/en/articles/13854387-schedule-recurring-tasks-in-claude-cowork",
@@ -11706,8 +11706,8 @@
       "url": "https://support.claude.com/en/articles/14499648-how-scim-sync-works-for-enterprise-organizations",
       "status": "success",
       "path": "support/14499648-how-scim-sync-works-for-enterprise-organizations.md",
-      "sha256": "482aecf5c42ecc38364cb87f5aefa69e54acabe273b202a4baee719a182323ba",
-      "size": 7672
+      "sha256": "98ce6cff39dfe747bceaaf041bf026f1775910c6fee19eb1b09d25caa75fa1df",
+      "size": 7676
     },
     {
       "url": "https://support.claude.com/en/articles/14503520-available-beta-and-research-preview-features",
@@ -11930,8 +11930,8 @@
       "url": "https://support.claude.com/en/articles/15330088-set-a-default-model-for-your-organization",
       "status": "success",
       "path": "support/15330088-set-a-default-model-for-your-organization.md",
-      "sha256": "13897f1ca7162da6c38be3d14fcc109c52e0ac3a000708b1a3b1b77046dcbc9a",
-      "size": 11315
+      "sha256": "7d9a506fda2491b1657cce37fa3e70ede6c2748e8aae996b096d1b41144bb177",
+      "size": 11311
     },
     {
       "url": "https://support.claude.com/en/articles/15330651-claude-enterprise-admin-api-reference-guide",
@@ -12042,8 +12042,8 @@
       "url": "https://support.claude.com/en/articles/15694740-manage-model-access-for-your-organization",
       "status": "success",
       "path": "support/15694740-manage-model-access-for-your-organization.md",
-      "sha256": "d654c0d0ed9b08b55d32ab5cdca5156a1c507508e7c794bcd17db6d93b4a5e12",
-      "size": 10344
+      "sha256": "0fc799e4ce559f66226abc78e449a69dcfd48ece635be0eb95d6af0e5788eb43",
+      "size": 10338
     },
     {
       "url": "https://support.claude.com/en/articles/15707726-using-claude-for-legal-work-privilege-confidentiality-and-how-to-think-about-configuration",
@@ -12077,8 +12077,8 @@
       "url": "https://support.claude.com/en/articles/15936181-get-started-with-1password-for-claude",
       "status": "success",
       "path": "support/15936181-get-started-with-1password-for-claude.md",
-      "sha256": "025b66cf2cedd674e889371ffceb9eed358b10fbea340c3c44e034abc8a4943b",
-      "size": 5060
+      "sha256": "a3f701b1beb38a0ea424d3c20f3e6b3868a5a693d42db3648712be2364894afd",
+      "size": 5058
     },
     {
       "url": "https://support.claude.com/en/articles/16049681-why-claude-switched-models-in-your-conversation-with-opus-5-or-opus-5-5",
@@ -12126,7 +12126,7 @@
       "url": "https://support.claude.com/en/articles/16607638-understanding-your-pro-or-max-plan-invoices",
       "status": "success",
       "path": "support/16607638-understanding-your-pro-or-max-plan-invoices.md",
-      "sha256": "680a350498bc847281f748226e6bd15a96207745e65a6bd6b00f8bdd44564962",
+      "sha256": "2c84ae3ea1729ed0d17163ccaf6c211afed8504c66746364484ff6d264c5815f",
       "size": 5832
     },
     {
@@ -12210,8 +12210,8 @@
       "url": "https://support.claude.com/en/articles/16893491-get-started-with-smart-reports",
       "status": "success",
       "path": "support/16893491-get-started-with-smart-reports.md",
-      "sha256": "2c1018ee4e6ba969af9123be030273d4d3e845a399af5911a1f36162f32142d9",
-      "size": 15969
+      "sha256": "381ea1ffc959494ed0868b481f4ed384a375b48f992d81e2ab4078236ccd6d37",
+      "size": 15965
     },
     {
       "url": "https://support.claude.com/en/articles/16923645-get-started-with-claude-docs",
@@ -12231,8 +12231,8 @@
       "url": "https://support.claude.com/en/articles/16951679-use-claude-in-google-docs-sheets-and-slides",
       "status": "success",
       "path": "support/16951679-use-claude-in-google-docs-sheets-and-slides.md",
-      "sha256": "59425431ea7b69ecffa079bb8d000c1b563c74409d1698b3c3075daaa2b53c4b",
-      "size": 21892
+      "sha256": "1ab6cee91663544d43bda75773d4039f0b00653ef1287e1fee274d5f4ede40eb",
+      "size": 21890
     },
     {
       "url": "https://support.claude.com/en/articles/16952184-set-up-salesforce-in-claude-for-your-organization",
@@ -12259,7 +12259,7 @@
       "url": "https://support.claude.com/en/articles/17005973-manage-pooled-group-budgets-on-enterprise-plans",
       "status": "success",
       "path": "support/17005973-manage-pooled-group-budgets-on-enterprise-plans.md",
-      "sha256": "baac9a85da282b2546b63786f17c69a7b60f138305d99ad885ad15013cd15dd7",
+      "sha256": "2b1ee3092c4acb20fa98895f5ed0be765d1fef96c8793fd6c19cfd7ae9065883",
       "size": 6982
     },
     {
@@ -12308,8 +12308,8 @@
       "url": "https://support.claude.com/en/articles/17203415-set-up-claude-for-intune",
       "status": "success",
       "path": "support/17203415-set-up-claude-for-intune.md",
-      "sha256": "e332b2df53b1a593c0d19a49668b5437d823d2d608d89cf9356a74bee0052bb5",
-      "size": 11381
+      "sha256": "b1d6c66d2db7ca7708b9314b609c085334150ce879577d8197f379d149e75c38",
+      "size": 11379
     },
     {
       "url": "https://support.claude.com/en/articles/17318731-use-claude-code-local-mode-and-claude-cowork-local-mode-on-a-hipaa-ready-enterprise-plan",
@@ -14422,8 +14422,8 @@
       "url": "https://code.claude.com/docs/en/web-scheduled-tasks",
       "status": "success",
       "path": "en/docs/claude-code/web-scheduled-tasks.md",
-      "sha256": "ade919df147c69b125bf6e2c6f87b913567702151473f7e4dee071cdb5d830cf",
-      "size": 44737
+      "sha256": "e0b273166fea5899fa1c0d898975938cc423eb1c8b0a1d4c0609ee105cf9c53f",
+      "size": 46689
     },
     {
       "url": "https://code.claude.com/docs/en/agent-sdk/slash-commands",
diff --git a/content/en/docs/claude-code/artifacts.md b/content/en/docs/claude-code/artifacts.md
index 6a41793b54..0517f515bd 100644
--- a/content/en/docs/claude-code/artifacts.md
+++ b/content/en/docs/claude-code/artifacts.md
@@ -340,9 +340,7 @@ Open the published artifact in a desktop browser to review the artboards. Select
 
 Claude Docs reaches Claude Code as a claude.ai [connector](https://code.claude.com/docs/en/mcp.md#use-mcp-servers-from-claude-ai) rather than a command. When it's connected, `/mcp` lists it as `claude.ai Claude Docs`. A request for a document meant for other people then goes to Claude Docs instead of an artifact page: a spec, a proposal, or a write-up of the plan you worked through in the session. Claude gives you the doc's link when it's drafted.
 
-A document that belongs in the codebase, such as a README, stays a file. To get a file for something Claude would otherwise put in Claude Docs, name the format, such as `.docx` or a Markdown file in the repository.
-
-To turn the connector off, add `claude.ai Claude Docs` to `deniedMcpServers` or use the `/mcp` toggle, both described in [Disable claude.ai connectors](https://code.claude.com/docs/en/mcp.md#disable-claude-ai-connectors).
+A document that belongs in the codebase, such as a README, stays a file. To get a file for something Claude would otherwise put in Claude Docs, name the format, such as `.docx` or a Markdown file in the repository. To turn off only the `claude.ai Claude Docs` connector, see [Disable claude.ai connectors](https://code.claude.com/docs/en/mcp.md#disable-claude-ai-connectors).
 
 ## Page constraints
 
diff --git a/content/en/docs/claude-code/claude-apps-gateway.md b/content/en/docs/claude-code/claude-apps-gateway.md
index a001ae7872..17bd749fef 100644
--- a/content/en/docs/claude-code/claude-apps-gateway.md
+++ b/content/en/docs/claude-code/claude-apps-gateway.md
@@ -458,17 +458,19 @@ Under the default first-wins setting, an admin value blocks the parent's only wh
 
 #### How hook and skill keys in parent settings take effect
 
-If you pass `disableAllHooks: true` as a parent setting through the Agent SDK's `managedSettings` option, not every hook stops. Your [SDK hook callbacks](https://code.claude.com/docs/en/agent-sdk/hooks.md) still run, and so do the administrator's hooks, which your application can't switch off.
+Keys your application passes in the Agent SDK's [`managedSettings`](https://code.claude.com/docs/en/agent-sdk/typescript#options) option are parent settings. On a machine where an administrator deploys managed settings, Claude Code ignores parent settings unless the administrator [lets an embedding host add policy](https://code.claude.com/docs/en/managed-settings.md#let-an-embedding-host-add-policy).
 
-On a machine where an administrator deploys managed settings, Claude Code ignores parent settings unless the administrator [lets an embedding host add policy](https://code.claude.com/docs/en/managed-settings.md#let-an-embedding-host-add-policy).
+If you pass [`disableAllHooks: true`](https://code.claude.com/docs/en/settings-reference#disableallhooks) in `managedSettings`:
+
+* **Stop**: user, project, and local hooks, plus hooks declared in agent frontmatter or in the SDK's [`settings` option](https://code.claude.com/docs/en/agent-sdk/typescript#options).
+* **Keep running**: your application's [SDK hook callbacks](https://code.claude.com/docs/en/agent-sdk/hooks.md) and an administrator's hooks from managed settings. Your application can't turn the administrator's hooks off.
 
 | What you pass | What happens |
 | :- | :- |
-| `disableAllHooks: true` | Treated as `allowManagedHooksOnly: true`, so the hooks listed as [blocked under `allowManagedHooksOnly`](https://code.claude.com/docs/en/settings-reference#what-runs-under-allowmanagedhooksonly) stop, and so do hooks in the SDK's [`settings` option](https://code.claude.com/docs/en/agent-sdk/typescript#options). |
-| [`disableSkillShellExecution: true`](https://code.claude.com/docs/en/settings-reference#disableskillshellexecution) | Takes effect. |
+| `hooks`, or `allowedHttpHookUrls` or `httpHookAllowedEnvVars` with entries | Claude Code ignores the key. Use the SDK `settings` option instead. |
 | `allowedHttpHookUrls: []` | Takes effect unless the administrator defines `hooks` or enables a plugin. No HTTP hook runs, except for URLs another settings source lists. |
 | `httpHookAllowedEnvVars: []` | Takes effect unless the administrator defines `hooks` or enables a plugin. HTTP hook headers can include only environment variables another settings source lists. |
-| `allowedHttpHookUrls` or `httpHookAllowedEnvVars` with entries | Claude Code ignores it, since merging would widen an administrator's list. Use the SDK `settings` option instead. |
+| [`disableSkillShellExecution: true`](https://code.claude.com/docs/en/settings-reference#disableskillshellexecution) | Takes effect. |
 
 Passing these keys in `managedSettings` requires Claude Code v2.1.309 or later, or TypeScript Agent SDK v0.3.309 or later.
 
diff --git a/content/en/docs/claude-code/claude-code-on-the-web.md b/content/en/docs/claude-code/claude-code-on-the-web.md
index a4dec44c8e..78cc12a1a5 100644
--- a/content/en/docs/claude-code/claude-code-on-the-web.md
+++ b/content/en/docs/claude-code/claude-code-on-the-web.md
@@ -8,7 +8,7 @@
 
 > [!NOTE]
 >
-> Cloud sessions are available on Pro, Max, and Team plans, and for Enterprise users with premium seats or Chat + Claude Code seats. If your Enterprise organization manages your access with [custom roles](https://support.claude.com/en/articles/13930452), you also need a role that includes the cloud sessions permission. Ask an Owner to check your roles and add it at [**Organization settings > Roles**](https://claude.ai/admin-settings/roles) if it's missing.
+> Cloud sessions are available on Pro, Max, and Team plans, and for Enterprise users with premium seats or Chat + Claude Code seats. If [custom roles](https://support.claude.com/en/articles/13930452) govern your access, you also need a role with the cloud sessions permission to start sessions on Anthropic's infrastructure from the browser, apps, or terminal. Ask an Owner to add it to one of your roles at [**Organization settings > Roles**](https://claude.ai/admin-settings/roles).
 
 A cloud session is a Claude Code session that runs on cloud infrastructure instead of on your machine. By default it runs on infrastructure Anthropic manages, or on your organization's [self-hosted environment](https://code.claude.com/docs/en/self-hosted-environments) when routed there. The session keeps running after you close your laptop, and you can check on it or steer it from any device. It counts toward your plan's usage limits alongside the rest of your Claude and Claude Code usage, and there's no separate charge for the cloud VM.
 
diff --git a/content/en/docs/claude-code/cloud-environments.md b/content/en/docs/claude-code/cloud-environments.md
index aff695ba2f..a78ac2c3a5 100644
--- a/content/en/docs/claude-code/cloud-environments.md
+++ b/content/en/docs/claude-code/cloud-environments.md
@@ -109,7 +109,7 @@ These requirements decide whether you can add a secret and whether the agent pro
 
 #### Add a secret
 
-You add secrets one at a time, and you can't edit a secret after you add it. To change a secret's hosts or value, delete it and add it again.
+You add secrets one at a time. To change a secret's hosts or value, delete it and add it again.
 
 To add a secret to a [shared environment](#organization-shared-environments), open it for editing from the **Cloud environments** page in [admin settings](https://claude.ai/admin-settings), then continue from step 2 in its **Network secrets** section. If you're on a Team plan and don't hold an [organization admin role](#requirements), follow step 1 on your own environment, then [fill in the shorter form](#add-a-secret-without-the-role).
 
@@ -119,7 +119,7 @@ To add a secret to a [shared environment](#organization-shared-environments), op
 
 **2. Add the secret**
 
-Select **Add secret** and fill in the form. Keep the default **Secret type**, **Bearer**, for an API key that travels in a request header, and fill in these fields:
+Select **Add secret**, labeled **Add** in admin settings, and fill in the form. Keep the default **Secret type**, **Bearer**, for an API key that travels in a request header, and fill in these fields:
 
 * **Name**: a label for the secret, such as `Internal billing API`
 * **Allowed websites**: the API's hosts, such as `api.example.com`. A leading `*.` matches every subdomain
@@ -443,11 +443,12 @@ apt update && apt install -y shellcheck
 
 ### Script requirements
 
-A setup script has three constraints to write around:
+A setup script has four constraints to write around:
 
 * **Exit zero**: if the script exits non-zero, the session fails to start. Append `|| true` to non-critical commands so an intermittent install failure doesn't block the session.
 * **Finish within five minutes**: keep the script's total runtime under roughly five minutes so the [environment cache](#environment-caching) can build. When setup takes longer than that, the environment isn't cached. Run independent installs in parallel with `&` and `wait`, and move any single download that won't fit into a [SessionStart hook](#setup-scripts-vs-sessionstart-hooks) that launches it in the background. If new sessions stall or fail during setup, see [New sessions hang or time out during setup](https://code.claude.com/docs/en/web-quickstart.md#new-sessions-hang-or-time-out-during-setup).
 * **Network access for installs**: package installs need to reach registries. The default **Trusted** level covers [common package registries](#default-allowed-domains) including npm, PyPI, RubyGems, and crates.io; with **None** network access, installs fail.
+* **The environment's variables aren't set yet**: the script runs before the session sets the environment's [environment variables](#set-environment-variables). Set any value the script needs in the script itself.
 
 ### Environment caching
 
diff --git a/content/en/docs/claude-code/code-review-customize.md b/content/en/docs/claude-code/code-review-customize.md
index c3b9fa9781..4f24e87299 100644
--- a/content/en/docs/claude-code/code-review-customize.md
+++ b/content/en/docs/claude-code/code-review-customize.md
@@ -123,13 +123,73 @@ Code Review includes the files when it reads `REVIEW.md` from a protected branch
 
 When a review doesn't apply an included file, check each of these:
 
-* **Location**: move the file to the repository root. A path into a subdirectory such as `@docs/review-rules.md` isn't included.
+* **Location**: move the file to the repository root. Except for a [skill file](#include-a-skill-file), a path into a subdirectory such as `@docs/review-rules.md` isn't included.
 * **Name**: match the file name exactly, including case, and use a name without spaces. A line whose name matches no file beside `REVIEW.md` stays in `REVIEW.md` as plain text, and the check run doesn't report it as a skipped include.
-* **One level**: list every file in the root `REVIEW.md`. An `@` line in an included file or in a subdirectory `REVIEW.md` stays as plain text, and a Markdown link to another file isn't an include.
+* **One level**: list every file in the root `REVIEW.md`. An `@` line in an included file or in a subdirectory `REVIEW.md` stays as plain text ([skill files differ](#include-a-skill-file)), and a Markdown link to another file isn't an include.
 * **Limits**: include at most eight different files, and keep `REVIEW.md` and the files it includes under 150,000 bytes combined. A file that would reach the byte limit is skipped whole, not cut short. The check run reports how many include lines it skipped for either limit.
-* **Links**: keep Markdown links at 64 or fewer across `REVIEW.md` and the files it includes. Links to `http`, `https`, or `mailto` addresses and to `#` anchors don't count. Past that limit, the review skips your whole root `REVIEW.md`, not only the included files. The check run then [says the instructions weren't applied](https://code.claude.com/docs/en/code-review-troubleshooting.md#the-check-run-mentions-review-md).
+* **Links**: keep Markdown links at 64 or fewer across `REVIEW.md` and the files it includes. Links to `http`, `https`, or `mailto` addresses and to `#` anchors don't count, and neither do links in a [skill file](#include-a-skill-file). Past that limit, the review skips your whole root `REVIEW.md`, not only the included files. The check run then [says the instructions weren't applied](https://code.claude.com/docs/en/code-review-troubleshooting.md#the-check-run-mentions-review-md).
 * **Merged copy**: merge the included file into the [branch `REVIEW.md` is read from](#which-branch-review-md-is-read-from). The review reads both from the same commit, never from the pull request's own changes.
 
+### Include a skill file
+
+To have reviews follow guidance you keep in a [skill](https://code.claude.com/docs/en/skills.md), include the skill's `SKILL.md` in your root `REVIEW.md`. Code Review doesn't run skills.
+
+Add `@` and the path to `SKILL.md`, in the form `.claude/skills/<folder>/SKILL.md`, on a line of its own:
+
+```markdown theme={null}
+# Review instructions
+
+Report at most five Nits per review.
+
+@.claude/skills/api-review/SKILL.md
+
+Treat any change under `migrations/` as Important.
+```
+
+Protect the [branch that `REVIEW.md` is read from](#which-branch-review-md-is-read-from), because Code Review includes a skill file only when it reads `REVIEW.md` from a protected branch. The skill file counts toward the limits of eight files and 150,000 bytes, and has its own limit of 30,000 bytes.
+
+#### Write a skill line that Code Review includes
+
+Use a folder name without spaces. A line with a space in its path stays in `REVIEW.md` as plain text, and the check run doesn't report it as a skipped include.
+
+If the `@` line for a skill breaks one of the rules below, Code Review doesn't include the skill from that line:
+
+* **Path**: write the path as `.claude/skills/<folder>/SKILL.md` from the repository root, with the skill's folder directly under `skills/`. Unlike a file name at the root, a path of this form that matches no file is skipped and counted.
+* **Source**: copy guidance from any other file under `.claude/`, or from a [bundled, personal, or plugin skill](https://code.claude.com/docs/en/skills.md#where-skills-live), into a file beside `REVIEW.md`. You can't include those directly.
+* **File**: commit `SKILL.md` as a regular text file. Code Review doesn't follow a symbolic link, whether the link is the file or a folder in its path.
+* **Size**: keep `SKILL.md` at 30,000 bytes or less, frontmatter included
+* **Count**: write at most eight skill lines. A repeated line counts again toward the eight.
+* **Blocks in `REVIEW.md`**: keep the `@` line out of code fences. Close every HTML comment and every `<pre>`, `<script>`, `<style>`, or `<textarea>` block above it.
+
+When Code Review skips a skill line for breaking the File, Size, Count, or Blocks rule, the check run's [message about skipped include lines](https://code.claude.com/docs/en/code-review-troubleshooting.md#the-check-run-mentions-review-md) counts it. The message appears only when the review applies `REVIEW.md` from a protected branch.
+
+#### Check what a review gets from a skill
+
+When the skill is included, a review gets the body of `SKILL.md` and nothing else from the skill, so check the skill against the list below.
+
+* **Frontmatter**: repeat in the body anything a review needs from the [frontmatter](https://code.claude.com/docs/en/skills.md#frontmatter-reference), for example the conditions that `description` gives for using the skill
+* **Injected commands**: write out what a [`!` command](https://code.claude.com/docs/en/skills#inject-dynamic-context) would supply. Code Review doesn't run the command, and replaces the whole line or block that holds it with a placeholder.
+* **Substitutions**: replace `$ARGUMENTS` and other [substitutions](https://code.claude.com/docs/en/skills.md#available-string-substitutions) with fixed text, because a review passes no arguments and leaves them as written
+* **Supporting files**: copy what a review needs into `SKILL.md`, because Code Review doesn't load scripts, linked files, or `@file` references
+* **Exclusions and Nit caps**: write instructions that exclude findings or cap Nits in `REVIEW.md` or a file beside it, not in the skill. Code Review doesn't accept a skill's text as the reason for either.
+* **Links to repository files**: state in words what a link or `@file` reference points to. The review sees the path as plain text or as a placeholder.
+
+If you edit the skill's `!` commands, `$ARGUMENTS`, or links, you also change how it works in Claude Code. If your team relies on those, copy the guidance into a file beside `REVIEW.md` and include that file in place of the skill.
+
+#### Characters that Code Review changes in skill text
+
+Code Review changes some characters in the skill's text, so your code samples reach a review in the form below.
+
+```text theme={null}
+In SKILL.md:       Use `items[0]`, never `List<String>`.
+The review reads:  Use ˋitems(0)ˋ, never ˋList< String>ˋ.
+
+In SKILL.md:       Run `ps | grep api` and ask @alice.
+The review reads:  Run ˋps ¦ grep apiˋ and ask @ alice.
+```
+
+Where a rule depends on one of those characters, state it in words too.
+
 ### Which branch REVIEW\.md is read from
 
 Code Review reads `REVIEW.md` from the pull request's base branch or from the default branch, never from the pull request's own changes. To change review behavior, merge the `REVIEW.md` change first.
@@ -140,6 +200,8 @@ Keep `REVIEW.md` on your default branch and protect that branch. When a review r
 * Excluding paths, files, or classes of issue
 * Capping nit comments
 
+Write exclusions and Nit caps in `REVIEW.md` or a file beside it, not in an [included skill](#include-a-skill-file).
+
 #### What counts as branch protection
 
 Code Review counts these settings as protection:
diff --git a/content/en/docs/claude-code/code-review-troubleshooting.md b/content/en/docs/claude-code/code-review-troubleshooting.md
index d199f309b5..d1b89d30c1 100644
--- a/content/en/docs/claude-code/code-review-troubleshooting.md
+++ b/content/en/docs/claude-code/code-review-troubleshooting.md
@@ -67,7 +67,7 @@ If the check run title says issues were found but you don't see inline review co
 
 ## The check run mentions REVIEW\.md
 
-These are three of the messages a check run can carry about `REVIEW.md`:
+These are four of the messages a check run can carry about `REVIEW.md`:
 
 * **"This review applied the repository's review instructions (REVIEW\.md) from its default branch, which is not protected against direct pushes."**: the review read the root file only. See [Which branch REVIEW.md is read from](https://code.claude.com/docs/en/code-review-customize.md#which-branch-review-md-is-read-from) for what protecting the branch changes.
 * **"were not applied to this review: branch protection could not be confirmed"**: the review read no `REVIEW.md`.
@@ -75,6 +75,7 @@ These are three of the messages a check run can carry about `REVIEW.md`:
   * **Too many links**: it carries more than 64 Markdown links. Cut links to [64 or fewer](https://code.claude.com/docs/en/code-review-customize.md#include-other-files-in-review-md).
   * **A link the review can't parse**: it has a malformed Markdown link. Fix or remove the link.
   * **A link to a changed file**: it links to a file or folder this pull request changes, and the review couldn't leave out only the lines with that link. Write the rule in `REVIEW.md` itself.
+* **"include line(s) in the root REVIEW\.md were skipped on this review"**: your root `REVIEW.md` applied, but the files those lines name didn't. Check the lists under [Include other files in REVIEW.md](https://code.claude.com/docs/en/code-review-customize.md#include-other-files-in-review-md) and, for a skill, under [Include a skill file](https://code.claude.com/docs/en/code-review-customize.md#include-a-skill-file).
 
 ## Setup problems
 
diff --git a/content/en/docs/claude-code/desktop-scheduled-tasks.md b/content/en/docs/claude-code/desktop-scheduled-tasks.md
index dc901d2e71..cd15232cc0 100644
--- a/content/en/docs/claude-code/desktop-scheduled-tasks.md
+++ b/content/en/docs/claude-code/desktop-scheduled-tasks.md
@@ -15,6 +15,10 @@ The Desktop app's **Scheduled tasks** page lists both local scheduled tasks and
 
 This page covers local scheduled tasks; for cloud scheduled tasks and their trigger options, see [Automate work with scheduled tasks](https://code.claude.com/docs/en/routines.md).
 
+> [!NOTE]
+>
+> If your app shows the feature under its [earlier name](https://code.claude.com/docs/en/routines.md#where-the-name-routines-still-appears), click **Routines** wherever this page says **Scheduled** and **New routine** where it says **New task**.
+
 ## Compare scheduling options
 
 Claude Code offers three ways to schedule recurring or one-off work:
@@ -45,11 +49,15 @@ Local scheduled tasks require Claude Desktop 1.1.5368 or later.
 
 **1. Open the Scheduled tasks page**
 
-In the [**Code** tab](https://code.claude.com/docs/en/desktop.md), click **Scheduled** in the sidebar or in the sidebar's **More** menu.
+In the [**Code** tab](https://code.claude.com/docs/en/desktop.md), click **Scheduled** in the sidebar or in the sidebar's **More** menu. If the sidebar shows **Routines** instead of **Scheduled**, click **Routines**, then click **New routine**, and continue with [Full-page form](#full-page-form).
 
 **2. Start a new task**
 
-Click **New task**. If a menu opens with **Create with Claude** and **Set up manually**, select **Set up manually**. The **New scheduled task** dialog opens. If **Only on this computer** is at the top of the dialog, go to [Dialog with Only on this computer at the top](#dialog-with-only-on-this-computer-at-the-top) before you enter anything.
+Click **New task** to open the **New scheduled task** dialog. Check for these screens before you continue:
+
+* If a menu opens with **Create with Claude** and **Set up manually**, select **Set up manually** to open the dialog.
+* If **Only on this computer** is at the top of the dialog, go to [Dialog with Only on this computer at the top](#dialog-with-only-on-this-computer-at-the-top) before you enter anything.
+* If a menu with **Local** and **Cloud** opens, or a full page opens in place of the dialog, go to [Full-page form](#full-page-form).
 
 **3. Name the task**
 
@@ -99,9 +107,20 @@ Then fill in the local form's fields:
 
 Click **Create**. The task's detail page opens.
 
+### Full-page form
+
+If a menu with **Local** and **Cloud** opens, select **Local**. A page titled **New local routine** or **New local scheduled task** opens. Fill in its fields:
+
+* **Name**: enter a name that is unique across your tasks.
+* **Description**: enter one.
+* **Instructions**: enter what Claude should do when the task runs. In the same box, select the permission mode, the model, and the folder the task runs in.
+* **Schedule**: select one of the [schedule options](#schedule-options).
+
+If **Create** is unavailable, hover over it to see what the form still needs. Click **Create**, and the task's detail page opens.
+
 ## Schedule options
 
-When you turn on **Only on this computer** under **Advanced settings**, the **Trigger** card offers Hourly, Daily, Weekdays, and Weekly. To get **Manual** or **Custom** for such a task, open its [**Edit** form](#manage-scheduled-tasks) after you create it. That form and the [dialog with **Only on this computer** at the top](#dialog-with-only-on-this-computer-at-the-top) offer these six options:
+When you turn on **Only on this computer** under **Advanced settings**, the **Trigger** card offers Hourly, Daily, Weekdays, and Weekly. To get **Manual** or **Custom** for such a task, open its [**Edit** form](#manage-scheduled-tasks) after you create it. That form, the [dialog with **Only on this computer** at the top](#dialog-with-only-on-this-computer-at-the-top), and the [full-page form](#full-page-form) offer these six options:
 
 * **Hourly**: runs every hour
 * **Daily**: runs every day at the local time you pick
diff --git a/content/en/docs/claude-code/env-vars.md b/content/en/docs/claude-code/env-vars.md
index d66c0deddb..f8ef8ec0e4 100644
--- a/content/en/docs/claude-code/env-vars.md
+++ b/content/en/docs/claude-code/env-vars.md
@@ -298,7 +298,7 @@ Numeric variables such as timeouts, token budgets, and retry counts accept scien
 | `CLAUDE_CODE_FORCE_SESSION_PERSISTENCE` | Set to `1` to force transcript persistence, prompt history, and `claude agents` registration even when this `claude` was launched from inside another Claude Code session. Use when an inherited `CLAUDE_CODE_CHILD_SESSION` value, for example from a `screen` session or a background launcher first started by Claude Code's Bash tool, causes a genuine top-level session to be misclassified as nested. As of v2.1.178, Claude Code detects the tmux case automatically and ignores the inherited marker, so tmux no longer needs this variable. Also honored on v2.1.169 and earlier; has no effect on v2.1.170 and v2.1.171, where the nested-session detection it overrides was removed |
 | `CLAUDE_CODE_FORCE_STRIKETHROUGH` | Set to `1` to force strikethrough rendering for `~~text~~` in Claude's responses when your terminal supports it but is not auto-detected, such as over SSH without `TERM_PROGRAM` forwarded. Without this, undetected terminals show the literal `~~` markers instead of rendering the text as strikethrough. Requires Claude Code v2.1.186 or later |
 | `CLAUDE_CODE_FORCE_SYNC_OUTPUT` | Set to `1` to force-enable DEC private mode 2026 [synchronized output](https://gist.github.com/christianparpart/d8a62cc1ab659194337d73e399004036) when your terminal supports it but is not auto-detected. Useful for emulators such as Emacs `eat` that implement BSU/ESU but do not reply to the capability probe. Has no effect under tmux. Unlike `CLAUDE_CODE_NO_FLICKER`, which switches to [fullscreen rendering](https://code.claude.com/docs/en/fullscreen.md), this doesn't change the renderer |
-| `CLAUDE_CODE_FORCE_TERMINAL_IMAGES` | Set to `1` to draw [mod `Image` elements](https://code.claude.com/docs/en/plugins/mods/reference#elements) as pictures when your terminal draws kitty graphics protocol images with Unicode placeholders and you still see an `Image`'s dimmed `alt` text. See [which terminals draw an `Image`](https://code.claude.com/docs/en/plugins/mods/gallery#image-and-client) and why this variable doesn't help inside tmux or screen |
+| `CLAUDE_CODE_FORCE_TERMINAL_IMAGES` | Set to `1` to draw [mod `Image` elements](https://code.claude.com/docs/en/plugins/mods/reference#elements) as pictures when your terminal draws kitty graphics protocol images with Unicode placeholders and you still see an `Image`'s dimmed `alt` text. See [which terminals draw an `Image` and where not to set this variable](https://code.claude.com/docs/en/plugins/mods/gallery#image-and-client) |
 | `CLAUDE_CODE_FORK_SUBAGENT` | Controls fork mode, which is on by default and lets Claude start [forks](https://code.claude.com/docs/en/sub-agents.md#fork-the-current-conversation) on its own. While fork mode is on, Claude also can't [wait for a subagent](https://code.claude.com/docs/en/sub-agents.md#run-subagents-in-foreground-or-background) in interactive terminal, VS Code, or desktop sessions on your machine. Set to `0` to turn fork mode off. For versions, see [Turn fork mode off](https://code.claude.com/docs/en/sub-agents.md#turn-fork-mode-on-or-off) |
 | `CLAUDE_CODE_FORWARD_SUBAGENT_TEXT` | Set to `1` to emit [subagent](https://code.claude.com/docs/en/sub-agents.md) text and thinking blocks in `claude -p --output-format stream-json` output, the same behavior as the [`--forward-subagent-text`](https://code.claude.com/docs/en/cli-reference#cli-flags) flag. Use the variable when a harness invokes `claude` and can't pass the flag itself. Unlike the flag, which exits with an error outside non-interactive mode with stream-json output, the variable is ignored there so that nested invocations keep working when it's set process-wide. Requires Claude Code v2.1.211 or later |
 | `CLAUDE_CODE_GATEWAY_HINT_HEADERS` | Set to `1` to send the [gateway hint headers](https://code.claude.com/docs/en/llm-gateway-protocol.md#gateway-hint-headers), such as `x-claude-code-request-class` and `x-claude-code-compaction`, on a custom proxy or a third-party provider such as Amazon Bedrock or Claude Platform on AWS. Set to `0` to stop sending them on every connection, including a direct connection to the Anthropic API, where Claude Code sends them by default. Requires Claude Code v2.1.273 or later |
diff --git a/content/en/docs/claude-code/errors.md b/content/en/docs/claude-code/errors.md
index c94d57b416..c3d513af5d 100644
--- a/content/en/docs/claude-code/errors.md
+++ b/content/en/docs/claude-code/errors.md
@@ -317,6 +317,7 @@ Match the message you see to a section below.
 | `Skipping connection (recent failure cached; retries automatically in 15 min, or edit the plugin config to retry now)` | [Plugin errors](#skipping-connection-recent-failure-cached) |
 | `Error: No such tool available: <tool name>` | [Tool errors](#no-such-tool-available) |
 | `MCP server "<name>" connection closed before the tool call was answered` | [Tool errors](#connection-closed-before-the-tool-call-was-answered) |
+| `MCP server "<name>" is disabled — re-enable it via /mcp to use its tools` | [Tool errors](#mcp-server-is-disabled) |
 | `MCP server "<name>" tool "<tool>" timed out after <N>s. The server asked the user a question, and no answer came before the time limit.` | [Tool errors](#mcp-tool-call-timed-out-with-the-servers-question-unanswered) |
 | `would be spawned with zero tools — refusing` | [Tool errors](#agent-would-be-spawned-with-zero-tools) |
 | `File is covered by a Read deny rule in your permission settings` | [Tool errors](#file-is-covered-by-a-read-deny-rule) |
@@ -349,6 +350,7 @@ Match the message you see to a section below.
 | `Your disk quota is full on the filesystem with Claude Code's temp directory <dir> (EDQUOT)` / `The filesystem with Claude Code's temp directory <dir>, or your disk quota on it, is full (ENOSPC)` | [Tool errors](#disk-quota-or-temp-filesystem-is-full) |
 | `Command output was lost: the temp filesystem at <dir> is full` / `is out of inodes` | [Tool errors](#disk-quota-or-temp-filesystem-is-full) |
 | `File is not valid UTF-8. It may use a legacy encoding such as Windows-1252, Shift-JIS or GBK, or be binary` | [Tool errors](#file-is-not-valid-utf-8) |
+| `git is not installed on this Mac. To install it, run xcode-select --install, then try again.` | [Tool errors](#git-is-not-installed-on-this-mac) |
 | `the source file is not valid UTF-8 text` / `the source file is not valid UTF-16 text` | [Tool errors](#the-source-file-is-not-valid-utf-8-text) |
 | `the source file has the replacement character U+FFFD` | [Tool errors](#the-source-file-is-not-valid-utf-8-text) |
 | `Not published: that file is on a network share` | [Tool errors](#not-published-that-file-is-on-a-network-share) |
@@ -488,6 +490,16 @@ The banner clears on its own once data resumes or a retry succeeds. If it reappe
 
 While Claude is consulting the [advisor](https://code.claude.com/docs/en/advisor.md), the banner appears after 90 seconds without data instead of 20, because a long advisor review can send nothing for well over 20 seconds. Before v2.1.214, the 20-second threshold applied during advisor calls too, so the banner appeared during advisor reviews even when nothing was wrong.
 
+#### The waiting banner comes and goes behind a gateway
+
+If the `Waiting for API response` banner comes and goes while Claude thinks and you connect through a gateway, [update Claude Code](https://code.claude.com/docs/en/setup.md#update-claude-code) to v2.1.309 or later. The banner appears after 45 seconds without data on these connections:
+
+* [`ANTHROPIC_BASE_URL`](https://code.claude.com/docs/en/env-vars) set to a host other than the Anthropic API, such as an [LLM gateway](https://code.claude.com/docs/en/llm-gateway)
+* A [Claude apps gateway](https://code.claude.com/docs/en/claude-apps-gateway) session
+* [Claude Platform on AWS](https://code.claude.com/docs/en/claude-platform-on-aws.md) with `ANTHROPIC_AWS_BASE_URL` set
+
+Before v2.1.309, the banner appeared after 20 seconds on these connections.
+
 ### Tune retry behavior
 
 You can tune retry behavior with these environment variables:
@@ -3257,7 +3269,7 @@ For example, the subcommand can't ask when its standard input or standard output
 
 **What to do:**
 
-* In a script or CI job, append `--trust-workspace` to trust the checkout for that run only: `claude ultrareview --trust-workspace`. Append it only for code you trust, because the checkout's git configuration and Claude Code project settings can then run programs. To review a pull request whose code you don't trust, see [how to review it from a checkout you do trust](https://code.claude.com/docs/en/ultrareview.md#trust-the-folder-before-the-review-runs).
+* In a script or CI job, append `--trust-workspace` to trust the folder for that run: `claude ultrareview --trust-workspace`. Append it only for code you trust, because git and Claude Code can then run programs named in the folder's git configuration and project settings. For a pull request whose code you don't trust, [run the review from a branch you trust](https://code.claude.com/docs/en/ultrareview.md#trust-the-folder-before-the-review-runs).
 * On your own machine, run `claude` in that folder and accept the [workspace trust dialog](https://code.claude.com/docs/en/permissions.md#project-allow-rules-and-workspace-trust), then run your original command again
 
 Each of these messages from `claude ultrareview` means that no review started and the exit code is 1:
@@ -4420,6 +4432,20 @@ Repeating the call could repeat the tool's action, such as creating a second iss
 * If the action didn't happen, ask Claude to run the tool again. You don't need to reconnect the server first, because Claude Code connects to it again for the next call to one of its tools. If that connection fails too, see [Mid-session drops of a remote server](https://code.claude.com/docs/en/mcp.md#mid-session-drops-of-a-remote-server).
 * If you build the server and the tool is safe to call twice, [mark it as safe to repeat](https://code.claude.com/docs/en/mcp.md#tool-calls-pending-when-a-connection-closes) so that Claude Code can repeat a lost call
 
+### MCP server is disabled
+
+This message in a tool result means Claude called a tool on an [MCP server](https://code.claude.com/docs/en/mcp.md) that is [turned off](https://code.claude.com/docs/en/mcp.md#disable-a-server-without-removing-it). Claude Code didn't connect to the server, so the tool didn't run, and Claude received this text in place of a result:
+
+```text wrap theme={null}
+MCP server "<name>" is disabled — re-enable it via /mcp to use its tools
+```
+
+**What to do:**
+
+* If you meant to turn the server off, you don't need to do anything
+* If Claude needs the server's tools, turn it back on from `/mcp` at the Claude Code prompt
+* In an [Agent SDK](https://code.claude.com/docs/en/agent-sdk/overview.md) application, turn the server back on by calling [`toggleMcpServer()`](https://code.claude.com/docs/en/agent-sdk/typescript#togglemcpserver) in TypeScript with `enabled` set to `true`, or [`toggle_mcp_server()`](https://code.claude.com/docs/en/agent-sdk/python#claudesdkclient) in Python with `enabled` set to `True`
+
 ### MCP tool call timed out with the server's question unanswered
 
 In [non-interactive mode](https://code.claude.com/docs/en/headless.md), an [MCP server](https://code.claude.com/docs/en/mcp.md) asked for input through [elicitation](https://code.claude.com/docs/en/mcp.md#respond-to-mcp-elicitation-requests) during a tool call, and the call's time limit ran out before an answer came:
@@ -4759,7 +4785,7 @@ Claude Code saves each Bash and PowerShell command's output to a file under that
 The command was not started: this computer's disk is full (ENOSPC) on the volume holding /tmp/claude-501 (Claude Code's temporary directory), so the file that captures command output could not be created there and nothing ran. Free space on that volume, or restart Claude Code with CLAUDE_CODE_TMPDIR set to a directory on another one, then retry. If this is the user's own computer, tell them before deleting anything to make room.
 ```
 
-The other three messages follow a command that ran and exited with a nonzero code. This example is the `Disk full:` form:
+The `Disk full:`, `Disk quota used up:`, and `Nearly out of inodes:` messages follow a command that ran and exited with a nonzero code. For example:
 
 ```text wrap theme={null}
 Disk full: this computer's volume holding /tmp/claude-501 (Claude Code's temporary directory) has 3 MB free, so whatever this command printed was lost and its own writes may have failed with "No space left on device". Free space on that volume, or restart Claude Code with CLAUDE_CODE_TMPDIR set to a directory on another one, then retry. If this is the user's own computer, tell them before deleting anything to make room.
@@ -4769,8 +4795,7 @@ Disk full: this computer's volume holding /tmp/claude-501 (Claude Code's tempora
 
 * On macOS and Linux, run `df -h <dir>` in your shell to see which volume holds the directory and how full it is. `df -i <dir>` shows how many inodes are free. `<dir>` is the directory your message names, as in `df -i /tmp/claude-501`
 * **`Disk full: this computer's volume` or `disk is full (ENOSPC)`**: anywhere on that volume, delete files you don't need
-* **`Disk quota used up:` or `Disk full: a test write`**: delete your own files on that volume, even if it still shows free space
-* **`disk quota is used up (EDQUOT)`**: delete your own files on that volume
+* **`Disk quota used up:`, `disk quota is used up (EDQUOT)`, or `Disk full: a test write`**: delete your own files on that volume, even if it still shows free space
 * **`Nearly out of inodes:`**: delete many files on that volume. Each takes one inode whatever its size, so their number matters, not their size
 * Or restart Claude Code with [`CLAUDE_CODE_TMPDIR`](https://code.claude.com/docs/en/env-vars) set to a directory on a volume with room
 * Then have Claude run the command again
@@ -4784,6 +4809,20 @@ Before v2.1.309, the messages read as follows, and the same steps apply:
 
 Before v2.1.305, a command that Claude Code couldn't start because the disk was full returned only the operating system's error text. That text read, for example, `ENOSPC: no space left on device, open <path>.output`.
 
+### git is not installed on this Mac
+
+This message means a step in Claude Code needed git, and the git it found is Apple's stand-in at `/usr/bin/git`. The developer tools that provide git aren't installed.
+
+Claude Code doesn't start the stand-in and shows this text instead, for example inside a longer message:
+
+```text wrap theme={null}
+git is not installed on this Mac. To install it, run xcode-select --install, then try again.
+```
+
+**What to do:**
+
+* In Terminal, run `xcode-select --install`, finish the installation it starts, then retry what you were doing in Claude Code
+
 ### File is not valid UTF-8
 
 Claude used the Edit or NotebookEdit tool on a file whose bytes don't decode as UTF-8, and Claude Code refused the change. Nothing was written, so the file is as it was. Those tools save the whole file back as UTF-8, which would have turned every byte they couldn't decode into the replacement character `U+FFFD`. The message appears in the tool result:
diff --git a/content/en/docs/claude-code/fast-mode.md b/content/en/docs/claude-code/fast-mode.md
index 98f478ecf5..c8f708cb48 100644
--- a/content/en/docs/claude-code/fast-mode.md
+++ b/content/en/docs/claude-code/fast-mode.md
@@ -155,25 +155,35 @@ Another option to disable fast mode entirely is to set `CLAUDE_CODE_DISABLE_FAST
 
 Before offering fast mode, Claude Code checks your organization's fast mode availability with a request directly to `api.anthropic.com`. The check doesn't follow [`ANTHROPIC_BASE_URL`](https://code.claude.com/docs/en/llm-gateway-connect#set-the-base-url-and-credential), so on a network that routes Claude traffic through an [LLM gateway](https://code.claude.com/docs/en/llm-gateway) and blocks direct egress to `api.anthropic.com`, the check fails even though inference requests work. The check does use a configured [HTTP proxy](https://code.claude.com/docs/en/network-config.md#proxy-configuration), so a network block fails the check only where `api.anthropic.com` is unreachable even through the proxy.
 
-When the check fails, `/fast` reports "Fast mode unavailable due to network connectivity issues", and requests run at standard speed, even when your organization has fast mode enabled. A check that succeeded in the past keeps working from its cached result, so a blocked check mostly affects new installations.
+If your organization has fast mode enabled and `/fast` says otherwise, find the message it shows among these cases.
 
-The same connectivity message appears on an open network when the check reaches `api.anthropic.com` but presents a credential Anthropic rejects. A session whose resolved key is a gateway-issued credential, held in [`ANTHROPIC_API_KEY`](https://code.claude.com/docs/en/llm-gateway-connect#set-the-base-url-and-credential) or produced by an [`apiKeyHelper`](https://code.claude.com/docs/en/settings-reference#apikeyhelper), sends the check with that key, and the rejected request is reported as a connectivity failure.
+#### Fast mode unavailable due to network connectivity issues
 
-To restore fast mode, allowlist direct egress to `api.anthropic.com` where a network block is the cause, or set whichever variable matches how the check fails:
+The availability check failed, for example because your network blocks `api.anthropic.com`, and requests run at standard speed. A check that succeeded in the past keeps working from its cached result, so a blocked check mostly affects new installations.
 
-* `CLAUDE_CODE_SKIP_FAST_MODE_NETWORK_ERRORS=1` treats a failed check as available and still honors a "disabled by your organization" response. Use it when your network refuses the connection, or when Anthropic rejects a gateway credential; allowlisting doesn't help the credential case, since nothing is blocked.
-* `CLAUDE_CODE_SKIP_FAST_MODE_ORG_CHECK=1` skips the check entirely. Use it when your network intercepts the request rather than refusing it.
+To restore fast mode, allowlist direct egress to `api.anthropic.com`, or set `CLAUDE_CODE_SKIP_FAST_MODE_NETWORK_ERRORS=1`, which treats a failed check as available and still honors a "disabled by your organization" response.
 
-Two gateway configurations report "Fast mode has been disabled by your organization" rather than the connectivity message, even when your organization has fast mode enabled:
+#### Fast mode is currently unavailable
 
-* A session that authenticates with [`ANTHROPIC_AUTH_TOKEN`](https://code.claude.com/docs/en/llm-gateway-connect#set-the-base-url-and-credential) alone skips the check: without a claude.ai login or an Anthropic API key, and without a cached successful check, Claude Code treats fast mode as disabled by your organization without sending the request.
-* A proxy that intercepts the check and answers with its own page, for example a TLS-inspecting proxy returning an HTTP 200 block page, is read as a response saying your organization has fast mode disabled.
+Behind a gateway, check for these configurations, in which Claude Code doesn't send the availability check and has no earlier successful check cached:
 
-In both cases, set `CLAUDE_CODE_SKIP_FAST_MODE_ORG_CHECK=1` to restore fast mode. `CLAUDE_CODE_SKIP_FAST_MODE_NETWORK_ERRORS` doesn't apply to either case, since it only bypasses failed checks and both of these produce a disabled response instead. Allowlisting direct egress doesn't help the bearer-token case, which never sends the request.
+* You point `ANTHROPIC_BASE_URL` at your gateway and set [`ANTHROPIC_API_KEY`](https://code.claude.com/docs/en/llm-gateway-connect#set-the-base-url-and-credential) to a gateway-issued key that isn't in the format of an Anthropic API key. Claude Code withholds such a key from `api.anthropic.com`.
+* You set [`CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC`](https://code.claude.com/docs/en/env-vars), so Claude Code skips the check.
 
-The variables affect only the client-side check. When your organization has fast mode disabled, the API rejects fast mode requests whether or not they're set. A rejection from the API stands even with a skip variable set. Claude Code retries the rejected request at standard speed, turns fast mode off, and `/fast` reports that your organization has disabled fast mode.
+To restore fast mode in either configuration, set `CLAUDE_CODE_SKIP_FAST_MODE_NETWORK_ERRORS=1`.
 
-Setting `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC` also suppresses the availability check. Without a previously cached successful check, `/fast` reports "Fast mode is currently unavailable"; both skip variables restore fast mode in that configuration too.
+#### Fast mode has been disabled by your organization
+
+Behind a gateway, you can see this message even when your organization has fast mode enabled, in either of these configurations:
+
+* You authenticate with [`ANTHROPIC_AUTH_TOKEN`](https://code.claude.com/docs/en/llm-gateway-connect#set-the-base-url-and-credential) alone, with no claude.ai login, no API key, and no cached successful check. Claude Code then treats fast mode as disabled by your organization without sending the request.
+* A proxy intercepts the check and answers with its own page, for example a TLS-inspecting proxy returning an HTTP 200 block page. Claude Code reads that page as a response saying your organization has fast mode disabled.
+
+In both cases, set `CLAUDE_CODE_SKIP_FAST_MODE_ORG_CHECK=1`, which skips the check entirely, rather than `CLAUDE_CODE_SKIP_FAST_MODE_NETWORK_ERRORS`, which doesn't apply to either.
+
+> [!NOTE]
+>
+> The skip variables change only the client-side check. When your organization has fast mode disabled, the API rejects fast mode requests whether or not they're set. Claude Code then retries the request at standard speed, turns fast mode off, and `/fast` reports that your organization has disabled fast mode.
 
 ### Require per-session opt-in
 
diff --git a/content/en/docs/claude-code/hooks.md b/content/en/docs/claude-code/hooks.md
index 58245633e5..c3168dd4a3 100644
--- a/content/en/docs/claude-code/hooks.md
+++ b/content/en/docs/claude-code/hooks.md
@@ -961,18 +961,27 @@ If the error for a blocked tool call includes this text, a `PreToolUse` or `Perm
 blocking because Git Bash wasn't found, so only exit code 0 or 2 counts as this hook's verdict.
 ```
 
-To find out why the hook failed, check the [debug log](#debug-hooks). Pick the fix that matches your hook:
+If the error also says `PowerShell started no program`, start with [the fixes for a `command` that is only quoted strings](#powershell-started-no-program), which PowerShell prints instead of running.
 
-* **The action should go ahead when the hook fails**: add [`"onFailure": "continue"`](#block-the-action-when-a-hook-fails) to the hook
-* **The hook is written for Bash**: a [shell-form](#exec-form-and-shell-form) hook with no `shell` set runs in PowerShell when Git Bash isn't installed, where a script written for Bash may not run as written. Install [Git for Windows](https://git-scm.com/downloads/win), or set [`CLAUDE_CODE_GIT_BASH_PATH`](https://code.claude.com/docs/en/env-vars) if Git Bash is installed where Claude Code doesn't find it, then start a new session
+Without Git Bash, any exit code other than 0 or 2 from that hook counts as a [failure](#block-the-action-when-a-hook-fails), even when it prints JSON that doesn't deny the call. To find out why the hook failed, check the [debug log](#debug-hooks). Then pick the fix that matches your hook:
+
+* **The call should go ahead when the hook fails**: add [`"onFailure": "continue"`](#block-the-action-when-a-hook-fails) to the hook
+* **The hook exits 1 to warn but must block when it crashes**: with `"onFailure": "continue"`, the call goes ahead on exit code 1, warning or crash alike. Add `"onFailure": "block"` instead, and have the script exit 0 where it warns, so those calls go ahead. To still show the warning on `PreToolUse`, print it to stdout as the [`systemMessage`](#json-output) field of one JSON object.
+* **The hook is written for Bash**: without Git Bash, a [shell-form](#exec-form-and-shell-form) hook with no `shell` set runs in PowerShell, where it can fail. Install [Git for Windows](https://git-scm.com/downloads/win), or set [`CLAUDE_CODE_GIT_BASH_PATH`](https://code.claude.com/docs/en/env-vars) if Git Bash is installed where Claude Code doesn't find it. Then start a new session.
 * **The hook runs one `.exe`, not a `.cmd` or `.bat` file**: put the program in `command` and its arguments in `args` to use exec form, and add `"onFailure": "block"`. Claude Code then starts the program with no shell. Without `"onFailure": "block"`, the call can go ahead when the program fails, is missing, or times out
-* **The hook exits 1 to warn but must block when it crashes**: with `"onFailure": "continue"`, the call goes ahead on exit code 1, warning or crash alike. Add `"onFailure": "block"` instead, and end the script with exit code 0 where it warns, so those calls go ahead. To show the warning on `PreToolUse` after exit code 0, print it to stdout in the [`systemMessage`](#json-output) field of one JSON object
 * **A PowerShell guard hook that must block on failure**: with `onFailure` unset, it stops doing so once Git for Windows is installed and Claude Code finds Git Bash. Add `"onFailure": "block"` so a failure or a timeout blocks the call with or without Git Bash. Also set `"shell": "powershell"` so the hook keeps running in PowerShell from then on instead of in Git Bash
 
-For a hook that shows this error, any exit code other than 0 or 2 counts as a [failure](#block-the-action-when-a-hook-fails), even when the hook prints JSON that doesn't deny the call.
-
 Before v2.1.309, the message read `blocking because Git Bash wasn't found and this hook doesn't set "shell" to "powershell", so only exit code 0 or 2 counts as its verdict.`
 
+#### PowerShell started no program
+
+A hook with this error ran in PowerShell, which prints a `command` that is only quoted strings, such as `"command": "\"C:\\Tools\\guard.exe\""`, instead of running it.
+
+* **To print text, such as JSON**: set `"shell": "powershell"`, and the hook exits 0
+* **To run a `.ps1`, `.cmd`, or `.bat` file, or a `.exe` whose path has a variable**: set `"shell": "powershell"` and put `&` before the quoted path. Leave `$HOME` as written, and spell environment variables as the [`check.ps1` example](#reference-scripts-by-path-in-powershell-hooks) spells `$env:CLAUDE_PROJECT_DIR`
+* **To run one `.exe` at a path without `$`**: remove the inner quotes from `command`, then apply the [fix for a hook that runs one `.exe`](#failed-hooks-on-windows-without-git-bash), writing `"args": []` if the program takes no arguments
+* **To run a script written for Bash**: apply the [fix for a hook written for Bash](#failed-hooks-on-windows-without-git-bash)
+
 #### Exit code 2 behavior per event
 
 Exit code 2 is the way a hook signals "stop, don't do this." The effect depends on the event, because some events represent actions that can be blocked (like a tool call that hasn't happened yet) and others represent things that already happened or can't be prevented.
@@ -4187,6 +4196,8 @@ On Windows, you can run individual hooks in PowerShell by setting `"shell": "pow
 }
 ```
 
+### Reference scripts by path in PowerShell hooks
+
 To reference the project root from a PowerShell shell-form command, write `${CLAUDE_PROJECT_DIR}` or `$env:CLAUDE_PROJECT_DIR`. Claude Code rewrites the `${CLAUDE_PROJECT_DIR}`, `${CLAUDE_PLUGIN_ROOT}`, and `${CLAUDE_PLUGIN_DATA}` placeholders in a PowerShell shell-form command to PowerShell's `${env:NAME}` form, whether the hook is defined in `settings.json`, a plugin, or a skill. PowerShell then resolves the value from the exported environment after parsing, so the placeholder works inside double-quoted strings but not inside single-quoted strings, where PowerShell never expands variables.
 
 Don't write the bare `$CLAUDE_PROJECT_DIR` spelling in a PowerShell hook. PowerShell parses it as an undefined local variable and resolves it to `$null`, which leaves the script path without its project-root prefix. Claude Code doesn't rewrite that form; it logs a warning in the [debug log](#debug-hooks) instead.
diff --git a/content/en/docs/claude-code/llm-gateway-connect.md b/content/en/docs/claude-code/llm-gateway-connect.md
index d1bfadc38c..11a462f1a2 100644
--- a/content/en/docs/claude-code/llm-gateway-connect.md
+++ b/content/en/docs/claude-code/llm-gateway-connect.md
@@ -519,8 +519,9 @@ These are the most common errors when running Claude Code through a gateway, wit
 | `400` errors on every request, in the gateway's own words rejecting a tool's input schema or its `pattern`, on Claude Code v2.1.265 through v2.1.267 | In a gradual rollout on those versions, the [Artifact tool](https://code.claude.com/docs/en/artifacts.md#availability) schema carries a regular expression with `\p{...}` Unicode character classes. The Anthropic API accepts it, but a gateway or upstream that checks each tool schema's `pattern` with its own regex engine rejects the whole request | Update to v2.1.268 or later, which doesn't send the regular expression. On an affected version, [turn artifacts off](https://code.claude.com/docs/en/artifacts.md#disable-artifacts), which removes the tool and its schema from requests |
 | `400` errors on every request, in the gateway's own words rejecting an unrecognized tool type, such as `Input tag 'advisor_20260301'`, on Claude Code v2.1.275 | In a gradual rollout on that version, requests carry an [advisor tool](https://code.claude.com/docs/en/advisor.md) entry even with the advisor off. The Anthropic API accepts it, but a gateway or upstream that validates tool types rejects the whole request; one that [forwards request body fields unchanged](https://code.claude.com/docs/en/llm-gateway-protocol.md#forward-as-open-lists) passes it through unaffected. The entry is a declaration that carries no conversation content | Update to v2.1.276 or later, which doesn't send the entry behind an `ANTHROPIC_BASE_URL` gateway unless you turn the advisor on. On v2.1.275, set [`CLAUDE_CODE_DISABLE_ADVISOR_TOOL=1`](https://code.claude.com/docs/en/env-vars), which removes the entry from requests |
 | Models missing from the `/model` picker | Gateway model names aren't in Claude Code's built-in list, or Claude Code is showing a [`modelPicker`](https://code.claude.com/docs/en/settings-reference#modelpicker) lineup that replaces the built-in options | Enable [gateway model discovery](#add-gateway-models-to-the-model-picker) or add names with the [model configuration](https://code.claude.com/docs/en/model-config.md) variables. If Claude Code shows a replacing `modelPicker` lineup, add the gateway models to it, or ask your administrator to add them when managed settings supply it |
-| `/fast` reports `Fast mode unavailable due to network connectivity issues` while inference requests work | The [fast mode](https://code.claude.com/docs/en/fast-mode.md) availability check goes directly to `api.anthropic.com` and doesn't follow `ANTHROPIC_BASE_URL`, so blocked direct egress fails the check. The same message appears on an open network when the check presents a gateway-issued key from `ANTHROPIC_API_KEY` or an `apiKeyHelper` and Anthropic rejects it | Allowlist `api.anthropic.com` if egress is blocked, or set a skip variable; for a rejected gateway key only the skip variables help. See [use fast mode behind proxies and LLM gateways](https://code.claude.com/docs/en/fast-mode.md#use-fast-mode-behind-proxies-and-llm-gateways) |
-| `/fast` reports `Fast mode has been disabled by your organization` in a session authenticated with `ANTHROPIC_AUTH_TOKEN`, even though the organization has fast mode enabled | The availability check requires a claude.ai login or an Anthropic API key; with only a bearer token, Claude Code treats fast mode as disabled without sending the check | Set `CLAUDE_CODE_SKIP_FAST_MODE_ORG_CHECK=1`; see [use fast mode behind proxies and LLM gateways](https://code.claude.com/docs/en/fast-mode.md#use-fast-mode-behind-proxies-and-llm-gateways) |
+| `/fast` reports `Fast mode unavailable due to network connectivity issues` while inference requests work | The [fast mode](https://code.claude.com/docs/en/fast-mode.md) availability check goes directly to `api.anthropic.com` and doesn't follow `ANTHROPIC_BASE_URL`, so blocked direct egress fails the check | Allowlist `api.anthropic.com` if egress is blocked, or set a skip variable. See [use fast mode behind proxies and LLM gateways](https://code.claude.com/docs/en/fast-mode.md#use-fast-mode-behind-proxies-and-llm-gateways) |
+| `/fast` reports `Fast mode is currently unavailable` in a session that authenticates with a gateway-issued key in `ANTHROPIC_API_KEY` | While `ANTHROPIC_BASE_URL` points at your gateway, Claude Code withholds from `api.anthropic.com` a key that isn't in the format of an Anthropic API key. The [fast mode](https://code.claude.com/docs/en/fast-mode.md) availability check then isn't sent, and without an earlier successful check cached, Claude Code treats fast mode as unavailable | Set `CLAUDE_CODE_SKIP_FAST_MODE_NETWORK_ERRORS=1`; see [use fast mode behind proxies and LLM gateways](https://code.claude.com/docs/en/fast-mode.md#use-fast-mode-behind-proxies-and-llm-gateways) |
+| `/fast` reports `Fast mode has been disabled by your organization` in a session authenticated with `ANTHROPIC_AUTH_TOKEN`, even though the organization has fast mode enabled | The availability check requires a claude.ai login or an API key; with only a bearer token, Claude Code treats fast mode as disabled without sending the check | Set `CLAUDE_CODE_SKIP_FAST_MODE_ORG_CHECK=1`; see [use fast mode behind proxies and LLM gateways](https://code.claude.com/docs/en/fast-mode.md#use-fast-mode-behind-proxies-and-llm-gateways) |
 | Claude Code asks you to log in even though the [curl test](#verify-the-connection) succeeds | The CLI has no credential of its own: a reachable base URL isn't one, and in an interactive session an `env` block in a project's `.claude/settings.json` or `.claude/settings.local.json` applies only after the first-run wizard and [trust prompt](https://code.claude.com/docs/en/permissions.md#what-runs-before-you-trust-a-folder) | Set `ANTHROPIC_AUTH_TOKEN` somewhere Claude Code reads before first-run setup: a shell export, the `env` block in `~/.claude/settings.json`, or managed settings |
 | `ANTHROPIC_API_KEY` is set but ignored, with no prompt | The key needs a one-time approval in interactive sessions, and a previously declined key is ignored without asking again | Enable it under `/config` with the `Use custom API key` option |
 | `This machine's managed settings require a first-party login`, or [`Administrator policy requires a Cloud gateway sign-in`](https://code.claude.com/docs/en/errors#administrator-policy-requires-a-cloud-gateway-sign-in) when managed settings set `forceLoginMethod` to `"gateway"` or also set `forceLoginGatewayUrl` | Managed settings include `forceLoginMethod` or `forceLoginOrgUUID`, which cannot coexist with `ANTHROPIC_API_KEY`, `ANTHROPIC_AUTH_TOKEN`, or `apiKeyHelper` | Your administrator must remove `forceLoginMethod`, `forceLoginOrgUUID`, and `forceLoginGatewayUrl` from managed settings to use gateway credentials, or remove the gateway credential and use the sign-in the managed settings require. The two cannot be combined |
diff --git a/content/en/docs/claude-code/mcp.md b/content/en/docs/claude-code/mcp.md
index daedd4483b..e1c3a1ac47 100644
--- a/content/en/docs/claude-code/mcp.md
+++ b/content/en/docs/claude-code/mcp.md
@@ -1332,7 +1332,7 @@ In Claude Code, use the command:
 
 Servers from claude.ai appear in the list with indicators showing they come from claude.ai.
 
-Anthropic also provides some connectors itself, without you or an admin adding them. On accounts where [Claude Docs](https://code.claude.com/docs/en/artifacts.md#write-a-document-with-claude-docs) is available, `/mcp` lists `claude.ai Claude Docs` with no setup, and Claude uses it when you ask for a document meant for other people. To turn it off, add a `serverName` entry of `"claude.ai Claude Docs"` to `deniedMcpServers` or use the `/mcp` toggle, both described in [Disable claude.ai connectors](#disable-claude-ai-connectors).
+Anthropic also provides some connectors itself, without you or an admin adding them. On accounts where [Claude Docs](https://code.claude.com/docs/en/artifacts.md#write-a-document-with-claude-docs) is available, `/mcp` lists `claude.ai Claude Docs` with no setup, and Claude uses it when you ask for a document meant for other people. To turn off only this connector, see [Disable claude.ai connectors](#disable-claude-ai-connectors).
 
 Claude Code marks a connector `managed` in `/mcp` and in the [`/plugin`](https://code.claude.com/docs/en/plugins/install) manager when your organization manages its authentication in claude.ai. Managed status doesn't change how Claude Code connects to the connector or applies your organization's [tool controls](#organization-controls-on-connector-tools).
 
diff --git a/content/en/docs/claude-code/model-config.md b/content/en/docs/claude-code/model-config.md
index f756377544..6db0f98f12 100644
--- a/content/en/docs/claude-code/model-config.md
+++ b/content/en/docs/claude-code/model-config.md
@@ -349,7 +349,7 @@ Without `enforceAvailableModels` or the `env` block, a user who selects Default
 
 When the managed settings Claude Code applies define `availableModels`, that list alone applies, apart from a [host platform that supplies its own](https://code.claude.com/docs/en/settings.md#exceptions-to-managed-settings-precedence): entries in user, project, or local settings cannot extend it, and Claude Code never merges `availableModels` across managed sources either; [how Claude Code combines managed sources](https://code.claude.com/docs/en/managed-settings.md#how-claude-code-combines-managed-sources) says which source's list applies. Otherwise, lists from user, project, and local settings are [concatenated and deduplicated](https://code.claude.com/docs/en/settings.md#settings-precedence) like other array settings. Before Claude Code v2.1.175, entries from lower-precedence scopes merged into the managed list instead of being replaced by it.
 
-Within the effective list, an entry naming a specific model in a family, whether a version prefix or a full model ID, disables that family's wildcard entry: `["sonnet", "claude-sonnet-4-5"]` allows only Sonnet 4.5 versions, not every Sonnet model.
+Within the effective list, an entry naming a specific model in a family, whether a version prefix or a full model ID, disables that family's wildcard entry. For example, with `["sonnet", "claude-sonnet-4-5"]`, users can pick only the model IDs that `claude-sonnet-4-5` [matches](#restrict-model-selection), not every Sonnet model.
 
 ### Mantle model IDs
 
@@ -947,7 +947,12 @@ When you set an `ANTHROPIC_DEFAULT_*_MODEL` variable, the `/model` picker shows
 >
 > An `availableModels` allowlist delivered through [MDM or a managed settings file](https://code.claude.com/docs/en/managed-settings.md#delivery-mechanisms) still applies when using third-party providers; [server-managed settings are not delivered there](https://code.claude.com/docs/en/server-managed-settings.md#platform-availability).
 >
-> Filtering matches on a model alias such as `opus`, a version prefix such as `claude-opus-4-8`, or the full provider-form model ID. Provider-specific prefixes such as `us.anthropic.` are not stripped, so to allow a specific model, list its full provider-form ID, or map it through [`modelOverrides`](#override-model-ids-per-version). For a pinned model, that ID is the value you set in its `ANTHROPIC_DEFAULT_*_MODEL` variable. Any `[1m]` suffix is stripped from both the allowlist entry and the requested model before matching.
+> Filtering matches on a model alias such as `opus`, a version prefix such as `claude-opus-4-8`, or the full provider-form model ID. Provider-specific prefixes such as `us.anthropic.` are not stripped, so to allow a specific model, map it through [`modelOverrides`](#override-model-ids-per-version) or list its full provider-form ID:
+>
+> * **Google Cloud's Agent Platform**: when the ID Claude Code requests carries an `@` date, such as `claude-sonnet-4-5@20250929`, include the date in your allowlist entry. On its own, `claude-sonnet-4-5` doesn't match that ID under either [`availableModelsMatch`](https://code.claude.com/docs/en/settings-reference#availablemodelsmatch) setting.
+> * **Pinned models**: list the value you set in the model's `ANTHROPIC_DEFAULT_*_MODEL` variable
+>
+> Any `[1m]` suffix is stripped from both the allowlist entry and the requested model before matching.
 
 ### Customize pinned model display and capabilities
 
diff --git a/content/en/docs/claude-code/network-config.md b/content/en/docs/claude-code/network-config.md
index 2088b38678..ed9fcde32a 100644
--- a/content/en/docs/claude-code/network-config.md
+++ b/content/en/docs/claude-code/network-config.md
@@ -240,9 +240,11 @@ If you install Claude Code through npm or manage your own binary distribution, e
 
 The two Datadog intake hosts carry only optional operational telemetry, and setting [`CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC`](https://code.claude.com/docs/en/env-vars) disables both. Sessions on third-party providers never send to these hosts, even when a platform sets [`CLAUDE_CODE_PROVIDER_MANAGED_BY_HOST`](https://code.claude.com/docs/en/env-vars) and telemetry metrics default on. See [Telemetry services](https://code.claude.com/docs/en/data-usage.md#telemetry-services) for everything Claude Code sends and how to disable it before finalizing your allowlist.
 
+### Cloud provider and LLM gateway routing
+
 When using [Amazon Bedrock](https://code.claude.com/docs/en/amazon-bedrock.md), [Google Cloud's Agent Platform](https://code.claude.com/docs/en/google-vertex-ai.md), [Microsoft Foundry](https://code.claude.com/docs/en/microsoft-foundry.md), or a signed-in [Claude apps gateway](https://code.claude.com/docs/en/claude-apps-gateway) session, model traffic and authentication go to your provider or gateway instead of `api.anthropic.com`, `claude.ai`, or `platform.claude.com`. The WebFetch tool still calls `api.anthropic.com` for its [domain safety check](https://code.claude.com/docs/en/data-usage.md#webfetch-domain-safety-check) unless you set `skipWebFetchPreflight: true` in [settings](https://code.claude.com/docs/en/settings.md).
 
-When routing through an [LLM gateway](https://code.claude.com/docs/en/llm-gateway) with [`ANTHROPIC_BASE_URL`](https://code.claude.com/docs/en/llm-gateway-connect#set-the-base-url-and-credential), the [fast mode](https://code.claude.com/docs/en/fast-mode.md) availability check still calls `api.anthropic.com` rather than the gateway base URL. The check does honor a configured HTTP proxy, so where a network block is the cause, an allowlist entry for `api.anthropic.com` in the proxy is the fix. A network block fails the check only where the host is unreachable even through the proxy, and fast mode then reports a connectivity error. The same connectivity error appears when the check presents a gateway-issued credential that Anthropic rejects; allowlisting doesn't help there, since nothing is blocked. See [use fast mode behind proxies and LLM gateways](https://code.claude.com/docs/en/fast-mode.md#use-fast-mode-behind-proxies-and-llm-gateways) for the variables that restore it.
+If your developers use [fast mode](https://code.claude.com/docs/en/fast-mode.md) behind an [LLM gateway](https://code.claude.com/docs/en/llm-gateway) set with [`ANTHROPIC_BASE_URL`](https://code.claude.com/docs/en/llm-gateway-connect#set-the-base-url-and-credential), keep `api.anthropic.com` reachable through your proxy. When Claude Code sends the fast mode availability check, it goes to that host through any configured HTTP proxy, never to the gateway. For when the check isn't sent, and the variable that restores fast mode in each case, see [Use fast mode behind proxies and LLM gateways](https://code.claude.com/docs/en/fast-mode.md#use-fast-mode-behind-proxies-and-llm-gateways).
 
 ### Organization IP allowlists and proxy egress
 
diff --git a/content/en/docs/claude-code/plugins/mods/gallery.md b/content/en/docs/claude-code/plugins/mods/gallery.md
index 2aebe05318..b8ac25cdc4 100644
--- a/content/en/docs/claude-code/plugins/mods/gallery.md
+++ b/content/en/docs/claude-code/plugins/mods/gallery.md
@@ -353,12 +353,35 @@ An `Image` draws as a picture in these terminals:
 
 In any other terminal, the user sees the `Image`'s `alt` text, dimmed, in place of the picture. Write `alt` text that stands on its own, because it also shows in these cases, among others:
 
-* **tmux and screen**: a session running inside tmux or screen, in any terminal.
+* **GNU screen**: a session running inside screen, in any terminal.
+* **tmux**: a session running inside tmux that misses a [requirement for drawing inside tmux](#draw-an-image-inside-tmux).
 * **Background sessions**: every [background session](https://code.claude.com/docs/en/agent-view.md), whatever terminal it's attached from.
 * **iTerm2 outside fullscreen rendering**: in iTerm2 the picture draws only under [fullscreen rendering](https://code.claude.com/docs/en/fullscreen.md), and not while [`CLAUDE_CODE_ALT_SCREEN_FULL_REPAINT`](https://code.claude.com/docs/en/env-vars) is set to `1`. To see the picture, run `/tui fullscreen` at the Claude Code prompt and leave that variable unset.
-* **A file path source in iTerm2**: iTerm2 draws an `Image` whose `source` prop holds `png` or `rgba` bytes, and shows the `alt` text for one whose `source` names a `file`. If your mod has iTerm2 users, pass the picture as base64 in `source.png` or `source.rgba` rather than as a path in `source.file`.
+* **A file path source in iTerm2 or tmux**: in iTerm2 and inside tmux, an `Image` whose `source` names a `file` shows the `alt` text instead of the picture. If your mod has iTerm2 or tmux users, pass the picture as base64 in `source.png` or `source.rgba` rather than as a path in `source.file`.
 
-If your mod's users see the dimmed text in a terminal that draws kitty graphics protocol images with Unicode placeholders, they can set [`CLAUDE_CODE_FORCE_TERMINAL_IMAGES`](https://code.claude.com/docs/en/env-vars) to `1`. Inside tmux or screen that doesn't help: the `alt` text goes away, and Claude Code sends the picture without wrapping it for tmux or screen passthrough.
+If your mod's users see the dimmed text in a terminal that draws kitty graphics protocol images with Unicode placeholders, they can set [`CLAUDE_CODE_FORCE_TERMINAL_IMAGES`](https://code.claude.com/docs/en/env-vars) to `1`. They shouldn't set it inside GNU screen, inside tmux older than 3.3, in a tmux popup, or with tmux's `allow-passthrough` off. There they see no picture and a box in place of the `alt` text.
+
+#### Draw an `Image` inside tmux
+
+If an `Image` shows its `alt` text inside tmux, check these requirements along with the [other `alt` text cases](#image-and-client) such as a background session:
+
+* Claude Code v2.1.310 or later
+* tmux 3.3 or later
+* Claude Code runs in a tmux pane, not a tmux popup
+* tmux runs inside kitty 0.28 or later, Ghostty, or iTerm2 3.5 or later
+* The tmux options `focus-events` and `allow-passthrough` are `on`. Inside kitty or Ghostty, `allow-passthrough` can also be `all`.
+* Inside iTerm2, tmux runs [without `-CC`](https://code.claude.com/docs/en/fullscreen#use-with-tmux), [fullscreen rendering](https://code.claude.com/docs/en/fullscreen.md) is on, and `CLAUDE_CODE_ALT_SCREEN_FULL_REPAINT` is unset.
+* Inside iTerm2, the tmux window is no bigger than the iTerm2 window. To check, run `tmux display-message -p '#{window_bigger}'` in that tmux window. If it prints `1`, make the tmux window fit, then restart Claude Code.
+* The mod's author passes the picture as `png` or `rgba` bytes, not as a `file` path. If you use a mod you didn't write and the other requirements hold, ask its author to check this one.
+
+For each tmux option that isn't already set as required, run its command in your shell:
+
+```bash theme={null}
+tmux set -g allow-passthrough on
+tmux set -g focus-events on
+```
+
+Then detach from tmux, attach again, and restart Claude Code. Restart it again whenever you attach tmux from a different terminal. To keep both options across tmux server restarts, [add both lines to `~/.tmux.conf`](https://code.claude.com/docs/en/terminal-config#configure-tmux) too.
 
 ## See where a mod can draw
 
diff --git a/content/en/docs/claude-code/plugins/mods/troubleshoot.md b/content/en/docs/claude-code/plugins/mods/troubleshoot.md
index c9fe31b304..125b11e50e 100644
--- a/content/en/docs/claude-code/plugins/mods/troubleshoot.md
+++ b/content/en/docs/claude-code/plugins/mods/troubleshoot.md
@@ -106,7 +106,7 @@ Rewrite the code so its scopes nest less deeply.
 
 Code in the hooks module is nested too deeply, or its chain of imports is too long, for Claude Code to load it. The line starts with the mod's name and `hooks module did not load:`, then gives a file's name and this reason.
 
-Look through that file and the files reached through its imports for the most deeply nested part and rewrite it to nest less, or shorten the chain of imports. If you installed the mod and didn't write it, ask its author to.
+In that file and the files its imports reach, find the most deeply nested code and rewrite it to nest less, or shorten the chain of imports. If you didn't write the mod, ask its author to fix it.
 
 ### `the parser stopped` or `the engine ran out of stack loading the file`
 
diff --git a/content/en/docs/claude-code/routines.md b/content/en/docs/claude-code/routines.md
index 932a6238da..b443db5e91 100644
--- a/content/en/docs/claude-code/routines.md
+++ b/content/en/docs/claude-code/routines.md
@@ -25,7 +25,7 @@ A scheduled task doesn't need a schedule:
 * A task with only an API trigger runs when you call its endpoint.
 * A task with only a GitHub trigger runs when a matching repository event occurs.
 
-Scheduled tasks are available on Pro, Max, Team, and Enterprise plans. Create and manage them at [claude.ai/code/routines](https://claude.ai/code/routines), or from the CLI with `/schedule`. The earlier name, routines, [still appears](#where-the-name-routines-still-appears) in the web address, the CLI, and the API.
+Scheduled tasks are available on Pro, Max, Team, and Enterprise plans. Create and manage them at [claude.ai/code/routines](https://claude.ai/code/routines), or from the CLI with `/schedule`. The earlier name, routines, [still appears](#where-the-name-routines-still-appears).
 
 > [!NOTE]
 >
@@ -66,7 +66,12 @@ Scheduled tasks belong to your individual claude.ai account. They are not shared
 
 **1. Open the creation dialog**
 
-Go to [claude.ai/code/routines](https://claude.ai/code/routines) and click **New task**. If a menu opens first, select **Set up manually**. The **New scheduled task** dialog opens. The menu's other option, **Create with Claude**, lets you describe the task in a chat and have Claude create it instead.
+Go to [claude.ai/code/routines](https://claude.ai/code/routines) and click **New task** to open the **New scheduled task** dialog. Check for these screens before you continue:
+
+* If the button reads **New routine** instead of **New task**, click **New routine** and continue with [Full-page form](#full-page-form).
+* In the Desktop app, if a menu with **Local** and **Cloud** opens, go to [Full-page form](#full-page-form).
+* If a menu opens with **Create with Claude** and **Set up manually**, select **Set up manually** to open the dialog. **Create with Claude** lets you describe the task in a chat and have Claude create it instead.
+* If a full page opens in place of the dialog, go to [Full-page form](#full-page-form).
 
 If **Repositories** and **Environment** are already showing when the dialog opens, see [how that dialog differs](#dialog-with-repositories-and-environment-in-the-main-view). Otherwise, this dialog also creates scheduled tasks for claude.ai chat. To make yours what the dialog calls a Claude Code task, select a repository or add a GitHub event or API trigger in the steps that follow. That kind of task runs Claude Code in a cloud session.
 
@@ -126,6 +131,17 @@ Follow the [steps to create from the web](#create-from-the-web), and fill in eac
 
 Select the repository before you add a GitHub event trigger, because that trigger is unavailable until a repository is selected.
 
+#### Full-page form
+
+In the Desktop app, if a menu with **Local** and **Cloud** opens, select **Cloud**. A page titled **New routine** or **New scheduled task** opens. Fill in its fields:
+
+* **Name**: enter one.
+* **Instructions**: enter the prompt. In the same box, select the model, the repositories, and the environment. For what each one controls, see the steps under [Create from the web](#create-from-the-web).
+* **Select a trigger**: select **Schedule**, **GitHub event**, or **API**. For a schedule, see [Add a schedule trigger](#add-a-schedule-trigger). For a [GitHub event](#add-a-github-trigger), select a repository. For an [API trigger](#add-an-api-trigger), copy the token from the **API token** dialog that opens after you click **Create**, because it is shown once. To combine several triggers, click **Add another trigger**.
+* **Connectors**: all of your connected connectors are included by default, so remove the ones the task doesn't need.
+
+If **Create** is unavailable, hover over it to see what the form still needs. Click **Create**, and the task's detail page opens.
+
 ### Create from the CLI
 
 Run `/schedule` in any session to create a scheduled task conversationally. You can also pass a description directly, for a recurring task like `/schedule daily PR review at 9am` or a one-off like `/schedule clean up feature flag in one week`. Claude walks through the same information the web dialog collects, then saves the task to your account. The command is also available under the alias `/routines`.
@@ -152,6 +168,7 @@ A schedule trigger runs the task on a recurring cadence, or once at a specific f
 * **Runs on the hour**: if you schedule a run exactly on the hour, such as 9:00, it can start several minutes late. To start close to the scheduled time, pick a few minutes past the hour, for example 9:07.
 * **Custom intervals**: for a cadence the presets lack, create the task and select **Custom** in its [edit dialog](#edit-and-control-scheduled-tasks). Then enter a cron expression, such as `0 */2 * * *` for every two hours. To set one from the CLI, run [`/schedule update`](#manage-scheduled-tasks-from-the-cli). Expressions that run more often than once per hour are rejected.
 * **Time zone**: when you pick a preset frequency, enter the time in your local time zone.
+* **Cron expression time zone**: when the expression is five fields alone, write the hours in UTC, so `0 9 * * 1-5` runs at 9:00 AM UTC on weekdays. If the field opens with a `CRON_TZ=` prefix, keep it and write the hours in its zone, or delete it and write them in UTC.
 
 #### Schedule a one-off run
 
@@ -455,6 +472,7 @@ While your subscription is paused, your scheduled tasks are put on hold and don'
 
 Scheduled tasks were previously called routines, and these places keep the earlier name. Each one refers to the same feature:
 
+* **App**: in some accounts the sidebar entry and page title read **Routines**, the button reads **New routine**, and other labels say routine. To create a task there, see [Full-page form](#full-page-form).
 * **Web address**: `claude.ai/code/routines`
 * **CLI**: the `/routines` alias for `/schedule`, the command's description, and Claude's replies while it sets up a task
 * **API**: the `/fire` endpoint path, its beta header, its response `type`, the `<routine-fire-payload>` tag, and the [Trigger a routine through the API](https://platform.claude.com/docs/en/api/claude-code/routines-fire) reference page
diff --git a/content/en/docs/claude-code/sandboxing.md b/content/en/docs/claude-code/sandboxing.md
index 0c24d805ae..f897bff00a 100644
--- a/content/en/docs/claude-code/sandboxing.md
+++ b/content/en/docs/claude-code/sandboxing.md
@@ -537,7 +537,7 @@ Inside the directories that sandboxed commands can write to, the sandbox still d
 
 * **In your working directory and the directories above it**: the `.claude` settings files, the `.claude/skills`, `.claude/agents`, `.claude/commands`, and `.claude/hooks` directories, `.mcp.json`, and the files Claude Code runs on its own, such as `.claude/workflows` and `.claude/scheduled_tasks.json`
 * **In your working directory only**: shell startup files such as `.bashrc` and `.zshrc`, `.gitconfig`, the `.vscode` and `.idea` directories, and `hooks` and `config` inside `.git`
-* **Files that would turn your working directory into a bare git repository**: `HEAD`, `objects`, and `refs` at the top level, plus existing `config` and `hooks` entries there when a `HEAD` sits beside them. A file named `config` is denied even with no `HEAD`. On Linux and WSL2, the sandbox deletes a top-level `HEAD` file or `objects` or `refs` directory that appears while a sandboxed command is running
+* **Files that would turn your working directory into a bare git repository**: `HEAD`, `objects`, and `refs` at the top level, plus existing `config` and `hooks` entries there when a `HEAD` file or symlink sits beside them. A file named `config` is denied even with no `HEAD`. [A `HEAD`, `objects`, or `refs` that appears later can be deleted](#when-the-sandbox-deletes-head-objects-or-refs). On Linux and WSL2, a sandboxed command can create one where none exists.
 * **In `~/.claude`, or the directory `CLAUDE_CONFIG_DIR` points to**: most of its contents, plus `~/.claude.json` and the `.credentials.json` credential store
 
 If a symlink appears at a protected settings file's path during the session, the sandbox also denies writes to the file it points to, starting with the next command.
@@ -552,6 +552,12 @@ To see most of these paths resolved for your machine, run `/sandbox` and open th
 
 If `git merge` or `git checkout` fails with `unable to unlink old` on one of these paths, see [A git command fails with `unable to unlink old`](#a-git-command-fails-with-unable-to-unlink-old).
 
+#### When the sandbox deletes `HEAD`, `objects`, or `refs`
+
+After a sandboxed command ends, a newer top-level `HEAD`, `objects`, or `refs` entry in your working directory is deleted unless it's a folder with contents. Newer means the entry wasn't there when the sandbox last built its configuration: at session start, or after a change such as [`/cd`](https://code.claude.com/docs/en/commands).
+
+A newer `objects` or `refs` folder with contents is deleted too, with its contents, when a `HEAD` file or symlink was there the last time the sandbox built its configuration. To keep a folder, see [A folder named `objects` or `refs` disappears after a command](#a-folder-named-objects-or-refs-disappears-after-a-command).
+
 #### Denied paths that pass through a symlink
 
 On macOS, when a denied path passes through a symlink, such as a `~/.claude` that is a link into a dotfiles repository, the sandbox also denies the path's real location. This covers the sandbox's own denials and your literal `denyWrite` and `denyRead` entries.
@@ -881,6 +887,12 @@ When Claude pipes text to one of these tools, adding the tool to [`excludedComma
 
 After the failure, Claude may [offer to rerun the command outside the sandbox](#the-unsandboxed-retry-escape-hatch). Approve that retry, or run the git command yourself in another terminal. If you've set `allowUnsandboxedCommands` to `false`, Claude can't offer the retry, so run the command yourself.
 
+### A folder named `objects` or `refs` disappears after a command
+
+A top-level `objects` or `refs` folder that appeared during the session can be [deleted after a sandboxed command ends](#when-the-sandbox-deletes-head-objects-or-refs). It doesn't matter whether a command, Claude, or you created it. To keep a folder, leave something in it. If a `HEAD` file or symlink has been at the top level during the session, move it away, then restart every Claude Code session open there.
+
+Before v2.1.307, the folder was deleted even with something in it and no `HEAD`. On an earlier version, [update Claude Code](https://code.claude.com/docs/en/setup.md#update-claude-code).
+
 ### Bubblewrap fails to start inside a container
 
 In an unprivileged container, [bubblewrap](#os-level-enforcement) can't mount a fresh `/proc` filesystem, so sandboxed commands fail with a `bwrap` error such as `Can't mount proc on /newroot/proc: Operation not permitted`. Set [`enableWeakerNestedSandbox`](https://code.claude.com/docs/en/settings-reference#sandbox-enableweakernestedsandbox) to `true` so the sandbox bind-mounts the container's existing `/proc` instead. Only use this setting when the outer container already provides the isolation boundary you need, since the setting exposes process information to sandboxed commands that a fresh `/proc` mount would hide.
diff --git a/content/en/docs/claude-code/self-hosted-environments-configuration.md b/content/en/docs/claude-code/self-hosted-environments-configuration.md
index c9f46ebbb7..30fb1de7be 100644
--- a/content/en/docs/claude-code/self-hosted-environments-configuration.md
+++ b/content/en/docs/claude-code/self-hosted-environments-configuration.md
@@ -36,6 +36,7 @@ The runner sets the following in the wrapper's environment:
 | `CLAUDE_CODE_REMOTE_SESSION_UUID` | The same session ID in canonical UUID form, for systems that key on UUIDs. |
 | `CLAUDE_CODE_REMOTE_SLACK_THREAD_URL` | For a [Claude Tag](https://claude.com/docs/claude-tag/overview) session that belongs to one Slack thread, the link to that thread. Unset for other sessions, and can be unset for a thread session too. |
 | `CLAUDE_CODE_REMOTE_SLACK_THREAD_TS` | For a Claude Tag session that belongs to one Slack thread, that thread's Slack timestamp, such as `1700000000.000100`. Can be unset, and can be set when `CLAUDE_CODE_REMOTE_SLACK_THREAD_URL` isn't, so check each variable on its own. |
+| `CLAUDE_CODE_REMOTE_SLACK_CHANNEL_ID` | For a Claude Tag session, the ID of the Slack channel or direct message that the session serves or that its thread is in, such as `C0123ABCDE`. A Slack timestamp identifies a message within one channel, so record this ID together with `CLAUDE_CODE_REMOTE_SLACK_THREAD_TS`. Unset for other sessions, and can be unset for a Claude Tag session too. |
 | `CLAUDE_SESSION_INGRESS_TOKEN_FILE` | Absolute path to a per-session file holding the current session JWT, kept fresh across token refreshes. Shell subprocesses read it for their `Authorization` header when downloading attachments the user added to the session. `exec` preserves the variable automatically; a wrapper that rebuilds the child's environment must carry the variable over, or attachment downloads silently stop working. |
 | `CLAUDE_CONFIG_DIR` | Per-session Claude config directory, written at session start from the snapshot of the runner host's config that the runner captures at startup; see [Permissions and tool approval](#permissions-and-tool-approval). Writes here are isolated to this session. The directory stays under `<base-dir>/_sessions/` after the session ends unless you start the runner with [`--remove-session-state`](https://code.claude.com/docs/en/self-hosted-environments-reference#runner-cli-flags); see [Reuse a pre-warmed checkout](https://code.claude.com/docs/en/self-hosted-environments-deploy.md#reuse-a-pre-warmed-checkout). |
 | `CLAUDE_CODE_REMOTE_MCP_CONFIG` | Path to a file in `CLAUDE_CONFIG_DIR` holding the MCP server definitions that Anthropic's control plane delivered for this session. If your wrapper rebuilds the child's environment, carry this variable over. Without it, when the control plane updates the delivered servers, the child shuts down any stdio, HTTP, or SSE server your wrapper adds with [`--mcp-config`](https://code.claude.com/docs/en/cli-reference#cli-flags) that isn't in the update. Requires Claude Code v2.1.299 or later. |
@@ -44,11 +45,11 @@ The runner sets the following in the wrapper's environment:
 
 The wrapper also inherits the rest of the child's managed environment, including any server-provided environment variables. `exec` propagates all of it automatically; if your wrapper spawns the child another way, forward the full environment.
 
-`CLAUDE_CODE_REMOTE_SLACK_THREAD_URL` and `CLAUDE_CODE_REMOTE_SLACK_THREAD_TS` reach your wrapper or [`command` hook](#command). They also reach what the session runs, such as shell commands, git hooks, and Claude Code hooks. The `checkout`, `post-session`, and `spawn-runner` hooks don't receive them.
+You can read the `CLAUDE_CODE_REMOTE_SLACK_*` variables in your wrapper or [`command` hook](#command), and in what the session runs, such as shell commands, git hooks, and Claude Code hooks. The `checkout`, `post-session`, and `spawn-runner` hooks don't receive them.
 
 ### Give a default to variables that can be unset
 
-`CCR_SESSION_ACCOUNT_EMAIL`, `CLAUDE_RUNNER_CLIENT_PLATFORM`, `CLAUDE_CODE_REMOTE_SLACK_THREAD_URL`, and `CLAUDE_CODE_REMOTE_SLACK_THREAD_TS` can each be unset. If your script uses `set -u`, Bash stops with `unbound variable` when it expands one that's unset, so expand them with a default, such as `"${CCR_SESSION_ACCOUNT_EMAIL:-}"`.
+If your script uses `set -u`, expand `CCR_SESSION_ACCOUNT_EMAIL`, `CLAUDE_RUNNER_CLIENT_PLATFORM`, `CLAUDE_CODE_REMOTE_SLACK_THREAD_URL`, `CLAUDE_CODE_REMOTE_SLACK_THREAD_TS`, and `CLAUDE_CODE_REMOTE_SLACK_CHANNEL_ID` with a default, such as `"${CCR_SESSION_ACCOUNT_EMAIL:-}"`. Each can be unset, and under `set -u` Bash stops with `unbound variable` when it expands an unset one.
 
 ### Quote the arguments and variables your script expands
 
@@ -89,6 +90,26 @@ In your wrapper script or [`command` hook](#command), handle these flags as foll
 * **Pass them through**: end the wrapper with `exec "$CLAUDE_RUNNER_CLAUDE_BIN" "$@"`, which forwards the file flags along with every other argument. Don't drop or rewrite them. If a session loses a prompt file flag, it runs without the instructions the control plane sent for it.
 * **On a runner at v2.1.281 or later, a file flag you append replaces the server's, never adds to it**: each prompt file flag takes a single value and Claude Code keeps the last occurrence, so if you append `--append-system-prompt-file <path>` after `"$@"`, your file's contents replace the server's appended instructions. To add instructions on top of the server's, put them in the runner image's `CLAUDE.md`, which the runner [seeds into every session's user-level config](#how-each-session’s-config-is-assembled).
 
+#### Fix `Argument list too long` at session start
+
+On Linux, if you join the control plane's prompt and your own text into one `--append-system-prompt` argument, the runner logs a line like this once the argument reaches 128 KB:
+
+```text theme={null}
+Session <id> finished: failed — reason: child exited 126: /opt/wrapper.sh: line 9: /usr/local/bin/claude: Argument list too long
+```
+
+Linux limits each single argument to 32 memory pages, or 128 KB with the usual 4 KB pages. The figure from `getconf ARG_MAX`, often 2 MB, is a separate limit on all arguments and the environment together.
+
+On Claude Code v2.1.283 or later, leave the file flags in `"$@"` and pass only your own text as `--append-system-prompt`. Claude Code [uses both](https://code.claude.com/docs/en/cli-reference.md#system-prompt-flags), the control plane's prompt first and then your own text:
+
+```bash theme={null}
+exec "$CLAUDE_RUNNER_CLAUDE_BIN" "$@" --append-system-prompt "$(cat /opt/team-instructions.md)"
+```
+
+On Linux, if your own text reaches 128 KB, move it to the runner image's `CLAUDE.md`, because it's still one argument.
+
+On v2.1.281 or v2.1.282, that command exits with `Cannot use both --append-system-prompt and --append-system-prompt-file`. On earlier versions, your text replaces the control plane's prompt with no error. On any of them, update first, or move your own text to `CLAUDE.md`.
+
 ### Provision credentials scoped to the session creator
 
 Use the `decode-token` subcommand to read claims from the session JWT. It reads the token from an argument, from `CLAUDE_CODE_SESSION_ACCESS_TOKEN`, or from stdin, in that order; see [Verify the token inside the session](https://code.claude.com/docs/en/self-hosted-environments-identity.md#verify-the-token-inside-the-session) for what it checks. The example below decodes the creator identity, exchanges it for short-lived AWS credentials, and execs into Claude Code:
@@ -122,7 +143,7 @@ Runs once per repository, in place of the runner's built-in clone and fetch. Use
 | Variable | Description |
 | :- | :- |
 | `CLAUDE_RUNNER_REPO_URL` | Repository URL to clone, after any `--git-host-rewrite` and `--git-ssh-rewrite` have been applied |
-| `CLAUDE_RUNNER_REPO_REF` | Revision to check out, as the session requested it: a branch, tag, commit SHA, or full reference name such as `refs/pull/<number>/head`. Empty means the repository's default branch. |
+| `CLAUDE_RUNNER_REPO_REF` | Revision to check out, as the session requested it: a branch, tag, commit SHA, or full reference name such as `refs/heads/<branch>` or `refs/pull/<number>/head`. Empty means the repository's default branch. |
 | `CLAUDE_RUNNER_CHECKOUT_PATH` | Absolute path where the working tree must be left |
 | `CLAUDE_RUNNER_SESSION_ID` | Session ID in the tagged `session_...` form, for logging and correlation |
 | `CLAUDE_RUNNER_SESSION_UUID` | The same session ID in canonical UUID form |
@@ -303,12 +324,12 @@ The spawned runner registers with the work order in place of the environment sec
 
 The contract has four rules, whichever platform your hook provisions on:
 
-1. **Be idempotent on `CLAUDE_RUNNER_ORDER_ID`.** Redelivery of the same request must spawn at most one runner. Derive a deterministic resource name from the order ID and let your platform reject the duplicate. Don't key on `CLAUDE_RUNNER_SESSION_ID` instead. Every re-request for a session carries the same session ID with a new order ID, so a workload named or deduplicated by the session ID is created once and never again for that session.
+1. **Be idempotent on `CLAUDE_RUNNER_ORDER_ID`.** Redelivery of the same request must spawn at most one runner. Derive a deterministic resource name from the order ID and let your platform reject the duplicate. Don't key on `CLAUDE_RUNNER_SESSION_ID` instead. Every re-request for a session carries the same session ID with a new order ID. A workload named or deduplicated by the session ID isn't created again while the first one exists.
 2. **Don't retry the workload.** One order ID means at most one created workload. If the runner never registers, Anthropic re-requests with a fresh order ID after `--expected-spawn-seconds`.
 3. **Use the exit-code contract.** Exit with the status that matches the outcome:
 
    * **Exit 0**: submitted.
-   * **Exit 1, or still running when `--hook-timeout` ends**: retryable failure. The session backs off and is re-offered.
+   * **Exit 1, or still running when `--hook-timeout` ends**: retryable failure. The session backs off and is re-offered. After 10 failed requests in a row, it's blocked as it is after exit 2 or higher.
    * **Exit 2 or higher**: non-retryable failure. The session is blocked from spawning again until a user sends it a new message or an [Owner](https://code.claude.com/docs/en/cloud-environments.md#organization-shared-environments) selects **Retry** on it in the environment's **Activity** tab.
 
    While a session backs off, it shows **Queued** in the **Activity** tab with no spawn error, so read the hook's output in the orchestrator's log. Once blocked, the session shows **Failed**. Expand it to read the spawn error, taken from the last 512 characters of the hook's stderr. Write an actionable error to stderr, and no secrets. In a shell hook, [keep transient failures retryable](#keep-transient-failures-retryable-in-a-shell-hook).
@@ -318,7 +339,41 @@ The contract has four rules, whichever platform your hook provisions on:
 
 Everything the hook writes to stdout or stderr appears in the orchestrator's log with credentials automatically redacted. If sessions stay queued, check the orchestrator's `/healthz` body for queue counts, then open your environment's **Activity** tab on the [**Cloud environments** admin page](https://claude.ai/admin-settings/cloud-environments): expand a failed session there for its spawn error, and select **Retry** to re-request it.
 
-A session that stays queued with no spawn error in the **Activity** tab can mean the hook is keyed on the session ID. To confirm, check whether your platform has a workload for that session's first spawn request and none for the re-requests. If so, key the workload on `CLAUDE_RUNNER_ORDER_ID` instead.
+#### Fix re-opened sessions that stay Queued or show Failed
+
+If re-opened sessions stay **Queued** or show **Failed**, or your hook times out on them, one cause is a hook that names or deduplicates workloads by the session ID. A session is re-opened when its user sends it a message after its runner has exited. For example, take a hook that builds each workload's name like this:
+
+```bash theme={null}
+name="runner-${CLAUDE_RUNNER_SESSION_ID}"
+```
+
+1. At the session's first spawn request, the hook creates a workload with that name, and a runner starts
+2. The runner exits, for example after [`--release-idle-session-min`](#make-on-demand-runners-exit-when-idle), and the user later re-opens the session
+3. The session's next spawn request carries the same session ID and a new order ID, so the hook builds the same name
+4. If your platform still has the workload from the first request, because nothing [removed](#make-on-demand-runners-exit-when-idle) it when its runner exited, the hook creates no new workload and no runner starts
+5. Each later spawn request for the session ends the same way
+
+Open your own hook and read what it does when the workload already exists, for example when your platform rejects the duplicate name. Find that behavior in the first column to see what the re-opened session shows in the **Activity** tab:
+
+| When the workload exists, your hook | **Queued** changes to **Failed** | Spawn error |
+| :- | :- | :- |
+| Exits 0 without creating anything | After 10 such requests in a row | `runner did not register within ETA after max attempts` |
+| Exits 1 | After 10 such requests in a row | Your hook's stderr tail, or `exit 1` if it wrote nothing to stderr |
+| Exits 2 or higher | Right away | Your hook's stderr tail, or `exit` and the code, such as `exit 2`, if it wrote nothing to stderr |
+| Waits until `--hook-timeout` ends | After 10 such requests in a row | Your hook's stderr tail, or `spawn-runner hook timed out after 60000ms` if it wrote nothing to stderr |
+
+In the last row's spawn error, `60000` is your `--hook-timeout` in milliseconds. When a hook waits until `--hook-timeout` ends, the orchestrator's log also gets a `timed out after` line.
+
+To fix the hook, build each name or key from `CLAUDE_RUNNER_ORDER_ID`, as [rule 1 of the hook contract](#the-spawn-runner-hook) requires. In the example, the name becomes:
+
+```bash theme={null}
+name="runner-${CLAUDE_RUNNER_ORDER_ID}"
+```
+
+If your hook waits, also make it exit once it has submitted the workload, because a waiting hook [delays its orchestrator's next hooks](https://code.claude.com/docs/en/self-hosted-environments-reference.md#orchestrator-cli-flags). After you change the hook, check each stuck session's status in the **Activity** tab:
+
+* **Queued**: the session gets its next spawn request on its own
+* **Failed**: select **Retry** on it as an Owner, or have its user send it a new message
 
 #### Make on-demand runners exit when idle
 
@@ -740,6 +795,27 @@ Outside [Claude Tag](https://claude.com/docs/claude-tag/overview) sessions, a se
 
 The runner's snapshot of the host's `~/.claude/` leaves out the `projects/` directory. Auto memory's default storage location is under that directory. If you put memory files there, the runner doesn't seed them into sessions, and they don't turn auto memory on.
 
+### Stop sessions that fail to fetch server-managed settings
+
+To keep a session that fetches [server-managed settings](https://code.claude.com/docs/en/server-managed-settings.md) from starting when that fetch fails, set [`forceRemoteSettingsRefresh`](https://code.claude.com/docs/en/settings-reference#forceremotesettingsrefresh) to `true` in the [`managed-settings.json`](https://code.claude.com/docs/en/settings#where-settings-live) in your runner image. A reply from Anthropic's API that your organization has no server-managed settings counts as a successful fetch.
+
+Before you add the key, check whether the environment runs Claude Tag channel sessions or sends model requests to Bedrock or Agent Platform:
+
+* **Claude Tag channel sessions**: leave the key out on runners in an environment that an Owner [routes Claude Tag channels to](https://code.claude.com/docs/en/cloud-environments.md#set-the-environment-a-claude-tag-channel-uses). Anthropic's API refuses these sessions' request for server-managed settings, so with the key set they fail to start. Put their rules in the runner image's `managed-settings.json`, which [they still read](https://code.claude.com/docs/en/managed-settings.md#where-and-when-a-policy-applies). To use the key for your other sessions, run those in a separate environment.
+* **Bedrock or Agent Platform**: sessions on these providers [don't fetch server-managed settings](#what-differs-from-sessions-on-the-anthropic-api), so they start whether or not you set the key. Enforce your rules from the same `managed-settings.json` instead.
+
+This `managed-settings.json` sets the key:
+
+```json managed-settings.json theme={null}
+{
+  "forceRemoteSettingsRefresh": true
+}
+```
+
+Set the key in that file even if you also set it in the claude.ai admin console. A new session has no [cached copy](https://code.claude.com/docs/en/server-managed-settings.md#fetch-and-caching-behavior) of your server-managed settings, so if you set the key only in the console, the session doesn't have it yet. If its fetch then fails, the session runs without those settings until a later fetch succeeds.
+
+To confirm that a failed settings fetch is why a session didn't start, look at [Claude Code's last output](#keep-stdin-and-file-descriptor-3-attached) in the session or the runner's log. It includes `Your organization requires remote managed settings to load, but they could not be loaded.`
+
 ### Repository settings in sessions with several repositories
 
 In a thread in a [project](https://code.claude.com/docs/en/claude-projects.md#what-threads-pick-up-from-your-repositories), no repository's `.claude/settings.json` takes effect as project settings and no repository's `.mcp.json` or skills load, wherever the thread starts. To give those threads a skill, add it to your runner image.
diff --git a/content/en/docs/claude-code/self-hosted-environments-deploy.md b/content/en/docs/claude-code/self-hosted-environments-deploy.md
index 039e80715a..720853ec4d 100644
--- a/content/en/docs/claude-code/self-hosted-environments-deploy.md
+++ b/content/en/docs/claude-code/self-hosted-environments-deploy.md
@@ -313,6 +313,26 @@ The per-session certificate file needs a system CA bundle at `/etc/ssl/certs/ca-
 
 For each session that uses Anthropic-managed git, the runner also logs a `[runner:warn]` line that begins `governed git: GIT_SSL_CAINFO is set` or `governed git: GIT_SSL_NO_VERIFY is set`. The line says what the runner did with that variable for its own git, for git inside the session, and for your lifecycle hooks. It ends with whether you need to change anything.
 
+### Add github.com repositories to Claude Tag channel sessions
+
+If Claude can't add a github.com repository to a Claude Tag channel session, make sure the channel has access to it, even when your runner can clone it. That access comes from settings on GitHub and in your Claude organization, not from your runner's git credentials.
+
+**1. Install the Claude GitHub App**
+
+Install the [Claude GitHub App](https://github.com/apps/claude) on the GitHub organization or account that owns the repository, and include that repository in the installation.
+
+**2. Link the GitHub organization or account**
+
+In [**Organization settings > Git providers**](https://claude.ai/admin-settings/source-control), link that organization or account to your Claude organization. An Owner of your Claude organization who also owns the GitHub organization can link it. See [Link your GitHub organization](https://claude.com/docs/claude-tag/admins/configure-github#link-your-github-organization).
+
+**3. Grant the repository**
+
+In [Claude Tag admin settings](https://claude.ai/admin-settings/claude-tag), grant the repository to the channel or to a wider scope that includes the channel: its Slack workspace or all of Slack. Someone with the Owner role or the Claude Tag Admin permission can grant it. A channel manager can also add it to their own channel if their GitHub account is an admin of the repository. See [Grant repository access](https://claude.com/docs/claude-tag/admins/configure-github#grant-repository-access).
+
+Then start a new thread in the channel and [name the repository](https://claude.com/docs/claude-tag/admins/configure-github#how-granted-repositories-reach-a-session) in your first message.
+
+If Claude still can't add the repository, see [If Claude can't reach a repository](https://claude.com/docs/claude-tag/admins/configure-github#if-claude-can%E2%80%99t-reach-a-repository) for where to check the GitHub link and the repository grant.
+
 ### Rewrite git URLs for private networks
 
 Repository URLs arrive from the control plane as HTTPS, with the hostname of your git host; for GitHub Enterprise, that's the hostname you configured for the [GitHub Enterprise integration](https://code.claude.com/docs/en/github-enterprise-server.md) on claude.ai. Two repeatable flags rewrite those URLs before clone:
@@ -376,10 +396,89 @@ resources:
 
 Builds and tests are usually the largest and most variable part of a session's load, so run a representative build of your repository, measure its peak CPU and memory, and raise any starting value that leaves no room for the Claude Code process on top of that peak.
 
-The runner uses `--capacity` to cap how many sessions it runs at once. It doesn't divide CPU or memory between them, so the sessions on a runner share the container's CPU and memory. To cap one session's share, apply limits from your [wrapper script](https://code.claude.com/docs/en/self-hosted-environments-configuration.md#wrapper-scripts). What to give one container therefore depends on how many sessions it serves at once:
+The runner uses `--capacity` to cap how many sessions it runs at once. It doesn't divide CPU or memory between them, so the sessions on a runner share the container's CPU and memory. To keep one session's memory use from ending the others, run one session per runner with [its own memory limit](#give-each-session-its-own-memory-limit).
 
 * **One session per runner**: give each container one session's values. Use this sizing at `--capacity 1`, which the [hardening section](#harden-your-deployment) recommends, and for [on-demand runners](https://code.claude.com/docs/en/self-hosted-environments-configuration.md#on-demand-runners), where you set the values on the workload your [`spawn-runner` hook](https://code.claude.com/docs/en/self-hosted-environments-configuration#the-spawn-runner-hook) submits, such as a Kubernetes Job's pod template.
 * **Several sessions per runner**: at a `--capacity` above one, multiply one session's values by the capacity, because up to that many sessions can run in the container at the same time. The [Kubernetes](#kubernetes) and [Docker Compose](#docker-compose) recipes run `--capacity 4` with no CPU or memory limits, so add limits sized for the capacity you run.
+* **Several runner containers on one host**: size the host for the sum of the runners' capacities, because each runner counts only its own sessions against `--capacity`:
+
+  * **Memory**: multiply one session's memory by the sum, then add what the host's own processes use
+  * **CPU**: multiply one session's CPU request by the sum. To let every session burst at once, multiply its CPU limit instead.
+
+  Give each runner its own container. Use the [same `--base-dir` path](#keep-the-base-directory-and-capacity-identical-across-runners) in each, on storage that no other runner's container mounts, so that each runner has [its own working directory](#harden-your-deployment).
+
+### Give each session its own memory limit
+
+To stop one session from ending the others when memory runs out, run each runner at `--capacity 1` under its own memory limit, set to one session's memory:
+
+* **In a container**: run one runner per container, and set the container's memory limit, such as `limits.memory` on Kubernetes, `--memory` on Docker, or `mem_limit` in a Compose file. Keep the sum of the containers' limits below the host's memory, because when the host itself runs out, the kernel can kill processes anywhere on the host.
+* **Under systemd without a container**: set `MemoryMax` on the runner's unit, and run one runner per host, because runners that [use the same `--base-dir`](#keep-the-base-directory-and-capacity-identical-across-runners) on one filesystem share the repositories cloned there. For example, at `--capacity 1` with no `checkout` hook, their sessions on one repository can work in the same checkout at once. To run several runners on one host, give each a container.
+
+When a container or unit reaches its memory limit, the kernel kills processes only inside it. If you set `--capacity` above one, the sessions share one limit. When they reach it, the kernel doesn't choose by session which processes to kill, so one session's memory use can end the others.
+
+On Kubernetes, you can't separate the sessions with either value of the kubelet's `singleProcessOOMKill` setting. You can't cap a session's total memory with a memory `ulimit` in your [wrapper script](https://code.claude.com/docs/en/self-hosted-environments-configuration.md#wrapper-scripts) either. The kernel applies a value such as `ulimit -v` to each process separately.
+
+### Leave room under process and thread limits
+
+To size a process and thread limit, measure what one session needs and multiply it by the number of sessions that share the limit. When those sessions reach the limit, the kernel refuses new processes and threads, so commands, builds, and tests in any of them can fail. The refused call returns `EAGAIN`, whose standard message is `Resource temporarily unavailable`.
+
+Suppose one session peaks at 300 processes and threads, and four sessions share the limit. Together they need 1,200, and with a limit of 2,400, you leave room for builds that need twice as much.
+
+#### Where to set each limit
+
+Each limit in this table counts threads as well as processes, and `pids.max` is the file that holds a cgroup's limit:
+
+| Limit | Where you set it | What shares it |
+| :- | :- | :- |
+| `pids.max` on Kubernetes | `podPidsLimit` in the kubelet configuration of the nodes that run runners. You can't set it in a Pod spec. | The containers of one Pod |
+| `pids.max` on Docker | `--pids-limit`, or `pids_limit` in a Compose file | One container |
+| `pids.max` under systemd | `TasksMax` on the runner's unit | One unit |
+| `ulimit -u` | The shell or service that starts the runner | Everything on the host that runs as the runner's user ID. Not enforced for root. |
+
+When you don't set `TasksMax`, systemd applies `DefaultTasksMax`, which defaults to 15% of the lowest of `kernel.pid_max`, `kernel.threads-max`, and the root cgroup's `pids.max`.
+
+#### Measure one session's peak
+
+To get the numbers for your own runners, measure one session on its host, which on Kubernetes is the node:
+
+**1. Start one runner alone**
+
+Start one runner at `--capacity 1` with nothing else in its container or systemd unit, alone on its host and in its environment:
+
+* **Its host**: use one that runs no other runner. You can then pick out its process in the next step.
+* **Its environment**: make it the only runner there, for example in an environment you [create for the test](https://code.claude.com/docs/en/self-hosted-environments-quickstart.md#set-up-manually). Sessions are routed to an environment and not to a runner.
+
+Don't start a session yet, because you need the directory from the next step before the build starts.
+
+**2. Find the runner's cgroup directory**
+
+On the host, not inside the container, find the runner's process ID, for example with `ps`. Read `/proc/<pid>/cgroup` for that ID:
+
+* **A line contains `:pids:`**: the host uses cgroup v1, and the directory is `/sys/fs/cgroup/pids` followed by the text after `:pids:`
+* **The only line starts with `0::`**: the host uses cgroup v2, and the directory is `/sys/fs/cgroup` followed by the text after `0::`
+
+**3. Run a representative build and record the peak**
+
+Run one session through a representative build, and take the peak from the runner's cgroup directory:
+
+* **The directory has `pids.peak`**: read the file after the build finishes
+* **The directory has no `pids.peak`**: read `pids.current` once a second while the build runs, and keep the highest value. A peak between two reads goes unseen, so treat that value as a low estimate.
+
+**4. Multiply by the sessions that share the limit**
+
+* **One runner's Pod, container, or unit**: multiply the peak by the runner's `--capacity`
+* **A limit that several runners share**: multiply the peak by the sum of their capacities
+
+Then add the peak of anything else that shares the limit, such as another container in the Pod.
+
+**5. Set the limit above the result**
+
+With a higher limit, you leave room for heavier builds, and with a lower one, you stop a fork bomb sooner.
+
+#### Check a `pids.max` limit
+
+* **Check whether `pids.max` was reached**: search the host's kernel log, for example with `dmesg`, for a line that contains `cgroup: fork rejected by pids controller in` and a cgroup's path. The kernel logs it only the first time it refuses a process or thread in that cgroup, so search the whole log.
+* **See the limit in force**: read `pids.max` in the runner's cgroup directory and in each directory above it. The lowest value is the limit in force, and `max` means no limit at that level.
 
 ## Kubernetes
 
@@ -577,7 +676,7 @@ Supply the clone in the image or on a persistent volume:
 
 What the reuse path does and doesn't guarantee:
 
-* **Any clone shape works**: a full, shallow, or single-branch clone at the path is used as-is. The runner never passes `--depth` when fetching into an existing clone, so a full pre-warm keeps its full history and a shallow one stays shallow. `CLAUDE_RUNNER_FETCH_DEPTH` (`full`, `0`, or a number; default 50) controls only the cold clone the runner makes when no clone exists yet.
+* **Clone depth**: build the clone without `--depth`, with or without `--single-branch`. The runner never passes `--depth` when it fetches into a clone with an `origin` remote, even if you set [`CLAUDE_RUNNER_FETCH_DEPTH`](https://code.claude.com/docs/en/self-hosted-environments-reference#environment-variable-only-settings). With a full clone, each session downloads only the commits the clone lacks. With a shallow clone, a session on a branch that forked before the clone's oldest commit downloads that branch's whole history.
 * **Tracked changes reset, untracked files persist**: at `--capacity 1`, each session starts from a hard reset that wipes the previous session's tracked modifications, but the runner never runs `git clean`, so untracked files from the locked owner's earlier sessions stay in the tree.
 * **Per-session directories persist too**: alongside the checkout, the runner creates per-session entries under `<base-dir>/_sessions/` for every session it runs. The session's Claude config directory holds a local copy of the conversation transcript. Next to it sit the session's uploaded files, when the session has any. The session directory sits there too: it holds any per-session worktrees and `checkout` hook checkouts while the session runs, and it keeps whatever else Claude wrote in it.
 
@@ -587,6 +686,12 @@ What the reuse path does and doesn't guarantee:
 * **With the git proxy, a `reftable` pre-warm loses its refs**: when the runner sanitizes `.git/` before each session, it keeps `.git/refs/` and removes the `.git/reftable/` directory. A clone pre-warmed in git's `reftable` ref format loses its refs that way, so pre-warm the clone in git's `files` ref format instead.
 * **Long clones need no workaround**: the runner bounds each git operation with a 120-second no-progress watchdog and a 30-minute hard cap, not a flat timeout, so a slow cold clone that keeps reporting progress completes.
 
+### Confirm that the runner uses your clone
+
+To confirm that the runner uses your clone, start it with [`--log-level debug`](https://code.claude.com/docs/en/self-hosted-environments-reference#runner-cli-flags) and start a session on the repository. The runner logs `Prefetched repo found at` and the clone's path. If it logs `No prefetched repo, fresh init at` instead, it found no usable clone at the path in that line. Check that your clone is at that path, owned by the runner's user, with a remote named `origin`.
+
+If the runner finds your clone and sessions still start slowly, check whether the clone is shallow.
+
 ## Pin the version
 
 Each session's child process runs the runner's own binary by default, and the runner turns off auto-update inside the sessions it spawns. With that default, every session runs the version you installed on the host or built into the image. A host-level update takes effect the next time the runner starts.
@@ -609,6 +714,23 @@ Two scaling approaches are available:
 * **Fixed fleet**: run a static set of runner replicas and scale on the [Prometheus metrics](https://code.claude.com/docs/en/self-hosted-environments-reference.md#prometheus-metrics) each runner serves
 * **On-demand runners**: run the `claude self-hosted-runner orchestrator` subcommand, which polls Anthropic for sessions that are queued with no runner available and invokes your `spawn-runner` hook to boot one per session. See [On-demand runners](https://code.claude.com/docs/en/self-hosted-environments-configuration.md#on-demand-runners).
 
+### Release idle sessions on a fixed fleet
+
+If sessions stay queued on a fixed fleet while every runner is online, idle sessions may be the cause. By default, a session keeps its slot after its turn finishes, and its runner stays locked to that session's [owner](https://code.claude.com/docs/en/self-hosted-environments#key-concepts). If your team's [cloud scheduled task](https://code.claude.com/docs/en/routines.md) starts a new session at each run, its idle sessions can fill every slot.
+
+To check, read `claude_code_self_hosted_runner_session_idle_seconds` in each runner's [Prometheus metrics](https://code.claude.com/docs/en/self-hosted-environments-reference.md#prometheus-metrics). Each session a runner holds has its own series: `0` while the session is busy, otherwise the seconds since it went idle. Choose the idle time you'd allow: longer than the pauses people take mid-task, and short enough that each run is released before the scheduled task's next one starts. Compare the series with it.
+
+* **Series above that time, such as `1800` for 30 minutes**: idle sessions hold those slots, so set `--release-idle-session-min`
+* **Every series below it**: no session has been idle that long. Add runners, or set [`--kill-session-after-min`](https://code.claude.com/docs/en/self-hosted-environments-reference#runner-cli-flags) for [sessions that never go idle](#some-sessions-don’t-count-as-idle).
+* **A runner with no series**: no session holds it. See **Sessions stay queued** under [Troubleshooting](#troubleshooting).
+* **A runner whose metrics don't answer**: its process may have exited. See **An environment that looks healthy** under [When the runner exits](#when-the-runner-exits).
+
+To release idle sessions, start every runner with [`--release-idle-session-min`](https://code.claude.com/docs/en/self-hosted-environments-reference#runner-cli-flags) and that time in minutes, such as `--release-idle-session-min 30`. The runner then releases any session that stays idle that long, whether a scheduled task or a person started it.
+
+* **Unpushed work**: a released session resumes at its next message, without the work it hadn't pushed. To keep its commits, see [Resumed sessions lose unpushed work](#additional-limitations).
+* **Runner exits**: a runner that releases its last session starts a [normal exit](#when-the-runner-exits). Have your supervisor restart it on a fresh filesystem, as [Harden your deployment](#harden-your-deployment) describes.
+* **Sessions that never go idle**: also set [`--kill-session-after-min`](https://code.claude.com/docs/en/self-hosted-environments-reference#runner-cli-flags), because [some sessions don't count as idle](#some-sessions-don’t-count-as-idle)
+
 ## Known issues and limitations
 
 The following are the limitations in this release, with workarounds where one exists.
@@ -642,9 +764,10 @@ Set the flag above your longest expected session, such as `--kill-session-after-
 ### Additional limitations
 
 * **Resumed sessions lose unpushed work**: a fresh runner clones the repository again from its starting branch, so work the session hadn't pushed is gone.
-  * **To keep committed work**: set [`--push-outcome-on-release`](https://code.claude.com/docs/en/self-hosted-environments-reference#runner-cli-flags) on every runner in the environment, because a runner without the flag resumes the session from its starting branch. A runner with the flag makes a best-effort push of the session's outcome branches before it releases, and the resumed session starts from those commits. The push uses the runner host's own git credentials, including on a runner that uses [Anthropic-managed git](#use-the-anthropic-git-proxy). Uncommitted changes are still lost.
+  * **To keep committed work**: set [`--push-outcome-on-release`](https://code.claude.com/docs/en/self-hosted-environments-reference#runner-cli-flags) on every runner in the environment, because a runner without the flag resumes the session from its starting branch. A runner with the flag makes a best-effort push of the session's outcome branches before it releases, and the resumed session starts from those commits. The push uses the runner host's own git credentials, including on a runner that uses [Anthropic-managed git](#use-the-anthropic-git-proxy).
   * **With a `checkout` hook**: repositories checked out via a [`checkout` lifecycle hook](https://code.claude.com/docs/en/self-hosted-environments-configuration#checkout) aren't pushed. Snapshot those from the [`post-session` hook](https://code.claude.com/docs/en/self-hosted-environments-configuration#post-session) instead.
   * **Before enabling the flag**: restrict who can push to `claude/*` refs on the source remote. On resume, the runner fetches the previously pushed branch without verifying who pushed it.
+  * **Uncommitted changes are still lost**: to prompt Claude to commit and push when it finishes responding, see [Prompt sessions to push their work](https://code.claude.com/docs/en/self-hosted-environments-configuration.md#prompt-sessions-to-push-their-work)
 * **A repository added mid-session can fail to clone**: Claude clones it with `git clone` over HTTPS. On a runner without [`--use-anthropic-git-proxy`](#use-the-anthropic-git-proxy), the clone fails with a git authentication error if nothing on the host can read the repository. Where you can, select every repository the session needs when you create it.
 * **Some connectors don't appear in self-hosted sessions**: a connector you haven't yet connected in claude.ai Settings isn't listed in a self-hosted session, and the session won't prompt you to connect it. Connect it in Settings first, then start a fresh session. Adding a connector to an already-running session also doesn't make its tools available to Claude; start a fresh session to pick up a newly added connector.
 * **When someone archives or deletes a session, or releases its runner from the session's menu**: don't count on the [`--push-outcome-on-release`](https://code.claude.com/docs/en/self-hosted-environments-reference#runner-cli-flags) push. To save commits in those cases, push `HEAD` to a rescue branch from a [`post-session` hook](https://code.claude.com/docs/en/self-hosted-environments-configuration#post-session). If you start from the example there, make it push even when nothing is uncommitted, because it pushes only after a snapshot commit.
@@ -684,6 +807,7 @@ Common issues:
 * **Sessions fail immediately after pickup**: open the session in claude.ai/code to see the error. If the error shows that git couldn't authenticate, check the runner's [git credentials](#configure-git). On a runner started with `--use-anthropic-git-proxy`, see [When sessions fail to start on a runner with the git proxy](#when-anthropic-doesnt-serve-a-session).
 
   An unwritable base directory stops the runner at startup instead of failing sessions. See the **Runner exits at startup with `cannot create or write to base directory`** entry in this list.
+* **A session is picked up, but Claude never answers its first message**: if your runners reach `api.anthropic.com` through a proxy, configure it to pass the session's `/worker/events/stream` response through as it arrives. Raising the runner's timeouts doesn't help. To confirm the cause in the runner's log, see [A session is picked up, but Claude never answers its first message](#when-a-sessions-first-message-is-never-answered).
 * **Sessions fail to start on a runner that set `--use-anthropic-git-proxy`**: look in the runner's log for `access denied by the git proxy`, or for a git error that names an `api.anthropic.com` address containing `/git_proxy/`. To tell whether Anthropic served the session and fix the cause, see [When sessions fail to start on a runner with the git proxy](#when-anthropic-doesnt-serve-a-session).
 * **Sessions can't reach the network through an authenticating egress proxy**: when the source you set with [`--proxy-authorization-command` or `--proxy-authorization-file`](#authenticate-to-an-egress-proxy) fails, times out after 30 seconds, or yields an empty value, the runner answers that connection `502 Bad Gateway` and logs why. The runner redacts the command's stderr in that log and never logs the header value. With `--proxy-authorization-command`, run the command yourself on the host to confirm it prints the whole header value on stdout. If the runner instead exits at startup with `could not start the proxy-authorization listener`, it couldn't open its loopback listener.
 * **Runner logs `Poll failed` lines containing `rejecting the malformed poll response`**: the runner received a work-poll response whose body isn't the queue's expected JSON. One cause is an intercepting proxy or a captive portal answering with its own page. If the runner connects through a proxy, configure the proxy to pass responses from `api.anthropic.com` through unaltered.
@@ -708,7 +832,11 @@ Common issues:
 * **A session fails to start with `This runner couldn't read`**: the runner asked the git host for a repository with its [git credentials](#configure-git) and got a not-found answer. The repository doesn't exist, or those credentials can't reach the repository.
   * **If you administer the runner**: give its git credentials read access to the repository, then start a new session.
   * **If you started the session**: if the repository doesn't exist, start a new session with the right repository. If the runner can't reach the repository, ask the runner's administrator to grant access, then start a new session.
-* **Sessions take minutes to start**: the initial clone usually dominates. Watch the `claude_code_self_hosted_runner_session_init_duration_seconds` [metric](https://code.claude.com/docs/en/self-hosted-environments-reference.md#prometheus-metrics) to confirm, and cut the clone with a [pre-warmed checkout](#reuse-a-pre-warmed-checkout) or a smaller `CLAUDE_RUNNER_FETCH_DEPTH`.
+* **Sessions take minutes to start or resume**: one cause is a fresh clone. On a fleet that starts each runner on an empty disk, with no [`checkout` hook](https://code.claude.com/docs/en/self-hosted-environments-configuration#checkout), the runner clones the session's repositories afresh before it starts Claude Code. A session that resumes on an empty disk waits for the same clone again.
+
+  To skip the fresh clone, supply a [pre-warmed checkout](#reuse-a-pre-warmed-checkout). If you already supply one, [confirm that the runner uses it](#confirm-that-the-runner-uses-your-clone). Where the runner makes the clone itself and exits after one session, lower [`CLAUDE_RUNNER_FETCH_DEPTH`](https://code.claude.com/docs/en/self-hosted-environments-reference#environment-variable-only-settings) from its default of 50 commits to fetch less history.
+
+  If you use a hook, it runs in place of the runner's clone, so look at what your hook does instead. Watch the `claude_code_self_hosted_runner_session_init_duration_seconds` [metric](https://code.claude.com/docs/en/self-hosted-environments-reference.md#prometheus-metrics) to see how long starts take.
 * **Turns fail with a 401**: when a turn ends with a 401 or 403 from the Anthropic API, the runner fetches a fresh [`CLAUDE_CODE_OAUTH_TOKEN`](https://code.claude.com/docs/en/self-hosted-environments-configuration#wrapper-scripts) from Anthropic and passes it to the session. The failed turn isn't retried. This token is short-lived, and the runner rotates it over the session's stdin.
 
   When a fetch fails, the runner logs an `inference_token refresh failed` line that says when it will retry, and it keeps retrying for as long as the session runs.
@@ -788,6 +916,43 @@ When the runner has exited right after starting several times in a row, stop and
 
 For guided diagnosis on the runner host, run the [doctor subcommand](#troubleshooting).
 
+### A session is picked up, but Claude never answers its first message
+
+If a runner picks up a session but Claude never answers the first message, and your runners reach `api.anthropic.com` through a proxy, the proxy may be the cause. Anthropic sends a session its messages over one streaming response that stays open. If your proxy buffers it, or ends it before passing anything on, the first message never arrives. Other requests from the session still succeed.
+
+To fix it, change how the proxy handles this request:
+
+```text theme={null}
+GET https://api.anthropic.com/v1/code/sessions/<session-id>/worker/events/stream
+```
+
+* **Don't buffer the response**: pass it through as it arrives. Its content type is `text/event-stream`.
+* **Let the response stay open**: it can stay open for up to an hour. If the proxy has an idle timeout, keep it well above 15 seconds, because Anthropic sends a keep-alive at least that often by default.
+
+Then start a new session and check that Claude answers. Raising the runner's timeouts doesn't help: you only wait longer before the runner stops the session.
+
+#### Confirm the cause in the runner's log
+
+These steps are for runners on Claude Code v2.1.287 or later, at the default `--log-level info`. Older runners log these lines later, or not at all.
+
+1. Wait for [`--startup-timeout-min`](https://code.claude.com/docs/en/self-hosted-environments-reference#runner-cli-flags) to pass, 15 minutes by default. The runner then stops the session and logs a line that contains `no child output for` and ends `— releasing`.
+2. Search the runner's log for `SDKStartup: SSE`. These lines follow a `finished: interrupted` line, a few lines after the one in step 1. Most have no timestamp, so a log collector may show them elsewhere.
+3. Find the line in this table:
+
+| Log line contains | What to do |
+| :- | :- |
+| `SSE connect failed (no response in 30s)` or `SSE liveness timeout` | Check that the proxy forwards the request, passes the response's headers and data through as they arrive, and doesn't drop the connection |
+| `SSE connect failed (HTTP` and a status code | Check the proxy's own log. If the proxy answered the request itself, let the request through it. |
+| `SSE connect failed (` and any other text | The text in the parentheses is the error. Look for the same connection in the proxy's own log. |
+| `SSE stream ended by server`, again and again | Check the proxy's time limit for long-lived responses. A single such line is normal. |
+| `SSE reconnected after` | Look for one of the other lines after it. This one doesn't mean that anything reached the session. |
+
+If the log has none of these lines, or the proxy's log shows nothing wrong, [report an issue](#report-an-issue).
+
+#### Stop the session from trying again
+
+The session keeps the message pending, and a runner that can serve the session's owner picks the session up again. Until you change the proxy, the session waits the same way each time. To stop that, archive the session in claude.ai/code.
+
 ## What's next
 
 * [Customize sessions](https://code.claude.com/docs/en/self-hosted-environments-configuration.md): wrapper scripts, lifecycle hooks, on-demand runners, MCP servers, and permissions
diff --git a/content/en/docs/claude-code/self-hosted-environments-quickstart.md b/content/en/docs/claude-code/self-hosted-environments-quickstart.md
index 4bcbc078ce..a41b199a22 100644
--- a/content/en/docs/claude-code/self-hosted-environments-quickstart.md
+++ b/content/en/docs/claude-code/self-hosted-environments-quickstart.md
@@ -121,6 +121,8 @@ If the session doesn't start working, match what you see:
 * **The session fails to start with a git error**: if the error includes git's `could not read Username for` followed by your git host's URL, the runner had no HTTPS credentials for that host.
   * **Supply HTTPS credentials**: see [Configure git](https://code.claude.com/docs/en/self-hosted-environments-deploy.md#configure-git)
   * **Clone over SSH instead**: if the runner host already has an SSH key, see [Rewrite git URLs for private networks](https://code.claude.com/docs/en/self-hosted-environments-deploy.md#rewrite-git-urls-for-private-networks)
+  * **After either fix**: start the runner again and watch the failed session instead of starting a new one. If it has failed several times, wait several minutes for the runner to log `Picked up session`.
+  * **To use a different repository instead**: [archive](https://code.claude.com/docs/en/claude-code-on-the-web.md#archive-sessions) or [delete](https://code.claude.com/docs/en/claude-code-on-the-web.md#delete-sessions) the failed session, then start the runner again and start a new session. Otherwise, the runner can pick up the failed session instead of the new one.
 
 ### If the runner exits
 
diff --git a/content/en/docs/claude-code/self-hosted-environments-reference.md b/content/en/docs/claude-code/self-hosted-environments-reference.md
index 0e7a44e03a..d7d56e4eeb 100644
--- a/content/en/docs/claude-code/self-hosted-environments-reference.md
+++ b/content/en/docs/claude-code/self-hosted-environments-reference.md
@@ -83,7 +83,7 @@ The `self-hosted-runner orchestrator` subcommand, which spawns [on-demand runner
 
 | Flag | Default | Description |
 | :- | :- | :- |
-| `--hook-concurrency <n>` | `4` | Maximum `spawn-runner` hooks running in parallel. Also caps how many spawn requests are claimed per poll. |
+| `--hook-concurrency <n>` | `4` | Maximum `spawn-runner` hooks running in parallel. Also caps how many spawn requests are claimed per poll. The orchestrator checks for new spawn requests only after every hook it started has finished, so one slow hook delays that orchestrator's next hooks. |
 | `--hook-timeout <sec>` | `60` | Terminate the hook's process tree after this many seconds. The timeout plus its 5-second kill grace must stay below `--expected-spawn-seconds`; the orchestrator enforces this at startup. |
 | `--expected-spawn-seconds <sec>` | `120` | Expected p99 time from when the orchestrator receives a spawn request to when the runner registers, including any wait for capacity on your platform. The server enforces a range of 10 to 3600. Sent on every poll as the server-side lease: if no runner registers before it elapses, the session is re-offered with a fresh order ID. All replicas must share this value. |
 | `--min-idle <n>` | `0` | Keep at least N idle session slots free by spawning standby runners proactively. `0` disables pre-warming. Pair with the runner's `--exit-if-unused-min` so surplus standby runners reclaim themselves. |
@@ -116,7 +116,7 @@ These runner settings are read from the environment only and cover behavior most
 | `SELF_HOSTED_RUNNER_MAX_LIFETIME_GRACE_MS` | `900000` | How long the runner waits after a session reaches its `--kill-session-after-min` limit, for a running turn to finish or the release to complete, before it terminates the session |
 | `SELF_HOSTED_RUNNER_POST_TURN_SETTLE_MS` | `7000` | Cap on how long the runner counts a session as busy for the `--drain-wait-sec` drain after a turn finishes, while the session's process reports the turn's end to Anthropic. `0` or an unusable value falls back to the default, so the hold can't be turned off. Requires Claude Code v2.1.275 or later. |
 | `SELF_HOSTED_RUNNER_SIGKILL_GRACE_MS` | `30000` | How long the runner waits for the OS to deliver `SIGKILL` to a child stuck in uninterruptible I/O before exiting itself. Floored at `--post-session-hook-timeout-sec` plus 15 seconds, and 30 more when `--push-outcome-on-release` is set, so the effective minimum is 75 seconds at defaults. |
-| `CLAUDE_RUNNER_FETCH_DEPTH` | `50` | Git fetch depth for fresh clones. Set a positive integer, or `full` or `0` for a complete fetch. Repositories already present in the workspace keep their existing depth. |
+| `CLAUDE_RUNNER_FETCH_DEPTH` | `50` | Git fetch depth for fresh clones. Set a positive integer, or `full` or `0` for a complete fetch. For a clone that's already in the workspace, see [Reuse a pre-warmed checkout](https://code.claude.com/docs/en/self-hosted-environments-deploy.md#reuse-a-pre-warmed-checkout). |
 | `CLAUDE_RUNNER_FETCH_SERVER_PROGRESS_CAP_MS` | `600000` | How long in milliseconds, per attempt, a git fetch may wait for its first data while the git server's own progress numbers keep rising, as when the server prepares the pack for a large repository. `0` or `off` turns the wait off: such a fetch is then cut off after two minutes without data. Any other whole number is clamped to between `120000` and `1800000`, 2 to 30 minutes. Requires Claude Code v2.1.295 or later. |
 | `CLAUDE_RUNNER_SKIP_GIT_VERIFY` | unset | When `1`, skip the `.git` presence check after a `checkout` hook runs. Set this when your hook materializes a non-git source. |
 | `FORCE_AUTOUPDATE_PLUGINS` | unset | When `1`, let plugin marketplaces auto-update even though the binary is pinned |
@@ -254,11 +254,11 @@ groups:
         annotations:
           summary: "Runners are running mixed versions"
       - alert: ClaudeRunnerInitErrorsHigh
-        expr: increase(claude_code_self_hosted_runner_session_init_errors_total[10m]) > 3
+        expr: sum by (namespace) (increase(claude_code_self_hosted_runner_session_init_errors_total[10m])) > 3
         for: 5m
         labels: {severity: warning}
         annotations:
-          summary: "Runner {{ $labels.pod }}: >3 session init failures in 10m (checkout hook / git / token / pre-init crash)"
+          summary: "Sessions are failing before init (checkout hook / git / token / pre-init crash)"
       - alert: ClaudeRunnerPollErrors
         expr: sum by (pod) (rate(claude_code_self_hosted_runner_poll_errors_total[5m])) > 0
         for: 2m
@@ -266,11 +266,11 @@ groups:
         annotations:
           summary: "Runner {{ $labels.pod }}: PollWork failing ({{ $value | humanize }}/s over 5m)"
       - alert: ClaudeRunnerSessionStartHookErrors
-        expr: increase(claude_code_self_hosted_runner_session_start_hook_errors_total[10m]) > 3
+        expr: sum by (namespace) (increase(claude_code_self_hosted_runner_session_start_hook_errors_total[10m])) > 3
         for: 5m
         labels: {severity: warning}
         annotations:
-          summary: "Runner {{ $labels.pod }}: >3 SessionStart hook failures in 10m"
+          summary: "SessionStart hooks are failing"
 
   - name: claude-code-self-hosted-orchestrator
     rules:
@@ -287,7 +287,7 @@ groups:
         annotations:
           summary: "Orchestrator {{ $labels.pod }} has not polled in >90s (poll loop waits on hook execution)"
       - alert: ClaudeOrchestratorCircuitBroken
-        expr: claude_code_self_hosted_orchestrator_queue_circuit_broken_sessions > 0
+        expr: max by (namespace) (claude_code_self_hosted_orchestrator_queue_circuit_broken_sessions and on (instance) max_over_time(claude_code_self_hosted_orchestrator_connected[2m]) == 1) > 0
         for: 1m
         labels: {severity: critical}
         annotations:
diff --git a/content/en/docs/claude-code/self-hosted-environments.md b/content/en/docs/claude-code/self-hosted-environments.md
index ea06c20376..c0259db7de 100644
--- a/content/en/docs/claude-code/self-hosted-environments.md
+++ b/content/en/docs/claude-code/self-hosted-environments.md
@@ -30,7 +30,7 @@ When a developer starts a cloud session, the session-start UI shows an environme
 
 The two Claude Code boxes in the diagram are session processes: one runner executing two sessions at once, up to its configured capacity. A runner serves one [owner](#key-concepts) at a time and locks to that owner when it claims its first session, so checked-out code never mixes between owners; [Runner lifecycle](#runner-lifecycle) covers the rule.
 
-You can start runners yourself and keep them running, or run the [autoscaling orchestrator](https://code.claude.com/docs/en/self-hosted-environments-configuration.md#on-demand-runners), a second process you host, which starts runners as sessions queue; each runner exits on its own when its work finishes. Either way, you set the environment up once, and it appears in the picker on every supported surface.
+You can start runners yourself and keep them running, or run the [autoscaling orchestrator](https://code.claude.com/docs/en/self-hosted-environments-configuration.md#on-demand-runners), a second process you host, which starts runners as sessions queue. Either way, you set the environment up once, and it appears in the picker on every supported surface.
 
 ## Availability and limitations
 
@@ -122,7 +122,8 @@ By default, model inference uses the Anthropic API. The control plane delivers t
 
 Corporate egress proxies are supported. The runner and the optional [autoscaling orchestrator](https://code.claude.com/docs/en/self-hosted-environments-configuration.md#on-demand-runners) honor the proxy and mTLS environment variables described in [Network configuration](https://code.claude.com/docs/en/network-config.md), such as `HTTPS_PROXY` and `NO_PROXY`; set them in each process's environment. The variables cover control-plane calls, the orchestrator's [SCM connector](https://code.claude.com/docs/en/self-hosted-environments-reference.md#scm-connector-flags) WebSocket, and the built-in clone for HTTPS remotes, and sessions inherit them from the runner. Session streaming uses server-sent events over HTTPS, so a proxy in the path must not buffer responses.
 
-If your proxy also requires a `Proxy-Authorization` header, the runner can add it to each connection it opens to the proxy; see [Authenticate to an egress proxy](https://code.claude.com/docs/en/self-hosted-environments-deploy.md#authenticate-to-an-egress-proxy).
+* **Proxy authentication**: if your proxy also requires a `Proxy-Authorization` header, the runner can add it to each connection it opens to the proxy; see [Authenticate to an egress proxy](https://code.claude.com/docs/en/self-hosted-environments-deploy.md#authenticate-to-an-egress-proxy).
+* **Long-lived responses**: if a runner picks up a session but Claude never answers its first message, your proxy may be the cause. See [A session is picked up, but Claude never answers its first message](https://code.claude.com/docs/en/self-hosted-environments-deploy.md#when-a-sessions-first-message-is-never-answered).
 
 ## What stays on your infrastructure
 
diff --git a/content/en/docs/claude-code/settings-reference.md b/content/en/docs/claude-code/settings-reference.md
index e3836aa8b0..e179061c6d 100644
--- a/content/en/docs/claude-code/settings-reference.md
+++ b/content/en/docs/claude-code/settings-reference.md
@@ -324,7 +324,7 @@ This example lets people select only Sonnet and Haiku models:
 }
 ```
 
-A model ID entry such as `"claude-opus-5"` also permits later versions that extend it, such as Opus 5.5. To block one of those versions, use [`deniedModels`](#deniedmodels). To make each model ID entry permit only the version it names, use [`availableModelsMatch`](#availablemodelsmatch). See [Restrict model selection](https://code.claude.com/docs/en/model-config.md#restrict-model-selection).
+A model ID entry such as `"claude-opus-5"` also permits later versions that extend it, such as Opus 5.5. To block one of those versions, use [`deniedModels`](#deniedmodels). To make each model ID entry permit only the version it names, use [`availableModelsMatch`](#availablemodelsmatch). See [Restrict model selection](https://code.claude.com/docs/en/model-config.md#restrict-model-selection). For third-party provider IDs, see [Pin models for third-party deployments](https://code.claude.com/docs/en/model-config.md#pin-models-for-third-party-deployments).
 
 ### `availableModelsMatch`
 
@@ -333,7 +333,7 @@ Choose how [`availableModels`](#availablemodels) entries match model IDs. By def
 * **Scope**: [`Managed`](#scopes). Claude Code ignores the key in user, project, and local settings and in `--settings`, with a warning
 * **Type**: string, one of:
   * `"prefix"`: a model ID entry permits its version and any model ID that extends it with another segment
-  * `"exact"`: a model ID entry permits only the version it names, including that version's dated IDs, so `"claude-opus-5"` permits Opus 5 but not `claude-opus-5-5`. A family alias such as `"opus"` still permits the whole family, and `best`, `opusplan`, and `default` entries are ignored
+  * `"exact"`: a model ID entry permits only the version it names, so `"claude-opus-5"` permits Opus 5 but not `claude-opus-5-5`. An entry such as `"claude-opus-4-5"` also permits its dated Anthropic model ID `claude-opus-4-5-20251101`. A family alias such as `"opus"` still permits the whole family, and `best`, `opusplan`, and `default` entries are ignored
 * **Default**: `"prefix"`
 
 This example permits Opus 5 and Sonnet 5 and no later release of either:
@@ -1371,12 +1371,40 @@ The `//path` prefix for absolute paths also works. If you use single-slash `/pat
 
 Claude Code strips a trailing slash from a directory path, so `~/.aws` and `~/.aws/` match the same directory. Before v2.1.224, Claude Code passed the trailing slash through to the sandbox, and Claude could still read or write paths under a `denyRead` or `denyWrite` entry written with one.
 
-Claude Code also removes a trailing `/**`, so `~/build/**` and `~/build` cover the same directory. Whether a wildcard such as `*` works depends on which list the entry is in and on the platform:
+##### Where wildcards work in sandbox paths
 
-* **`allowWrite` and `denyWrite`**: on macOS, wildcards work. On Linux and WSL2, the sandbox mounts concrete paths, so Claude Code skips an entry that contains `*`, `?`, or `[` once the trailing `/**` is removed, and that entry has no effect. Claude Code adds the paths from your `Edit` permission rules to these lists, so the same limit applies to them, and the **Config** tab of `/sandbox` warns about `Edit` and `Read` permission rules that contain wildcards.
-* **`denyRead` and `allowRead`**: wildcards work on every platform. On Linux and WSL2, Claude Code expands a read entry to the concrete paths it matches, which it doesn't do for the write lists.
+The wildcards `*`, `?`, and `**` work in all four `sandbox.filesystem` path lists on macOS and in fewer places on Linux and WSL2:
 
-Braces match as ordinary characters in a name, so `~/data/{keys,tokens}` covers a directory literally named `{keys,tokens}`, not two alternatives. To cover `~/data/keys` and `~/data/tokens`, add each as its own entry.
+| `sandbox.filesystem` list | What works on Linux and WSL2 | Example that doesn't work on Linux and WSL2 | What to write instead |
+| :- | :- | :- | :- |
+| `denyRead`, `allowRead` | A trailing `/**` works, so `~/build/**` covers the same directory as `~/build`. Any other wildcard works only after the first directory name of the entry's [full path](#sandbox-path-prefixes). | `/**/*.pem` in `denyRead` covers nothing, so it blocks no reads | `/srv/**/*.pem`, with one entry for each top-level directory |
+| `allowWrite`, `denyWrite` | Only a trailing `/**` works, so `~/build/**` covers the same directory as `~/build` | `./src/*` covers only a file or directory in `src` that is itself named `*`, and nothing when there is none | `./src`, which covers everything under `src`, or one entry for each path |
+
+In `~/keys/*.pem`, the wildcard comes after the first directory name, which is `home` for a home directory of `/home/alice`:
+
+```text theme={null}
+~/keys/*.pem              the entry
+/home/alice/keys/*.pem    its full path
+ ^^^^                     the first directory name, home
+```
+
+On Linux and WSL2, the **Config** tab of `/sandbox` in a session warns about `Edit` permission rules that contain a wildcard other than a trailing `/**`. Those wildcards don't work for sandboxed commands. Add each path the rule should cover, or the directory that holds them, to `allowWrite` for an allow rule or `denyWrite` for a deny rule.
+
+##### Directory names with brackets, braces, or parentheses
+
+To allow or block a directory whose name contains brackets, write the name as it is, such as `./app/[slug]`. In that entry, `[slug]` is the directory's real name, brackets included:
+
+```text theme={null}
+app/
+└── [slug]/
+    └── page.tsx
+```
+
+That entry covers everything under the directory, so leave off a trailing `/**`. On macOS and on Linux and WSL2, the `app/[slug]` directory has to exist when the sandboxed command starts.
+
+* **Brackets such as `[slug]`**: in every list on macOS, and in `denyRead` and `allowRead` on Linux and WSL2, the brackets in `./app/[slug]` are also a pattern. The entry then also matches any path under `app` named with one character from `slug`, such as `app/s` or `app/g`. With that entry in `allowRead`, or in `allowWrite` on macOS, sandboxed commands can reach those paths as well. Rename any they shouldn't reach.
+* **Brackets such as `[user-id]` or `[post-id]`, where the hyphen's left character sorts after its right**: `./app/[user-id]` covers only the directory with exactly that name, in every list on every platform. Before v2.1.304, sandboxed commands on Linux and WSL2 failed to start while `denyRead` or `allowRead` held such an entry.
+* **Braces and parentheses**: these are ordinary characters, so `~/data/{keys,tokens}` covers one directory named `{keys,tokens}`, not two alternatives. To cover `~/data/keys` and `~/data/tokens`, add each as its own entry.
 
 ### `sandbox.filesystem.allowWrite`
 
@@ -3470,7 +3498,7 @@ This example allows any URL under `https://hooks.example.com/` and any `http://l
 
 Hostname matching is case-insensitive and treats `hooks.example.com.`, with the trailing dot that marks a fully qualified domain name, the same as `hooks.example.com`, which is how DNS treats them. The allowlist applies to hooks from every source, including managed settings.
 
-In the Agent SDK's `managedSettings` option, Claude Code ignores this key when its list has entries, so pass the list in the SDK's `settings` option instead. See [what each value does in parent settings](https://code.claude.com/docs/en/claude-apps-gateway#how-hook-and-skill-keys-in-parent-settings-take-effect).
+In the Agent SDK's `managedSettings` option, Claude Code ignores a list with entries, so pass it in the SDK's [`settings` option](https://code.claude.com/docs/en/agent-sdk/typescript#options) instead. See [what an empty list does in parent settings](https://code.claude.com/docs/en/claude-apps-gateway#how-hook-and-skill-keys-in-parent-settings-take-effect).
 
 ### `allowManagedHooksOnly`
 
@@ -3520,7 +3548,7 @@ Turn off [hooks](https://code.claude.com/docs/en/hooks.md#disable-or-remove-hook
 The reach depends on which file carries the key:
 
 * **In managed settings**: Claude Code disables every configured hook, including managed ones, and keeps running the hooks the [Agent SDK](https://code.claude.com/docs/en/agent-sdk/overview.md) registers in process
-* **In the Agent SDK's `managedSettings` option**: Claude Code treats the key as `allowManagedHooksOnly: true`, so see [what runs under `allowManagedHooksOnly`](#what-runs-under-allowmanagedhooksonly) for which hooks stop. On a machine where an administrator deploys managed settings, Claude Code ignores this key unless the administrator [lets an embedding host add policy](https://code.claude.com/docs/en/managed-settings.md#let-an-embedding-host-add-policy). Requires Claude Code v2.1.309 or later.
+* **In the Agent SDK's `managedSettings` option**: on a machine where an administrator deploys managed settings, Claude Code ignores this key unless the administrator [lets an embedding host add policy](https://code.claude.com/docs/en/managed-settings.md#let-an-embedding-host-add-policy). Where the key takes effect, user, project, local, and plugin hooks stop, as do any in the SDK's `settings` option. An administrator's managed hooks, [force-enabled](#enabledplugins) plugins' hooks, and your [SDK hook callbacks](https://code.claude.com/docs/en/agent-sdk/hooks.md) keep running. Requires Claude Code v2.1.309 or later.
 * **In any other settings file**: Claude Code disables user, project, local, and plugin hooks; managed hooks, Agent SDK hooks, and hooks from plugins force-enabled in managed [`enabledPlugins`](#enabledplugins) keep running
 
 The key also stops [mods](https://code.claude.com/docs/en/plugins/mods/overview.md), which are plugins whose code registers hooks:
@@ -3624,7 +3652,7 @@ This example limits header interpolation to `MY_TOKEN` and `HOOK_SECRET`:
 
 The allowlist applies to hooks from every source, including managed settings.
 
-In the Agent SDK's `managedSettings` option, Claude Code ignores this key when its list has entries, so pass the list in the SDK's `settings` option instead. See [what each value does in parent settings](https://code.claude.com/docs/en/claude-apps-gateway#how-hook-and-skill-keys-in-parent-settings-take-effect).
+In the Agent SDK's `managedSettings` option, Claude Code ignores a list with entries, so pass it in the SDK's [`settings` option](https://code.claude.com/docs/en/agent-sdk/typescript#options) instead. See [what an empty list does in parent settings](https://code.claude.com/docs/en/claude-apps-gateway#how-hook-and-skill-keys-in-parent-settings-take-effect).
 
 ### `workflowKeywordTriggerEnabled`
 
@@ -3841,7 +3869,7 @@ Block the [`command` plugin source](https://code.claude.com/docs/en/plugins/mark
 * **Type**: Boolean
   * `true`: Claude Code never runs the marketplace-declared command, doesn't install or update command-sourced plugins, and stops loading the ones already installed
   * `false`: Claude Code allows command-sourced plugins explicitly
-* **Default**: unset, so Claude Code follows [`allowManagedHooksOnly`](#allowmanagedhooksonly): an organization that restricts hook execution to managed settings gets command sources disabled too
+* **Default**: unset, so Claude Code follows [`allowManagedHooksOnly`](#allowmanagedhooksonly): an organization that restricts hook execution to managed settings gets command sources disabled too. An application that passes [`disableAllHooks: true`](#disableallhooks) in the Agent SDK's `managedSettings` option doesn't by itself disable command sources.
 
 ```json managed-settings.json theme={null}
 {
diff --git a/content/en/docs/claude-code/terminal-config.md b/content/en/docs/claude-code/terminal-config.md
index 49f8fae91c..57e9dda6da 100644
--- a/content/en/docs/claude-code/terminal-config.md
+++ b/content/en/docs/claude-code/terminal-config.md
@@ -127,12 +127,15 @@ When Claude Code runs inside tmux, by default Shift+Enter submits instead of ins
 
 ```bash ~/.tmux.conf theme={null}
 set -g allow-passthrough on
+set -g focus-events on
 set -s extended-keys on
 set -as terminal-features 'xterm*:extkeys'
 ```
 
 The `allow-passthrough` line lets notifications and progress updates reach the outer terminal instead of being swallowed by tmux. The `extended-keys` lines let tmux distinguish Shift+Enter from plain Enter so the newline shortcut works.
 
+A [mod's `Image`](https://code.claude.com/docs/en/plugins/mods/reference#elements) needs the `allow-passthrough` and `focus-events` lines, along with the other [requirements for drawing inside tmux](https://code.claude.com/docs/en/plugins/mods/gallery.md#draw-an-image-inside-tmux). After you add the lines, also detach from tmux, attach again, and restart Claude Code.
+
 ## Fix Backspace deleting a whole word on Windows
 
 On Windows, Claude Code reads a Backspace that arrives as `^H` as Ctrl+Backspace, which [deletes the previous word](https://code.claude.com/docs/en/interactive-mode.md#text-editing), except when `TERM_PROGRAM` is `mintty` or `TERM` is `cygwin`. On macOS and Linux, Claude Code reads it as plain Backspace.
diff --git a/content/en/docs/claude-code/ultrareview.md b/content/en/docs/claude-code/ultrareview.md
index 86bb02e3f5..67e48ea3f2 100644
--- a/content/en/docs/claude-code/ultrareview.md
+++ b/content/en/docs/claude-code/ultrareview.md
@@ -176,7 +176,7 @@ Running `claude ultrareview` requires the same authentication and usage-credits
 The subcommand exits with one of three codes:
 
 * **0**: the review completed, with or without findings
-* **1**: the review failed to launch or was stopped before it finished, the cloud session errored, or the timeout elapsed. The code is also 1 when the [folder isn't trusted](#trust-the-folder-before-the-review-runs), including when you answer `n` or press Ctrl-C at the trust question.
+* **1**: the review failed to launch or was stopped before it finished, the cloud session errored, or the timeout elapsed. The code is also 1 when the [folder isn't trusted](#trust-the-folder-before-the-review-runs), including when you answer `n`, press Enter, or press Ctrl-C at the trust question.
 * **130**: you pressed Ctrl-C while the subcommand was launching the review, waiting for the findings, or sending the `--post` comment, rather than at the trust question
 
 If the subcommand exits before the findings arrive, they never reach your terminal. The review may still be running in the cloud. Running the subcommand again starts a new review rather than resuming that one, and the new review [uses a free run or bills as usage credits](#pricing-and-free-runs).
@@ -198,7 +198,7 @@ When it can't ask you, such as in a CI job or with output sent to a file, it exi
 claude ultrareview 1234 --trust-workspace
 ```
 
-To review an untrusted pull request, run `claude ultrareview <PR number> --trust-workspace` from a branch you trust. Unlike `y`, the flag saves nothing. The PR is [cloned in the cloud](#review-a-pull-request), so you don't need its branch locally.
+To review an untrusted pull request, run `claude ultrareview <PR number> --trust-workspace` from a branch you trust. The PR is [cloned in the cloud](#review-a-pull-request), so you don't need its branch locally.
 
 ## How ultrareview compares to /code-review
 
diff --git a/content/en/docs/claude-code/web-scheduled-tasks.md b/content/en/docs/claude-code/web-scheduled-tasks.md
index 932a6238da..b443db5e91 100644
--- a/content/en/docs/claude-code/web-scheduled-tasks.md
+++ b/content/en/docs/claude-code/web-scheduled-tasks.md
@@ -25,7 +25,7 @@ A scheduled task doesn't need a schedule:
 * A task with only an API trigger runs when you call its endpoint.
 * A task with only a GitHub trigger runs when a matching repository event occurs.
 
-Scheduled tasks are available on Pro, Max, Team, and Enterprise plans. Create and manage them at [claude.ai/code/routines](https://claude.ai/code/routines), or from the CLI with `/schedule`. The earlier name, routines, [still appears](#where-the-name-routines-still-appears) in the web address, the CLI, and the API.
+Scheduled tasks are available on Pro, Max, Team, and Enterprise plans. Create and manage them at [claude.ai/code/routines](https://claude.ai/code/routines), or from the CLI with `/schedule`. The earlier name, routines, [still appears](#where-the-name-routines-still-appears).
 
 > [!NOTE]
 >
@@ -66,7 +66,12 @@ Scheduled tasks belong to your individual claude.ai account. They are not shared
 
 **1. Open the creation dialog**
 
-Go to [claude.ai/code/routines](https://claude.ai/code/routines) and click **New task**. If a menu opens first, select **Set up manually**. The **New scheduled task** dialog opens. The menu's other option, **Create with Claude**, lets you describe the task in a chat and have Claude create it instead.
+Go to [claude.ai/code/routines](https://claude.ai/code/routines) and click **New task** to open the **New scheduled task** dialog. Check for these screens before you continue:
+
+* If the button reads **New routine** instead of **New task**, click **New routine** and continue with [Full-page form](#full-page-form).
+* In the Desktop app, if a menu with **Local** and **Cloud** opens, go to [Full-page form](#full-page-form).
+* If a menu opens with **Create with Claude** and **Set up manually**, select **Set up manually** to open the dialog. **Create with Claude** lets you describe the task in a chat and have Claude create it instead.
+* If a full page opens in place of the dialog, go to [Full-page form](#full-page-form).
 
 If **Repositories** and **Environment** are already showing when the dialog opens, see [how that dialog differs](#dialog-with-repositories-and-environment-in-the-main-view). Otherwise, this dialog also creates scheduled tasks for claude.ai chat. To make yours what the dialog calls a Claude Code task, select a repository or add a GitHub event or API trigger in the steps that follow. That kind of task runs Claude Code in a cloud session.
 
@@ -126,6 +131,17 @@ Follow the [steps to create from the web](#create-from-the-web), and fill in eac
 
 Select the repository before you add a GitHub event trigger, because that trigger is unavailable until a repository is selected.
 
+#### Full-page form
+
+In the Desktop app, if a menu with **Local** and **Cloud** opens, select **Cloud**. A page titled **New routine** or **New scheduled task** opens. Fill in its fields:
+
+* **Name**: enter one.
+* **Instructions**: enter the prompt. In the same box, select the model, the repositories, and the environment. For what each one controls, see the steps under [Create from the web](#create-from-the-web).
+* **Select a trigger**: select **Schedule**, **GitHub event**, or **API**. For a schedule, see [Add a schedule trigger](#add-a-schedule-trigger). For a [GitHub event](#add-a-github-trigger), select a repository. For an [API trigger](#add-an-api-trigger), copy the token from the **API token** dialog that opens after you click **Create**, because it is shown once. To combine several triggers, click **Add another trigger**.
+* **Connectors**: all of your connected connectors are included by default, so remove the ones the task doesn't need.
+
+If **Create** is unavailable, hover over it to see what the form still needs. Click **Create**, and the task's detail page opens.
+
 ### Create from the CLI
 
 Run `/schedule` in any session to create a scheduled task conversationally. You can also pass a description directly, for a recurring task like `/schedule daily PR review at 9am` or a one-off like `/schedule clean up feature flag in one week`. Claude walks through the same information the web dialog collects, then saves the task to your account. The command is also available under the alias `/routines`.
@@ -152,6 +168,7 @@ A schedule trigger runs the task on a recurring cadence, or once at a specific f
 * **Runs on the hour**: if you schedule a run exactly on the hour, such as 9:00, it can start several minutes late. To start close to the scheduled time, pick a few minutes past the hour, for example 9:07.
 * **Custom intervals**: for a cadence the presets lack, create the task and select **Custom** in its [edit dialog](#edit-and-control-scheduled-tasks). Then enter a cron expression, such as `0 */2 * * *` for every two hours. To set one from the CLI, run [`/schedule update`](#manage-scheduled-tasks-from-the-cli). Expressions that run more often than once per hour are rejected.
 * **Time zone**: when you pick a preset frequency, enter the time in your local time zone.
+* **Cron expression time zone**: when the expression is five fields alone, write the hours in UTC, so `0 9 * * 1-5` runs at 9:00 AM UTC on weekdays. If the field opens with a `CRON_TZ=` prefix, keep it and write the hours in its zone, or delete it and write them in UTC.
 
 #### Schedule a one-off run
 
@@ -455,6 +472,7 @@ While your subscription is paused, your scheduled tasks are put on hold and don'
 
 Scheduled tasks were previously called routines, and these places keep the earlier name. Each one refers to the same feature:
 
+* **App**: in some accounts the sidebar entry and page title read **Routines**, the button reads **New routine**, and other labels say routine. To create a task there, see [Full-page form](#full-page-form).
 * **Web address**: `claude.ai/code/routines`
 * **CLI**: the `/routines` alias for `/schedule`, the command's description, and Claude's replies while it sets up a task
 * **API**: the `/fire` endpoint path, its beta header, its response `type`, the `<routine-fire-payload>` tag, and the [Trigger a routine through the API](https://platform.claude.com/docs/en/api/claude-code/routines-fire) reference page
diff --git a/content/support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md b/content/support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md
index 99c66caee8..4e536e1fe2 100644
--- a/content/support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md
+++ b/content/support/10504844-manage-user-feedback-settings-on-team-and-enterprise-plans.md
@@ -6,6 +6,6 @@ As a Primary Owner or Owner of a Team or Enterprise plan, you can manage the abi
 
 2. Use the toggle to change the **Rate chats** setting for your organization:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2058292603/75752add0bed6a9f3ab217f01708/CleanShot%2B2026-02-12%2Bat%2B08_55_14-402x.png?expires=1792852200&amp;signature=06822855b99af35b9b4a42e7eef7d7c91ba16d6a94566a5c2791822fdc2fbd2f&amp;req=diAiHst3n4dfWvMW1HO4zYGm8yUUFarO085gFtEpvcSBpypOuhkT51q9It9T%0AHU%2BEkOHFKBH7Pzbb5k4%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2058292603/75752add0bed6a9f3ab217f01708/CleanShot%2B2026-02-12%2Bat%2B08_55_14-402x.png?expires=1792868400&amp;signature=51199e67b454a7772a3ebd2839bd394def448a9e9e0e6203b88ed3a204f015c5&amp;req=diAiHst3n4dfWvMW1HO4zYGm8yUUFqDI085gFtEpvcRIwYAfHbKLCz91bO5A%0AkrMWEFEExRN%2Fbok1bnk%3D%0A)
 
 More information on how Anthropic collects, uses, and stores feedback data can be found in our Privacy Center: **[How long do you store my organization’s data?](https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data)**
\ No newline at end of file
diff --git a/content/support/10593882-share-and-unshare-chats.md b/content/support/10593882-share-and-unshare-chats.md
index 76cddda6ce..3e6c94808b 100644
--- a/content/support/10593882-share-and-unshare-chats.md
+++ b/content/support/10593882-share-and-unshare-chats.md
@@ -38,12 +38,12 @@ To unshare a chat:
 
 Users on free, Pro, or Max plans can review a log of shared chats by navigating to **[Settings > Privacy](https://claude.ai/settings/data-privacy-controls)**. Find the **Privacy settings** section and click “Manage” next to **Shared chats:**
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1921669913/7cc7be48cfc7a18f9f469d6cd83c/CleanShot+2026-01-08+at+10_20_43%402x.png?expires=1792852200&amp;signature=918729c4356ee36b8e577b5c750daea79714247011c60cce87521f91693a826a&amp;req=dSklF894lIheWvMW1HO4zWn5HjEVZ0dpc9cNIYuX0GFl1qFrj5yn5%2Bcojt6H%0AIcqersEKG0sAsOCcY%2Bg%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1921669913/7cc7be48cfc7a18f9f469d6cd83c/CleanShot+2026-01-08+at+10_20_43%402x.png?expires=1792868400&amp;signature=29fd787d3a9950d5d9a315d35e11dc9200b247f05f7c9f36361d185f2e81530e&amp;req=dSklF894lIheWvMW1HO4zWn5HjEVZE1vc9cNIYuX0GFyrXJoOHbUuRJDS47Q%0A9awyzGZqYmGpoypjgUk%3D%0A)
 
 This will open a **Shared chats** modal listing the title, date shared, and link to each chat, allowing you to easily review and access all your previously-shared content. From here, you also have the option to click “Unshare” next to each listed chat to revoke access to the last snapshot you shared:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1624243810/e6fe1d262597446c7fe21dff9f10/AD_4nXdW-GhByF8uKV7fCq9lTbkVB91FglSL6TSyXAOUk_MLcTV9YsEMBMkm9rgm1oXqv0k3sJh1JhlzZP6tHVkKbDJJ71pDRRtM3aVNG64MDuKDIzgmknh-XDZdNa7biTsTdwGoPr5GRg?expires=1792852200&amp;signature=06a2fc6f200f128b07cda86d66fab0a4205d02f9afadf3f8c63c14e4604c50a1&amp;req=dSYlEst6noleWfMW1HO4ze44eSVpkRA8guvTv9woD7Za1CvCkJaIgnhXEbrZ%0ACtwdH32RjvgUrAnBfKo%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1624243810/e6fe1d262597446c7fe21dff9f10/AD_4nXdW-GhByF8uKV7fCq9lTbkVB91FglSL6TSyXAOUk_MLcTV9YsEMBMkm9rgm1oXqv0k3sJh1JhlzZP6tHVkKbDJJ71pDRRtM3aVNG64MDuKDIzgmknh-XDZdNa7biTsTdwGoPr5GRg?expires=1792868400&amp;signature=a2eebe4a42ea032649965db74e20183a74c48b48377c0c54ffd4aa2c9a1c0473&amp;req=dSYlEst6noleWfMW1HO4ze44eSVpkho6guvTv9woD7ZPJ4H0fViF6iQnpe4P%0Afq0KtfkRAuv2TwAdSSg%3D%0A)
 
 If you don’t have any shared chat snapshots, the **Shared chats** modal will show “No shared content found”:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1624243808/b025db8e598f0c88fb16d83d48d5/AD_4nXeUwCKnmFzzrjMHhfr5By4zk5pJlkEn3wbJ8-aNfu13Yl99IjBywpqPx9G07QRzpH1EwRY7uG7Q9m9fib98Gql1cIV7XwUCTzEgBNu79Ey8tCOS5CEVmwveIcEOxJ4fonBhe3g9MA?expires=1792852200&amp;signature=04722bb396db64604b30e59cddfd3c37cfa7d8887d0e423d9b678ec9b9e27548&amp;req=dSYlEst6nolfUfMW1HO4zdaFnMd8hIuzDeZsm0Gz1Ht%2FzSpMjTFkeboP7fK5%0AbShmmuayBAxgVAeFi%2FE%3D%0A)
\ No newline at end of file
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1624243808/b025db8e598f0c88fb16d83d48d5/AD_4nXeUwCKnmFzzrjMHhfr5By4zk5pJlkEn3wbJ8-aNfu13Yl99IjBywpqPx9G07QRzpH1EwRY7uG7Q9m9fib98Gql1cIV7XwUCTzEgBNu79Ey8tCOS5CEVmwveIcEOxJ4fonBhe3g9MA?expires=1792868400&amp;signature=7152b25033956b434afb825ec875d081ca1f505e9cea9ae48b351adf4165cf2d&amp;req=dSYlEst6nolfUfMW1HO4zdaFnMd8h4G1DeZsm0Gz1HvGzl00lD4a7vbBycfo%0Atf0vnmNwBwpnJ8x26jk%3D%0A)
\ No newline at end of file
diff --git a/content/support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md b/content/support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md
index 0d74934ff8..7ca8a66ca1 100644
--- a/content/support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md
+++ b/content/support/11725453-set-up-the-claude-lti-in-canvas-by-instructure.md
@@ -44,7 +44,7 @@ This article provides information on how to enable the Claude LTI integration in
 
 5. Click "Install" and refresh the course page.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1611422430/c8e0875feac1f2c7cb033be74fc9/AD_4nXfLU_bui3EXcCjQ0qm70HD97neqjGayKeDer_t76utlci8gZSUjYRhw6ZSOlDdqSEcwXBzd_shAh7pQEJ-8OoE0O21DM5coOgxmO_WD5hlwiuwtS2iYXcTavhIRyQT5zKFWvfn3NA?expires=1792852200&amp;signature=e778c2a01234bd24607035cfb5efc3c3dc26c59f946fc7e5c62223cebe62180d&amp;req=dSYmF818n4VcWfMW1HO4zTEDa%2BkWnvGDEv2ojHLMylaVoBLgSSnPagMQCskQ%0ACqd9dzOTHFkIQHNXCBo%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1611422430/c8e0875feac1f2c7cb033be74fc9/AD_4nXfLU_bui3EXcCjQ0qm70HD97neqjGayKeDer_t76utlci8gZSUjYRhw6ZSOlDdqSEcwXBzd_shAh7pQEJ-8OoE0O21DM5coOgxmO_WD5hlwiuwtS2iYXcTavhIRyQT5zKFWvfn3NA?expires=1792868400&amp;signature=d3e6c1ede0e7e8096a523aaf70a667e22589115cbea90691a65dc992915cd741&amp;req=dSYmF818n4VcWfMW1HO4zTEDa%2BkWnfuFEv2ojHLMylZP7tZ%2B%2BVk2r3I0Gnf0%0A%2FBImQwuqhb8Ye0XC39k%3D%0A)
 
 ## Turn on the Claude LTI Integration in Claude for Education organization settings
 
diff --git a/content/support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md b/content/support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md
index 5c1572bb5d..11dd498a1f 100644
--- a/content/support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md
+++ b/content/support/11818288-why-am-i-being-asked-to-verify-my-payment-method.md
@@ -2,7 +2,7 @@
 
 If you see the following pop-up when you log in to your Claude account, you’ll need to click the “Verify now” button to verify your payment method:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1631413861/42c3b13d7fc44a11a88ec2b9cd03/AD_4nXeMx8QXpeZZCkfAnVSwx8KZ9n4Vr2rvPdQddyE6ZNxch__F6ZqFs1G4ZmU52Wvb7gRlwRqquTLdw8IQv-gICDyP-MXqiQK_Oe7gX3SKsCKKt2IEpMx4qDeMeeZufMaJfv16XgOH5g?expires=1792852200&amp;signature=f63d559f089fea065c949a5e8ddedcad01f44101aae0d34462df5f3d8d45dcee&amp;req=dSYkF81%2FnolZWPMW1HO4zf7%2BjUbm7YLwn6MrEicvimAD28W2jFU5V5AJY396%0AmWcmw37fY0lS5ynOBCs%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1631413861/42c3b13d7fc44a11a88ec2b9cd03/AD_4nXeMx8QXpeZZCkfAnVSwx8KZ9n4Vr2rvPdQddyE6ZNxch__F6ZqFs1G4ZmU52Wvb7gRlwRqquTLdw8IQv-gICDyP-MXqiQK_Oe7gX3SKsCKKt2IEpMx4qDeMeeZufMaJfv16XgOH5g?expires=1792868400&amp;signature=12b4048741d9d6126dbd4ce9fc3e728a30fd84ef822b0e9dfdda18161d0a8eb1&amp;req=dSYkF81%2FnolZWPMW1HO4zf7%2BjUbm7oj2n6MrEicvimCnPSaM1Ip8zYSvvM9p%0AbALA%2BiL6pBRBvu1ndEE%3D%0A)
 
 ## What happens if I click “Remind me later?”
 
diff --git a/content/support/11869629-use-claude-with-android-apps.md b/content/support/11869629-use-claude-with-android-apps.md
index bc43ed9308..2c2d874615 100644
--- a/content/support/11869629-use-claude-with-android-apps.md
+++ b/content/support/11869629-use-claude-with-android-apps.md
@@ -222,7 +222,7 @@ Permission requirements vary by feature:
 
 For features requiring permissions (like location or calendar access), Claude will request permission contextually with clear explanations of why the access is needed. You’ll be prompted to approve the action with three options: Allow once, Always allow, or Don't allow.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1707351614/ccb910e4b87b1e96ad9a11bbd835/b57b2130-d8d6-4499-89f6-6c12de236fd4?expires=1792852200&amp;signature=74cf0a548f1aa6c463c1a4932f9778786c0439d4facbafd154183a3b12eb2397&amp;req=dScnEcp7nIdeXfMW1HO4zQe5G12H3if2S5x65TIld%2FD1Ptcl2b8E%2FR%2FRK8wx%0A7VeaPwpbh%2FJQ3GNyMbw%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1707351614/ccb910e4b87b1e96ad9a11bbd835/b57b2130-d8d6-4499-89f6-6c12de236fd4?expires=1792868400&amp;signature=4467f76d20b0cc9a640678ab2ab7445d9421cd4b391c3696ad9e88c5d1b33568&amp;req=dScnEcp7nIdeXfMW1HO4zQe5G12H3S3wS5x65TIld%2FDk4WdVFKEWZtpdDqHQ%0AOFL9OcfiORUkUTZuYio%3D%0A)
 
 These permissions can be managed at any time in your device settings by going to Settings > Apps > Claude > Permissions. Click into each permission listed under **Allowed** and **Not allowed** to make changes. You can toggle between “Allow only while using the app” or “Ask every time” to change Claude’s access, or remove permissions by choosing “Don’t allow.” Claude will only request permissions if needed for specific features, and you can always choose to decline while still using other capabilities.
 
diff --git a/content/support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md b/content/support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md
index adc2550522..373440c3a3 100644
--- a/content/support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md
+++ b/content/support/12005970-manage-usage-credits-for-team-and-seat-based-enterprise-plans.md
@@ -70,7 +70,7 @@ After navigating to **[Organization settings > Usage](https://claude.ai/admin-se
 
 The **Usage and spend limits** section will show the current limit (if any) or **Unlimited**. Clicking on "Adjust limit" opens a modal where you can either input an amount and click "Set spend limit," or click "Set to unlimited" to remove the organization-wide monthly spend limit.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149347604/936ac4eb025d3ef1f00c3b8a26b0/image.png?expires=1792852200&amp;signature=7b5516dfc8251607ff483f6ee6d3b889c8d039d3f4020fe9dbf415ce1935aa7e&amp;req=diEjH8p6modfXfMW1HO4zQHwgqPfkyyk6DwhVVpk1mDOJstlm8wQeMDtE%2Fa%2B%0Am7v2jbfaQFskKog4hZA%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149347604/936ac4eb025d3ef1f00c3b8a26b0/image.png?expires=1792868400&amp;signature=3f3a63d4b67b86de0a9ee3ea0b43d878c1e66d6ecc547884e0a0a7171dd69cf9&amp;req=diEjH8p6modfXfMW1HO4zQHwgqPfkCai6DwhVVpk1mA2TjLlZOp27xXUdSdC%0Am6Km8CddL8hpHHdBOiA%3D%0A)
 
 Changes to your organization’s overall spend limit go into effect immediately.
 
@@ -78,11 +78,11 @@ Changes to your organization’s overall spend limit go into effect immediately.
 
 Owners and Primary Owners on **seat-based Enterprise plans only** can set spend limits that apply to all users within a specific seat tier.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149351600/c5b979c366ac2738f60ea84e85b3/CleanShot+2026-03-10+at+15_37_41%402x.png?expires=1792852200&amp;signature=b065c261bb5baf7dcfa0e05575c3a4a05838b35c02a9036f7acec3454b0eb733&amp;req=diEjH8p7nIdfWfMW1HO4zYnqMYecJnKL0wfO62ivdG%2BmTp5dQlkCPUfgUyBT%0AjcbrabvZ7angvZyrh4g%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149351600/c5b979c366ac2738f60ea84e85b3/CleanShot+2026-03-10+at+15_37_41%402x.png?expires=1792868400&amp;signature=b298e9e7bd99a3470c6d546ae929120d6e78c2d99dae173f986b01b35e2c1adf&amp;req=diEjH8p7nIdfWfMW1HO4zYnqMYecJXiN0wfO62ivdG%2B3YNkRkL4uq4aJYdS8%0A3kzDZAxOPUQpLScikOA%3D%0A)
 
 Select the "By group" tab to see **Standard seats** and **Premium seats** groups. Click the "..." icon next to the current limit, then "Edit limit." This opens a modal where you can either select "Set dollar amount" and input an amount, or click "Unlimited" to remove the limit for that seat type. Click "Set limit" to save your changes.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149362056/44993661ca2db771fe924d0346f6/image.png?expires=1792852200&amp;signature=75356f2d0f47aa326c1d3b354bcd5a15a2440eb9b12b7d1cae56585480ac607a&amp;req=diEjH8p4n4FaX%2FMW1HO4zRzvvYcDdU9Eq7nEDCGq9G77QtRDsePDJ74mHfG3%0ArKFY7HK4%2BfW0C3wpTgA%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149362056/44993661ca2db771fe924d0346f6/image.png?expires=1792868400&amp;signature=41fd180fa5101c534b8eedff01c8c8c26af577e3adfe9e8dc7b061b343b3a277&amp;req=diEjH8p4n4FaX%2FMW1HO4zRzvvYcDdkVCq7nEDCGq9G5R5aVF%2F1qzjUOAMs%2Fh%0A83XASnuA8AdLY%2FtWg2A%3D%0A)
 
 ---
 
@@ -90,11 +90,11 @@ Select the "By group" tab to see **Standard seats** and **Premium seats** groups
 
 Owners and Primary Owners can also set individual monthly spend limits for each member by finding **Spend limits by user** and clicking the "..." button next to the user, then "Edit limit."
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149370853/db66f5cd03683b9cc119d0dcd6b8/image.png?expires=1792852200&amp;signature=4d6f7ef29c8ddd5b01504fea1bd98265e58549e65d31f1892b50003d45993a4e&amp;req=diEjH8p5nYlaWvMW1HO4zaPdGAVfUC1Ee9HwvwG7ubjtJz2NnFcmUr5H3FI9%0Ahvv2WnpcYtp1oUISFgc%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149370853/db66f5cd03683b9cc119d0dcd6b8/image.png?expires=1792868400&amp;signature=c6816e7b1e2e3dabd5dbabc8d469fb2044beb7bc714304c8792a7f2d61d9a627&amp;req=diEjH8p5nYlaWvMW1HO4zaPdGAVfUydCe9HwvwG7ubhHBGR846WLWxXeDSd3%0ADx7i84YxfoM%2BoPVeC7U%3D%0A)
 
 Enter the amount and click "Set limit." Alternatively, selecting "Set to unlimited" will remove that member's monthly spend limit (they will still be subject to any organization or seat-level spend limits).
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149374028/97813fe3b515c2e839d8d92abd79/image.png?expires=1792852200&amp;signature=5622514d2364753380abe1452d21b48d6c38155ff4983a952614ec16b5b231ed&amp;req=diEjH8p5mYFdUfMW1HO4zevsA%2FWCNumIw6z2wGSwkbvPYRt5qbUwPYnKCCPx%0AL0ieR4uv7eIz%2FDgyRd0%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2149374028/97813fe3b515c2e839d8d92abd79/image.png?expires=1792868400&amp;signature=b21ad50d8c3e14d07f84eef8bb1b502bc504b0b5057f919557e5e53c5429516b&amp;req=diEjH8p5mYFdUfMW1HO4zevsA%2FWCNeOOw6z2wGSwkbt0XasihSn4YD1EqQFZ%0Awp2oAgp%2BXD3g%2Bi%2BhqrQ%3D%0A)
 
 This allows owners fine control over usage credits, so you can set limits for different members based on their roles or individual needs. Once a user reaches their defined spend limit, this will automatically pause their usage credits until the end of the month. They will need to wait for their usage limits to reset before using Claude again.
 
diff --git a/content/support/12157520-claude-code-usage-analytics.md b/content/support/12157520-claude-code-usage-analytics.md
index 49e29457f7..e53d189711 100644
--- a/content/support/12157520-claude-code-usage-analytics.md
+++ b/content/support/12157520-claude-code-usage-analytics.md
@@ -46,7 +46,7 @@ The **Usage** tab displays the following metrics for your organization. Data on
 
 - **Top commands**: The Claude Code commands used most often across your organization.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1717579277/46c512f4b3ed05c359cecd78ed5c/e0ce2c19-39e2-411f-9a1f-cb1d46439a42?expires=1792853100&amp;signature=f05ef254c8ff0fa35ef28ef3bb604b15d65d86503c133682eece143284864be2&amp;req=dScmEcx5lINYXvMW1HO4zfiEPqRYinrPCX9h5MbdDjMWFddw5K0HRblPIhJi%0AtWVkyTwOOF8%2FDtrclXk%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1717579277/46c512f4b3ed05c359cecd78ed5c/e0ce2c19-39e2-411f-9a1f-cb1d46439a42?expires=1792868400&amp;signature=c786e00e8e2d33911c3ee26f7cc556992a36593f33eee0e0a3d93bcdb08baa4d&amp;req=dScmEcx5lINYXvMW1HO4zfiEPqRYiXHKCX9h5MbdDjO7uMdNOIOUawN2WbgO%0AzFLeU3wRY8xK%2BCKom8o%3D%0A)
 
 ### User-level metrics
 
diff --git a/content/support/12260368-use-incognito-chats.md b/content/support/12260368-use-incognito-chats.md
index ec1ac64df9..d558056569 100644
--- a/content/support/12260368-use-incognito-chats.md
+++ b/content/support/12260368-use-incognito-chats.md
@@ -34,7 +34,7 @@ These differ from regular chats in several ways:
 
 When starting a new chat with Claude outside of a project, you'll see a ghost icon in the upper right corner of your screen:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1719768744/c7a2fa56cf284e48472f3b9c4dbf/030563f8-9f97-4891-a749-9ae95968a063?expires=1792852200&amp;signature=6f029f113ce07d95564701cf6961848179aeeb4937d80c7f38385399ecbac684&amp;req=dScmH854lYZbXfMW1HO4zeUcugC1a%2BeJDCAt3Cx%2FSO3qKkDPTmJrGIvKi51a%0A94M8ydLxwuTqWXVqWdA%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1719768744/c7a2fa56cf284e48472f3b9c4dbf/030563f8-9f97-4891-a749-9ae95968a063?expires=1792868400&amp;signature=a7d82382cba914cc7ba7dd622cf23862aa383d788de07fb1e7a9f3a05248345c&amp;req=dScmH854lYZbXfMW1HO4zeUcugC1aO2PDCAt3Cx%2FSO3T894gRmrDf39JoYY6%0Ak1Pzktzn%2B0b3BUlww%2F0%3D%0A)
 
 1. Click the ghost icon to enable incognito mode.
 
diff --git a/content/support/12293051-use-claude-in-xcode.md b/content/support/12293051-use-claude-in-xcode.md
index 9f3fd8788b..3a326fa242 100644
--- a/content/support/12293051-use-claude-in-xcode.md
+++ b/content/support/12293051-use-claude-in-xcode.md
@@ -34,7 +34,7 @@ To start using Claude in Xcode:
 
 3. Log in with your Claude account.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1727371585/b18ca03a6357c52d12d10386f28e/dab2dcb2-f670-4173-b77d-38767a34cec1?expires=1792852200&amp;signature=e96cc7812e0b8b649d08250d29f0dbb9ae928142a78de698d8711ebd7337d035&amp;req=dSclEcp5nIRXXPMW1HO4zUAXIs4KV6rWFalhp3bugHIxaoForhE3l5zAYZON%0AABX%2Bg4D0pjmdPxJDl1g%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1727371585/b18ca03a6357c52d12d10386f28e/dab2dcb2-f670-4173-b77d-38767a34cec1?expires=1792868400&amp;signature=e206dc527715b22d12edbf9a7637bafed31f634012670db95964dbb1a7dac3fd&amp;req=dSclEcp5nIRXXPMW1HO4zUAXIs4KVKDQFalhp3bugHJHUGen5xNaMvGaLhZ0%0AwaDeBEQCmcOFIGS8jxA%3D%0A)
 
 ## Usage limits
 
diff --git a/content/support/12429409-manage-usage-credits-for-paid-claude-plans.md b/content/support/12429409-manage-usage-credits-for-paid-claude-plans.md
index 9a973fba02..180aa68cb9 100644
--- a/content/support/12429409-manage-usage-credits-for-paid-claude-plans.md
+++ b/content/support/12429409-manage-usage-credits-for-paid-claude-plans.md
@@ -50,7 +50,7 @@ To enable usage credits on your paid Claude plan:
 
 8. You can also enable auto-reload to automatically make a purchase when your balance falls below a threshold you set:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1805819785/5e203c38e6ba3f76bfd1dab0d5ce/fe062e7c-18cb-48cc-a7e2-754ac6e6c4be?expires=1792852200&amp;signature=ff67b35d7234f0818b8977cc0d28053be9920610b54cec8b1227783cc163b051&amp;req=dSgnE8F%2FlIZXXPMW1HO4zYj2ABCRoPI6opE7m38YdfdLoKeicolrfSAUexMp%0AvT1qN5250qtAOEEwLG8%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1805819785/5e203c38e6ba3f76bfd1dab0d5ce/fe062e7c-18cb-48cc-a7e2-754ac6e6c4be?expires=1792868400&amp;signature=d8148384ae964691dc5e9adb560661d0755b2cb89fb62c57469d7918c09ae639&amp;req=dSgnE8F%2FlIZXXPMW1HO4zYj2ABCRo%2Fg8opE7m38YdfdgcSEyMtKaobkoQxL9%0ACl4bdKceaVn1ipVnJHg%3D%0A)
 
 ---
 
diff --git a/content/support/12466728-troubleshoot-claude-error-messages.md b/content/support/12466728-troubleshoot-claude-error-messages.md
index f629e357cc..6e31844606 100644
--- a/content/support/12466728-troubleshoot-claude-error-messages.md
+++ b/content/support/12466728-troubleshoot-claude-error-messages.md
@@ -60,4 +60,4 @@ Capacity issues will not appear on our status page because they represent normal
 
 Service incidents are disruptions where Claude is unavailable or significantly degraded for all or most users. These represent actual technical problems with our systems. To check for confirmed incidents, visit status.claude.com, where you'll find real-time updates on scope, impact, and resolution progress for any active incidents.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1753796247/e6a8c6ef8653b229c5758e881242/c2fc6fc0-d163-4119-93e0-394104d86bc9?expires=1792852200&amp;signature=352653fc3cd50f84c42be5e6c63a0a3882575992a7f9b13b2269b0ba708ba46c&amp;req=dSciFc53m4NbXvMW1HO4za4BX60r17DG7y68oYp%2BYg8D6U6D%2F7HUDnsAcADZ%0AohKucj0az8X44XtTMnc%3D%0A)
\ No newline at end of file
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1753796247/e6a8c6ef8653b229c5758e881242/c2fc6fc0-d163-4119-93e0-394104d86bc9?expires=1792868400&amp;signature=79a19aee638ea7297ae5ffed81cc200851ded55e4d56f1c3d656d5aaceedaf35&amp;req=dSciFc53m4NbXvMW1HO4za4BX60r1LrA7y68oYp%2BYg98TsxvzdmQyi2e6i0r%0A9uU5EGMX9%2Fb4MUSF4Cs%3D%0A)
\ No newline at end of file
diff --git a/content/support/12592343-enabling-and-using-the-desktop-extension-allowlist.md b/content/support/12592343-enabling-and-using-the-desktop-extension-allowlist.md
index d970a014a6..389f952bfd 100644
--- a/content/support/12592343-enabling-and-using-the-desktop-extension-allowlist.md
+++ b/content/support/12592343-enabling-and-using-the-desktop-extension-allowlist.md
@@ -20,11 +20,11 @@ The desktop extension allowlist is disabled by default, so an organization Owner
 
 4. Switch to the "Desktop" tab:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1781755172/63c92550571842577ad435860ec5/6f5cc4e1-ff7d-48de-863a-c4e6184d4605?expires=1792852200&amp;signature=d385097071529d0516dc4e2c469b27b62ca7b55fed998cc468b6ab701f87d54e&amp;req=dScvF857mIBYW%2FMW1HO4zQ9pXEgC%2BnLZ0ugSQm1MFW8rLWaKG9TsDE9LbxaR%0ANNw4%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1781755172/63c92550571842577ad435860ec5/6f5cc4e1-ff7d-48de-863a-c4e6184d4605?expires=1792868400&amp;signature=fe78dbca52afaee33f63717d74f9929dad388532d10fd8c1a3253dcacf9306c2&amp;req=dScvF857mIBYW%2FMW1HO4zQ9pXEgC%2BXjf0ugSQm1MFW%2BXTaD56EmrxivldXds%0A7Gzp%0A)
 
 5. Toggle **Allowlist** on:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1781755578/a6bafff5f084dc86ae463703fd3d/6cf0ee18-4e71-4129-98e8-cc08174e3c3a?expires=1792852200&amp;signature=c72b126a0ee3678515536876349b532c14f50e22f8adc183a8cfaf3aeaf3b38a&amp;req=dScvF857mIRYUfMW1HO4zaj0BXMjTKUGTAorLxpdoc822UoMSz4yDXPYI1dr%0AVckn%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1781755578/a6bafff5f084dc86ae463703fd3d/6cf0ee18-4e71-4129-98e8-cc08174e3c3a?expires=1792868400&amp;signature=c775e22a816b2048d6c78829cef37e721a28f4a9ed17904b38568ad340d4befe&amp;req=dScvF857mIRYUfMW1HO4zaj0BXMjT68ATAorLxpdoc%2FpBrOouH3kbTIM%2B4g9%0AXp%2Fp%0A)
 
 ## What happens after enabling the allowlist?
 
@@ -42,7 +42,7 @@ Consider completing the allowlist setup during off-hours to minimize disruption
 
 **Important:** The allowlist requires Claude Desktop version 0.13.91 or higher, so users should update the desktop app by clicking “Claude”, then either “Check for updates” or “Restart to update to Claude 0.13.91”:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1781756960/ad18af50c83d35f2673656c23e00/a7ee450f-0c7d-42d6-a75f-fb1bc088cb52?expires=1792852200&amp;signature=5955856cd8e2f2c3063134c67c4094a05c0bcccc55ca304329aeb3bbceadd746&amp;req=dScvF857m4hZWfMW1HO4zYUJqIGiDzDpCEDZ5AdBjIYBL7pE%2BdZ%2B%2BO0%2BVXzA%0AftkDkT39PLgl7peF%2B%2B4%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1781756960/ad18af50c83d35f2673656c23e00/a7ee450f-0c7d-42d6-a75f-fb1bc088cb52?expires=1792868400&amp;signature=6cb1edb4198bf42ef647d81b4fe89656d893e782b6d06b84de120aef01071813&amp;req=dScvF857m4hZWfMW1HO4zYUJqIGiDDrvCEDZ5AdBjIYQs7QOtyOrLEebowEJ%0AhoFfuD4sIMVFkXsMxWk%3D%0A)
 
 ## Managing allowed extensions
 
@@ -60,7 +60,7 @@ After enabling the allowlist, you can choose which extensions to allow:
 
 If you want to remove an extension from the allowlist, click the “...” button and “Remove from allowlist.”
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1781751250/6558c0f59aea7976bd44b0213d76/e750f02b-cd0d-437e-a83f-9ac362cdf456?expires=1792852200&amp;signature=463ffad47440cd7385bb31e09fce6ff67e71d5d99715b237f88be5504c456d2a&amp;req=dScvF857nINaWfMW1HO4zTrxBKoh%2BlWXqXridZhfx1LJsNY5hlDNDDNciMBg%0A9IjCyBSYF%2BqjNnSHlAM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1781751250/6558c0f59aea7976bd44b0213d76/e750f02b-cd0d-437e-a83f-9ac362cdf456?expires=1792868400&amp;signature=6490316419f7dc52eaf72ea2ab7f9427f67c4440ffa558c50296a619ac26b35f&amp;req=dScvF857nINaWfMW1HO4zTrxBKoh%2BV%2BRqXridZhfx1KrEitjX%2BMZiQ20Q5RG%0ABZC38Ywsg%2BOGrbtR5VM%3D%0A)
 
 ## Uploading custom extensions
 
diff --git a/content/support/12618689-use-claude-code-in-the-cloud.md b/content/support/12618689-use-claude-code-in-the-cloud.md
index 9974e1ad32..118ce956a0 100644
--- a/content/support/12618689-use-claude-code-in-the-cloud.md
+++ b/content/support/12618689-use-claude-code-in-the-cloud.md
@@ -10,7 +10,7 @@ This feature works with repositories you may not have on your local machine. You
 
 Cloud sessions enable asynchronous development workflows. In a local session in your terminal or editor, you typically work synchronously: you make a request, wait for Claude to respond, review the changes, then make another request. Synchronous work like this gives you fine-grained control but requires your attention throughout the process. A cloud session handles this differently: you can assign a larger task, let Claude work independently, and return later to review the completed work.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1786446157/07ec74cd46317f8278083a317841/6448f3ee-c6df-4417-8a13-90d8c2ca3d55?expires=1792852200&amp;signature=8c2ae697fa49ab24a997cef1c7266008760a3ae3c8e2c6323c4d34c9b13c85b6&amp;req=dScvEM16m4BaXvMW1HO4zR8%2BAVGIR5907XrRA1YwWGsQZHJ%2BeesE37Rkte5r%0AzyqSjmlmFFcPnW0cS8o%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1786446157/07ec74cd46317f8278083a317841/6448f3ee-c6df-4417-8a13-90d8c2ca3d55?expires=1792868400&amp;signature=66d8f3c386e979ebd22a6c5e0ed6b0cf92e3b0906244a78a7f23bf4320095e7e&amp;req=dScvEM16m4BaXvMW1HO4zR8%2BAVGIRJVy7XrRA1YwWGu3NDi06hnTbMuwpiDO%0A4lmrPtSrrOQ1LUtuK8E%3D%0A)
 
 You can also run multiple tasks in parallel. Since each task runs in its own isolated environment, you can have Claude working on several different issues or repositories simultaneously. Each task proceeds independently and creates its own pull request when complete. More than one task can work on the same repository at the same time.
 
@@ -20,13 +20,13 @@ You can also run multiple tasks in parallel. Since each task runs in its own iso
 
 When you start a cloud session, Claude Code creates an isolated virtual machine for your work. Your GitHub repository is cloned into this environment, which comes pre-configured with common development tools and language ecosystems.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1786446158/c092f1383826cb871493f74169d4/97b7cb98-5da2-438e-a920-e170b8b9790e?expires=1792852200&amp;signature=0fa38c82056eb2bcc7f99074a7d945460ccb5a0818f82fbb222fb4fe1e56ebe1&amp;req=dScvEM16m4BaUfMW1HO4zcR0rJQ8iuvC7DtpMiX%2FBYk2n9sfcyprwfE8QsmV%0A3%2BVg9a7rhvlKWmMLi3I%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1786446158/c092f1383826cb871493f74169d4/97b7cb98-5da2-438e-a920-e170b8b9790e?expires=1792868400&amp;signature=26207672babe2597684fd0390397f197c52d9ce14246f7f800ed15643bc7f384&amp;req=dScvEM16m4BaUfMW1HO4zcR0rJQ8ieHE7DtpMiX%2FBYnBmXxNenZiq63cPtKD%0AfJLoljsbUXXlTy7Y9mk%3D%0A)
 
 Claude prepares the environment by running any setup commands you've defined in your repository's configuration. This includes installing dependencies, setting up databases, or running other initialization steps your project needs. If your task requires network access, maybe to install packages or fetch data, you can configure the level of internet access the environment has.
 
 Once the environment is ready, Claude begins working on your task. Claude reads your code, makes changes, writes tests, and runs commands to verify the work. You can monitor progress and provide guidance through the web interface if needed.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1786446156/83ecf0a5b98eddc9ffc9694c50f7/353589ce-b678-441d-8909-71b45fa2d065?expires=1792852200&amp;signature=7c19a070a8ce63885fa3ca570559ff2e945bb286677c553c06608ea7e6c2819d&amp;req=dScvEM16m4BaX%2FMW1HO4zVbcTWGL5sbMUQl3YqgIJdYjAi5wBv6u1GMutuZm%0A%2FcaImNmV8sVRzFnAkGg%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1786446156/83ecf0a5b98eddc9ffc9694c50f7/353589ce-b678-441d-8909-71b45fa2d065?expires=1792868400&amp;signature=98cb949b25b8cd7b0bb91bea8f687263abf41cb51fddb9f344e9dbef2ef7b0b7&amp;req=dScvEM16m4BaX%2FMW1HO4zVbcTWGL5czKUQl3YqgIJdYOk4vEeRlcg95XnJOR%0ACsSCHXTBDZDe%2B6GoC4w%3D%0A)
 
 When Claude completes the task, it pushes the changes to a new branch in your GitHub repository. You receive a notification and can review the changes, then create a pull request directly from the interface. The pull request includes all of Claude's work, ready for your review and any additional changes you want to make.
 
diff --git a/content/support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md b/content/support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md
index d6b28884df..d8c6bd86ee 100644
--- a/content/support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md
+++ b/content/support/12883420-view-usage-analytics-for-team-and-enterprise-plans.md
@@ -22,7 +22,7 @@ This page includes the following analytics:
 
 - Sessions in Cowork
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515895966/9f231a620f47d49e0ee648152189/848c1787-4eaa-4809-8fd2-1dbe2722560f?expires=1792852200&amp;signature=b03cd8bf7179d2123f088c362606c618b95f2a05feecf3783e30539d2f2c9ea8&amp;req=diUmE8F3mIhZX%2FMW1HO4zZL6wKR6nodzExEG4dCAGDZbdbcfwxmCqyEOS5k2%0AoWPPg3rjoCvfQBNfteQ%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515895966/9f231a620f47d49e0ee648152189/848c1787-4eaa-4809-8fd2-1dbe2722560f?expires=1792868400&amp;signature=57e8158f56ce496f217ada703c8021f40f2a2a42b82cdde0a4cc7c0f2aad812f&amp;req=diUmE8F3mIhZX%2FMW1HO4zZL6wKR6nY11ExEG4dCAGDbDTLIIbqRHnGfc6GFk%0AEJ8o0ojxxaAbsfccagw%3D%0A)
 
 ### Who’s using Claude?
 
@@ -34,7 +34,7 @@ This page includes the following analytics:
 
 Use the dropdown on the **Active members and assigned seats** chart to filter by product, including Claude Design.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896351/4d955858e6662c37489cc1470871/457cf159-8c2a-4403-ba22-cb92cb47e459?expires=1792852200&amp;signature=c599b57f25e86a2ca4a067187ddac7712caae2b76d91605c82f05e0909def9cc&amp;req=diUmE8F3m4JaWPMW1HO4zYEqezWhR5KtYqPRsgaNdTzfIhg1w9azZuIoh82G%0A0C18BMNBss4c%2BGV7Sjo%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896351/4d955858e6662c37489cc1470871/457cf159-8c2a-4403-ba22-cb92cb47e459?expires=1792868400&amp;signature=9fbbc978dd81145bc7b43bfc05df0732430252832c30d3afab2878537400daca&amp;req=diUmE8F3m4JaWPMW1HO4zYEqezWhRJirYqPRsgaNdTx0W1MI0EEb8dMNJyoS%0Ax7%2FVqGNGrp5e3DH4kHI%3D%0A)
 
 ### How are they using Claude?
 
@@ -48,9 +48,9 @@ Use the dropdown on the **Active members and assigned seats** chart to filter by
 
 - How agentic is their work? (beta)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2583875713/e3cb3c329f3b643cb9a3809876b3/image.png?expires=1792852200&amp;signature=37448684e5f27c54687d9354ca6225660563044d1afd747d7884d9af70315e64&amp;req=diUvFcF5mIZeWvMW1HO4zciS3Krhn7xpDFD6TO7tG4jijd8YR1a6q6MiNuD9%0A1o5NkNhaXIBWh%2BPJ9gs%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2583875713/e3cb3c329f3b643cb9a3809876b3/image.png?expires=1792868400&amp;signature=2ae9973a65bc5d42f29d187e357aad2fae815fe8598f73bcf3af1d1554fd97ee&amp;req=diUvFcF5mIZeWvMW1HO4zciS3KrhnLZvDFD6TO7tG4jSV4jWyR99ZwAfzTvB%0AFdb982H1m1ILrsiJOR8%3D%0A)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896563/abf008596ce5501297a609696362/fce5423c-4769-4b73-9a0a-c50f6407ebea?expires=1792852200&amp;signature=84619939284482bacfc539f9d2e1cc39d07880fe7ac425caa1612cd4e153ad2d&amp;req=diUmE8F3m4RZWvMW1HO4zR%2BID4VmuPX1LS3kobW3ZgQQCG%2Bp7yEHhSs6nbQk%0AJftQJ%2F7xs6iAZ47mgbE%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896563/abf008596ce5501297a609696362/fce5423c-4769-4b73-9a0a-c50f6407ebea?expires=1792868400&amp;signature=cfc71ed9096d62d9ff41fe9fc22540aaa004c2d23a1ad7967fae57cced0049d4&amp;req=diUmE8F3m4RZWvMW1HO4zR%2BID4Vmu%2F%2FzLS3kobW3ZgT3DcpHoYfIJpcTSqJQ%0AFjiaWm5FOqViIoW9J0A%3D%0A)
 
 ### What are the results?
 
@@ -66,7 +66,7 @@ Use the dropdown on the **Active members and assigned seats** chart to filter by
 
 - Estimated time saved
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896943/dd415f03afe56ca38308ef987f86/189e8ebc-5594-4f4b-bd84-e3c11c824d5b?expires=1792852200&amp;signature=c3d73ae10ac1f6bdfc5707317faaf234e7796044a182c8739be2ea499f27c5ca&amp;req=diUmE8F3m4hbWvMW1HO4zfJThSY3rN5EiovaLYNN7RkNlEQTqJM2%2BJb5bwQm%0AYEIyHQ%2FuJ1okgvi13kM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896943/dd415f03afe56ca38308ef987f86/189e8ebc-5594-4f4b-bd84-e3c11c824d5b?expires=1792868400&amp;signature=e5a99f0a947ad5c39569f8470ae0717b9ec0a2bcb2e9a6456009e646eb7b9b13&amp;req=diUmE8F3m4hbWvMW1HO4zfJThSY3r9RCiovaLYNN7Rl9AJ3aslJIKbtxfDnr%0AuOPtHs4hzNMTSuyN30U%3D%0A)
 
 ### How much is Claude costing?
 
@@ -82,9 +82,9 @@ This section includes the following analytics:
 
 - Spend by model (month-to-date, quarter-to-date, year-to-date, 1 year)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896942/b403f2d216fc40b5195911020b8e/446b99f1-3187-4b79-b2be-9f17b1632ff8?expires=1792852200&amp;signature=eb7bc4a950993cffc8754b57375cccc5cebb425a2e7ccc52a9f5742d88c9d147&amp;req=diUmE8F3m4hbW%2FMW1HO4zYE%2BQtwK6TPfWbBLGZ4vBJXHtZ77aentR%2BLY8u5c%0ALCcW8l7b54CpMyN9lfk%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896942/b403f2d216fc40b5195911020b8e/446b99f1-3187-4b79-b2be-9f17b1632ff8?expires=1792868400&amp;signature=3978f551a16b8ec9f7b03368c659d8ce6fbbfb064836a8259549f593294c3c63&amp;req=diUmE8F3m4hbW%2FMW1HO4zYE%2BQtwK6jnZWbBLGZ4vBJXRTv%2FwoWOIULwCKJHF%0ADVCT%2FCDmp4gg5prCqyI%3D%0A)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896941/2239ce38639df339b24d5af1cb50/f829bc2a-ee52-4135-9b13-09ef1b7d66d6?expires=1792852200&amp;signature=1e68f5e81d429453d36490b47fa647a6d6e19c03784845c4e6a56c99557601cb&amp;req=diUmE8F3m4hbWPMW1HO4zTz0N%2BgKIstSC%2BtvTPa1I7HUoS1HQMmSc6yNQdHm%0Ar5DIVQ%2FOxm8a9h4pxI4%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515896941/2239ce38639df339b24d5af1cb50/f829bc2a-ee52-4135-9b13-09ef1b7d66d6?expires=1792868400&amp;signature=3b6ef6aef5c31e7a60e8f57d1cc150b6c1217ad322d329bc9b09e1231c817eac&amp;req=diUmE8F3m4hbWPMW1HO4zTz0N%2BgKIcFUC%2BtvTPa1I7FCbSunzAfAsW6eDkkV%0A7UUOyDjQlVN6OJ2Ujfs%3D%0A)
 
 **Note:** For a view of how spend limits are affecting your organization, you can also check the **Blocked by a spend limit** section at the top of **[Organization settings > Usage](https://claude.ai/admin-settings/usage)**. **Blocked by a spend limit** is built for usage-based Enterprise plans. Orgs without usage-based seats only see how many members are blocked or near their limit right now. Learn more about **[monitoring usage and spend on Enterprise plans](https://support.claude.com/en/articles/11526368-how-am-i-billed-for-my-enterprise-plan#h_ae17ec8236)**.
 
@@ -162,7 +162,7 @@ Navigate to **[Analytics > Claude Chat](https://claude.ai/analytics/usage)** to
 
 - Top members by chats
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515898793/405db0c492da11886c28a2b82731/71a55afc-1cef-4c50-b7e1-86775cb9a168?expires=1792852200&amp;signature=20bcf9854a1dde6ff310eece3350475b54dfb8b8dd66f3c048b0a128d4132f26&amp;req=diUmE8F3lYZWWvMW1HO4zbhc8P%2BUZOYjTcfMEUwBBiUv2j33u46ngGtRuc61%0A6%2BcEolTwTIl5ite99UM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515898793/405db0c492da11886c28a2b82731/71a55afc-1cef-4c50-b7e1-86775cb9a168?expires=1792868400&amp;signature=0c04d50475145be11aa059c69594731de0c3d5c8733fd72507e0a09ed27957e7&amp;req=diUmE8F3lYZWWvMW1HO4zbhc8P%2BUZ%2BwlTcfMEUwBBiVCx0YcErrp3iYaZcVC%0A2qgzm7QndJbW7CATL30%3D%0A)
 
 ### Projects
 
@@ -174,7 +174,7 @@ Navigate to **[Analytics > Claude Chat](https://claude.ai/analytics/usage)** to
 
 - Top members by project usage
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515899610/91d93108f0767e795fb9e488e882/71607d6d-dff1-4a13-a445-aa1d79850eed?expires=1792852200&amp;signature=321133fceec3c9b396740415b858d78de5818f92856c59183db6434adf0e74c9&amp;req=diUmE8F3lIdeWfMW1HO4zWhGoD6RniGgExu5cYiHHN%2FAR4BP2OUaDae70ztG%0A%2BbqoRZDZNOmfZIgoFeQ%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515899610/91d93108f0767e795fb9e488e882/71607d6d-dff1-4a13-a445-aa1d79850eed?expires=1792868400&amp;signature=042c7c751b7c4b99d571a256c3d54c426fee24d3786fd16d7e4518855633b893&amp;req=diUmE8F3lIdeWfMW1HO4zWhGoD6RnSumExu5cYiHHN%2BLnJsvwlv%2BjXM3DcWu%0AJJ2uSt0uzVPv8QNqiqo%3D%0A)
 
 ### Artifacts
 
@@ -184,7 +184,7 @@ Navigate to **[Analytics > Claude Chat](https://claude.ai/analytics/usage)** to
 
 - Top 10 users by artifacts generated (month-to-date, quarter-to-date, year-to-date, 1 year)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515899838/33d737f2357d6e485704669962ae/43faadc3-47da-4a93-bbb7-47a7983e7441?expires=1792852200&amp;signature=1d877a0559fe1912c4ce7dc7f75faf8f634afa8e30973e105b3fb2136643e26a&amp;req=diUmE8F3lIlcUfMW1HO4zcSk47jae%2BzCjHDogqK0V%2ByZXKIPkMHe9G2fjOvS%0AfhY7CClrUXfVqsoDImE%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515899838/33d737f2357d6e485704669962ae/43faadc3-47da-4a93-bbb7-47a7983e7441?expires=1792868400&amp;signature=f4b42d4ec0f71a357d0bc5daa779388e56fb2a142491bb79d587b411b5543367&amp;req=diUmE8F3lIlcUfMW1HO4zcSk47jaeObEjHDogqK0V%2BzwOE8E0CPjbmIiZhnk%0A0kbfZOWVBX0%2F757NopA%3D%0A)
 
 ---
 
@@ -280,7 +280,7 @@ Navigate to **[Analytics > Cowork](https://claude.ai/analytics/cowork)** to view
 
 - Daily, weekly, and monthly active Cowork users
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515901489/8005693d55b7fefbfe9233258d39/106c22a0-3f47-47a6-abbd-4788dd70f218?expires=1792852200&amp;signature=c09a42bc2e865771fc8c78f9e17b11dec2370bfb0012285f6b2751c31b5ca79a&amp;req=diUmE8B%2BnIVXUPMW1HO4zX7WE4q5WEOqFSi1Z3SzLLtEIVjlJchjvdQcDX8U%0A78drMOwm7iBaX2iNgGs%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2515901489/8005693d55b7fefbfe9233258d39/106c22a0-3f47-47a6-abbd-4788dd70f218?expires=1792868400&amp;signature=4915f0d84bc42efc7be4893bbb029e595a3d1f8e90a6e566b578a74b3c5456b6&amp;req=diUmE8B%2BnIVXUPMW1HO4zX7WE4q5W0msFSi1Z3SzLLtNOspEx26%2Bp8lH1dmq%0AlvtPwNWIfPh1ITj1M7k%3D%0A)
 
 **Note:** Cowork analytics are available alongside Chat and Claude Code data in the **[Analytics API](https://platform.claude.com/docs/en/manage-claude/analytics-api)**.
 
@@ -296,7 +296,7 @@ Navigate to **[Analytics > Surveys](https://claude.ai/analytics/surveys)** to as
 
 On Enterprise plans with usage-based billing, when your admin turns on individual usage analytics, any member of the organization can see their own usage broken down by product, model, and skill, along with where they stand against any spend limits set for them. Individual usage analytics are available in **[Settings > Usage](https://claude.ai/settings/usage)**.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2533906328/1f5cd0a57def40676410f8f379b4/member-usage-30d-model.png?expires=1792852200&amp;signature=c9a64e17aa8024ce8613dd2d4d13a83a12c69304a5f848ff89f1a0c7ebe66d3e&amp;req=diUkFcB%2Bm4JdUfMW1HO4zfveBq3NeenYWGUKUw6QS4%2F712i%2FrD1Hvdn5kDEa%0AZSlPbGG1AjfKBCJjMCY%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2533906328/1f5cd0a57def40676410f8f379b4/member-usage-30d-model.png?expires=1792868400&amp;signature=c8788525c8b9badbb2fc89487278b3f991026beee3cf5b9f53a575be8e351ae1&amp;req=diUkFcB%2Bm4JdUfMW1HO4zfveBq3NeuPeWGUKUw6QS48CRqt2S%2F7En3Z42sk%2F%0Acj%2BZv6uW58ScuQeXtIU%3D%0A)
 
 ---
 
diff --git a/content/support/12997503-team-plan-billing-faqs.md b/content/support/12997503-team-plan-billing-faqs.md
index ba3bfb7015..a0b79f3acc 100644
--- a/content/support/12997503-team-plan-billing-faqs.md
+++ b/content/support/12997503-team-plan-billing-faqs.md
@@ -18,7 +18,7 @@ Your organization's billing address determines where your invoices are sent. You
 
 If you want to use a name other than the one tied to your payment method, an organization Owner should check the "Use a different name on invoices" box when adding or updating your payment method in **[Organization settings > Billing](https://claude.ai/admin-settings/billing)**:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1922145253/f2e3d4e0fe43a2ea07e89244764c/image.png?expires=1792852200&amp;signature=8bd29d9601d9344c88301d219919f47dcce097046fcbd00c2254e2b0d1d5e59b&amp;req=dSklFMh6mINaWvMW1HO4zRZTxVjJvsnRKAqLF4ERnlV0X3tIwQ7gFFm26%2FQ0%0APi8VaeAnsm8CTHFRYSo%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1922145253/f2e3d4e0fe43a2ea07e89244764c/image.png?expires=1792868400&amp;signature=3b3a64bc545f32d3b4d1283aea16754a32f00f416846c5be5b6f6dc4aeeda38d&amp;req=dSklFMh6mINaWvMW1HO4zRZTxVjJvcPXKAqLF4ERnlWmtlYN4KsBoPzAPaHZ%0AdZ%2B4U6BrIaH%2BAh7cEpk%3D%0A)
 
 ## When will I be billed?
 
diff --git a/content/support/13132885-set-up-single-sign-on-sso.md b/content/support/13132885-set-up-single-sign-on-sso.md
index 260ac02113..b37de25e52 100644
--- a/content/support/13132885-set-up-single-sign-on-sso.md
+++ b/content/support/13132885-set-up-single-sign-on-sso.md
@@ -42,7 +42,7 @@ You can verify multiple domains for a single organization, but all domains must
 
 3. Enter the domain(s) you want to verify in the **Update organization email domains** modal and click the “+” button:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2498843282/561d5ceb1c3a5df75bdfee8bfc3f/d2491145-362d-490b-bdcf-66a0a7656ddc?expires=1792852200&amp;signature=07ffaff3e923c2a76ef51277c842dc68b8d930bcd7838405bcfb72f5d4534fde&amp;req=diQuHsF6noNXW%2FMW1HO4zSdmH34x%2F8aOe3H0OpmIzWHPeQNi1etWdVtPviSf%0ArxJE%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2498843282/561d5ceb1c3a5df75bdfee8bfc3f/d2491145-362d-490b-bdcf-66a0a7656ddc?expires=1792868400&amp;signature=63ccaeb68c347f6217993957a5b220bbbe1204704ad44a9c1d7023652d390b46&amp;req=diQuHsF6noNXW%2FMW1HO4zSdmH34x%2FMyIe3H0OpmIzWG1MSgaKkda9KT5VKum%0AkRG6%0A)
 
 4. Click “Save” when you’re finished adding domains.
 
@@ -50,7 +50,7 @@ You can verify multiple domains for a single organization, but all domains must
 
 6. Enter your domain in the text box and click “Continue”:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2047042630/0617a562cd28a7ff0e607d66a30b/6bd08e1d-2b65-40ab-bc79-a257153854c1?expires=1792852200&amp;signature=7a43970eb5283c99de8dcf6b3b004593d334ad873a565b92afedb020ca3aee0b&amp;req=diAjEcl6n4dcWfMW1HO4zWHctB%2BfktOoyoyXAW0OlXo%2FYw7VCdOuXbsMr5wq%0AlNF4%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2047042630/0617a562cd28a7ff0e607d66a30b/6bd08e1d-2b65-40ab-bc79-a257153854c1?expires=1792868400&amp;signature=042d223335ffffb8e1ef207066f70e29af0b987f56efa9273085dff2c01d6c7a&amp;req=diAjEcl6n4dcWfMW1HO4zWHctB%2BfkdmuyoyXAW0OlXr8xKPx%2BAauwPDtC01T%0AncV3%0A)
 
 7. The setup screen displays a TXT record. **Copy the full Value using the copy button**—it begins with `anthropic-domain-verification-` and is longer than what's visible in the box. In your DNS provider, add a TXT record to your domain and **Value** set to the copied string. The domain must match exactly what you entered in the previous step, including any subdomains. Add it alongside any existing TXT records; don't replace them. The value is case-sensitive, so paste it exactly. Please refer to your DNS provider's documentation on this topic.
 
@@ -76,7 +76,7 @@ Clicking "Refresh" re-checks your DNS; it won't show Verified until the publishe
 
 If the record is correct and propagated but the status still shows Pending, contact Support.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2047044496/b8df54a0331784cc9ae8f00112aa/bf9609c1-dc93-4665-a066-4cae2fe4b002?expires=1792852200&amp;signature=02012671912345c73a2d4dd255a3b9d3e31f598374cbcbef367fcdab088d8b4d&amp;req=diAjEcl6mYVWX%2FMW1HO4zVjmWCsIana7PM2D8ZcdgrivVyDi2Gzetzk8FboB%0ArE8TxEUu1BYDJemcI%2FA%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2047044496/b8df54a0331784cc9ae8f00112aa/bf9609c1-dc93-4665-a066-4cae2fe4b002?expires=1792868400&amp;signature=5986065f1c55692b42ecad0b73119a0b99ec3f75ac9b955fe8f62d740fc941ab&amp;req=diAjEcl6mYVWX%2FMW1HO4zVjmWCsIaXy9PM2D8Zcdgrjyov%2FOlaN%2Fkh3%2Bxnvd%0ApKpsBIGEV4DJKXuMxKk%3D%0A)
 
 **Note:** Once your domain is verified, you'll see a **Restrict organization creation** toggle under **Security** on the Organization and access organization settings page. Enable this if you want to prevent users from creating new Claude or Console organizations—including personal accounts—using your verified domains.
 
@@ -116,7 +116,7 @@ For IdP-specific setup instructions, see:
 
 You can now choose to toggle on **Require SSO for Console** and/or **Require SSO for Claude,** on the **Organization and access** page, under the **Authentication** section:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312690200/bd2403586d4f6651ccd79e2a45af/b9f8d7ce-0def-49d9-bfb2-3a14352d7214?expires=1792852200&amp;signature=cff6c7ccd014d2833daed26944a82fd879d690ef93812ce4df9d12e9a4c083c4&amp;req=diMmFM93nYNfWfMW1HO4zdAICg2pB34IItXtKivx6ZGnPBdi4Y8evM%2BhtW%2F1%0AUGKMizYH99U0dTHFQwI%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312690200/bd2403586d4f6651ccd79e2a45af/b9f8d7ce-0def-49d9-bfb2-3a14352d7214?expires=1792868400&amp;signature=ee339917893a2b4c7e215619c83f571553a5bb9b02e906e96c8e5b48198ad408&amp;req=diMmFM93nYNfWfMW1HO4zdAICg2pBHQOItXtKivx6ZEL3GKndntEYb90WsSk%0A9iWXGifTnr70J3DMI9U%3D%0A)
 
 When SSO is required, users must use the “Continue with SSO” option to log in to their Claude/Console accounts. When SSO is not required, they will have the option to choose “Continue with SSO” or “Continue with email.”
 
diff --git a/content/support/13133195-set-up-jit-or-scim-provisioning.md b/content/support/13133195-set-up-jit-or-scim-provisioning.md
index 0ba883be3b..099902a4c5 100644
--- a/content/support/13133195-set-up-jit-or-scim-provisioning.md
+++ b/content/support/13133195-set-up-jit-or-scim-provisioning.md
@@ -40,7 +40,7 @@ Use this table to help decide which provisioning mode is right for your organiza
 
 Both JIT and SCIM can be combined with **Enable group mappings** to control role or seat tier assignment based on IdP group membership. If you select either of these options for your provisioning mode, **Enable group mappings** will appear within the **User provisioning** section:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312706099/35d5d3ec149880a96bb7acec59f6/a4cfce55-86bf-40b0-b455-c8f412d48e9e?expires=1792852200&amp;signature=366e2875727d128432740250ee9737235ed6d16f237bd7f5508c8aa26829b4a8&amp;req=diMmFM5%2Bm4FWUPMW1HO4zXBDQqlcCFh0xFMG%2BIEvQSf%2FgOCNgKh3nUW3TCJT%0AvWtEwoyGE%2BDFhc9BkRQ%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312706099/35d5d3ec149880a96bb7acec59f6/a4cfce55-86bf-40b0-b455-c8f412d48e9e?expires=1792868400&amp;signature=7ab0473140aff31ebb5dc85cdc8e5d309dc01d700c75c43946d2ca922287994a&amp;req=diMmFM5%2Bm4FWUPMW1HO4zXBDQqlcC1JyxFMG%2BIEvQSejjR9%2FdUr%2FZ%2FlTTFjm%0A%2Fq%2BnPtcsXnUpaDZqQno%3D%0A)
 
 **Important:** Group mappings set a user’s role type and seat tier only. Users with the Custom role get their permissions from groups in Claude, and those groups sync from your IdP only when your provisioning mode is SCIM directory sync. With JIT, you need to create groups and add users to them manually in **[Organization settings > Groups](https://claude.ai/admin-settings/groups)**. If you map an IdP group to the Custom role under JIT without doing this, those users have no permissions when they log in. Learn more about **[managing groups on Enterprise plans](https://support.claude.com/en/articles/13799932)**.
 
@@ -136,7 +136,7 @@ Learn more about **[setting up role-based permissions on Enterprise plans](https
 
 4. Toggle **Enable group mappings** on (if it’s not already):
 
-  ![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312714635/b57870b51e6511c8293637bceee2/da1ceabc-b6bc-451b-9cda-24ff6aa90d02?expires=1792852200&amp;signature=e3424c1e38cf3f742784d7f51c19fec995ee54dfebf37e9d16c1fdfd9a282138&amp;req=diMmFM5%2FmYdcXPMW1HO4zeBEb8fQkvhKyb72rapuHpO20kV%2BHxHyQfCuCnaN%0AaMPN%0A)
+  ![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312714635/b57870b51e6511c8293637bceee2/da1ceabc-b6bc-451b-9cda-24ff6aa90d02?expires=1792868400&amp;signature=a4626e41adb4030c388d4fa448aeee943e3ace4863e6d7c8121feb6e064a04d8&amp;req=diMmFM5%2FmYdcXPMW1HO4zeBEb8fQkfJMyb72rapuHpM023d8Ax%2Fta3fb3Icp%0ADdOa%0A)
 
 5. In the **Enable group mappings** section, click “Add” next to each role and select the corresponding group from your IdP in the dropdown.
 
@@ -188,7 +188,7 @@ Verify you have enough seats purchased and available to add members to your org.
 
 4. **For SCIM:** Click "Sync" to prompt an immediate sync, or wait for the automatic sync cycle:
 
-  ![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312717421/c97fce49ad17d4660880a05fbaaf/59fbfa2a-1072-4662-8ca5-102970d5a795?expires=1792852200&amp;signature=aa5cba49e548bf7398569d5c686e2f3965617ed7dadf6c784d512afbc6e25b87&amp;req=diMmFM5%2FmoVdWPMW1HO4zZ9Lal%2BlHMjA5hujYvMis4c15Pcg8mxviGxNZ%2BKq%0Af%2B82%0A)
+  ![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312717421/c97fce49ad17d4660880a05fbaaf/59fbfa2a-1072-4662-8ca5-102970d5a795?expires=1792868400&amp;signature=cbf09b0ceb48439de5cc4f50602fc1577f42a05087d7379858202b4718b797bf&amp;req=diMmFM5%2FmoVdWPMW1HO4zZ9Lal%2BlH8LG5hujYvMis4ciK4EvaJ10nrPjBb%2Fd%0A3Bb7%0A)
 
 ### Users mapped to the Custom role can't access anything after logging in
 
diff --git a/content/support/13163631-configuring-session-security-settings.md b/content/support/13163631-configuring-session-security-settings.md
index a2ab251227..d68b2ecdd1 100644
--- a/content/support/13163631-configuring-session-security-settings.md
+++ b/content/support/13163631-configuring-session-security-settings.md
@@ -18,7 +18,7 @@ Session duration controls allow Enterprise and Console Admins to set a maximum s
 
 5. Confirm your selection by clicking “Enable.”
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1888469436/1725e63ea1a2615948faecf4ec73/9bd276a1-7329-414d-87a1-d04dac93fff7?expires=1792852200&amp;signature=b42221b7511bf1af204ba96778fb66d94db9ba619dd745011ee15ce914d25f0e&amp;req=dSgvHs14lIVcX%2FMW1HO4zQNx6uAvRlhSg%2F6XaftFnjxT0DCO17ABWA%2FtFt8%2B%0A5oVfJvOUVsp1UWi3Hq0%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1888469436/1725e63ea1a2615948faecf4ec73/9bd276a1-7329-414d-87a1-d04dac93fff7?expires=1792868400&amp;signature=88393abc587bd030e9748d05674590f5c6620437e7e2d2aaf02596e7408bccf9&amp;req=dSgvHs14lIVcX%2FMW1HO4zQNx6uAvRVJUg%2F6XaftFnjyewpqekr8w3Gok80Z6%0ADOQJC%2BO3mLOudRZ0iEs%3D%0A)
 
 ### For Console Admins
 
@@ -32,7 +32,7 @@ Session duration controls allow Enterprise and Console Admins to set a maximum s
 
 5. Confirm your selection by clicking “Enable.”
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1888469435/7a766bbe02e61c7d8f05deb5b8f0/b0bda400-47c6-43dd-9907-131ebe180b36?expires=1792852200&amp;signature=8162f558d7962003281ae5e589562b452853a87bd411067eaa471c6ee3a079af&amp;req=dSgvHs14lIVcXPMW1HO4zWzx2bs%2BIn0jXZ5D7eVpMtdwIZkqeJ2ydaIlcdhs%0AfSsRsLZmYheabvi4R44%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1888469435/7a766bbe02e61c7d8f05deb5b8f0/b0bda400-47c6-43dd-9907-131ebe180b36?expires=1792868400&amp;signature=6c73bfe1fca79e1c286fc773174b250b45a7991a944a69d7a8ae0fdde1b2c172&amp;req=dSgvHs14lIVcXPMW1HO4zWzx2bs%2BIXclXZ5D7eVpMtdm6vge4Twn3VabuTIV%0ARJsD0V0w%2BXSwfYDJDlE%3D%0A)
 
 ### What happens after enabling shortened session length?
 
@@ -50,7 +50,7 @@ You can change the session duration at any time by selecting a new value from th
 
 - Sessions scheduled to expire beyond the new duration will have their expiration shortened accordingly.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1888469437/46ac5bc55484ca01556d87a5ade7/b01a7651-ad65-4b32-93ff-16dbc9ca97c0?expires=1792852200&amp;signature=22b450684226f2b12bf51c0a80bbc345cff646be1460b725e3e9a0ed838e1939&amp;req=dSgvHs14lIVcXvMW1HO4zZ7mW8qT4juhA00cbyPOLDVZhkMjnByRlO0q7ZPq%0AwgkOhN8VqclyaKQIeio%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1888469437/46ac5bc55484ca01556d87a5ade7/b01a7651-ad65-4b32-93ff-16dbc9ca97c0?expires=1792868400&amp;signature=e10d998fe9799ce5d1739f032cae11572df05af1a745afce13f2223077bfab5d&amp;req=dSgvHs14lIVcXvMW1HO4zZ7mW8qT4TGnA00cbyPOLDXrXwoLrqUOEtAKCIkd%0ATTtEnEM2cSOmkqRV%2Fjg%3D%0A)
 
 ## Disabling session length settings
 
diff --git a/content/support/13189465-log-in-to-your-claude-account.md b/content/support/13189465-log-in-to-your-claude-account.md
index b96aa9a7a5..b7bb46d75e 100644
--- a/content/support/13189465-log-in-to-your-claude-account.md
+++ b/content/support/13189465-log-in-to-your-claude-account.md
@@ -2,7 +2,7 @@
 
 When you open Claude on a web browser ([claude.ai](https://claude.ai)), the desktop app, or a mobile app, you will see two different options for logging in to your Claude account.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1893216804/f2209c3ec6cf4fc2e803d13bbc9d/40520c9e-ff82-4a7c-adca-5a064fe18d8c?expires=1792853100&amp;signature=50588c5d5da1dbc325daecfce84135066ec56bbebee2b24200fbe27cbbe2acca&amp;req=dSguFct%2Fm4lfXfMW1HO4zXg5B4CE5hG1zWhrqpWiTMlJPuxIZ%2FoBJisw3ST0%0A8UKRHMMUdCs1tUqPddg%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1893216804/f2209c3ec6cf4fc2e803d13bbc9d/40520c9e-ff82-4a7c-adca-5a064fe18d8c?expires=1792868400&amp;signature=36c1080058704bf5aeed39f8e37ea6c972b4a5385e374d43834956b3d6fb6280&amp;req=dSguFct%2Fm4lfXfMW1HO4zXg5B4CE5RqwzWhrqpWiTMnWq4ZRbr2HvOcFslf%2F%0ANDBoM849bjU6LawGI%2Fk%3D%0A)
 
 ## Continue with Google
 
diff --git a/content/support/13371040-log-in-to-your-console-account.md b/content/support/13371040-log-in-to-your-console-account.md
index dcf0c7b4de..3413f77ef2 100644
--- a/content/support/13371040-log-in-to-your-console-account.md
+++ b/content/support/13371040-log-in-to-your-console-account.md
@@ -2,7 +2,7 @@
 
 When you navigate to the **[Claude Console](https://platform.claude.com)**, you will see two different options for logging in to your Console account.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1935026646/d90d1613a3dbe763fef5abb96e3c/image.png?expires=1792852200&amp;signature=f6f4b7fad0cad264c1437c07533694b4034d6501480d8e727b6e4d4af479139e&amp;req=dSkkE8l8m4dbX%2FMW1HO4zcrI5ovkpYIP8vUNcPt4%2B70DpLnylrndtQajW6ys%0Ap6cLmc0QpjVVmFxUbso%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1935026646/d90d1613a3dbe763fef5abb96e3c/image.png?expires=1792868400&amp;signature=f565ca0e33366b94fe3c67e74a70c2ae73ab7f3934ce69cdac18101aa6549170&amp;req=dSkkE8l8m4dbX%2FMW1HO4zcrI5ovkpogJ8vUNcPt4%2B71LIlfJiHnk0ohsITu1%0AHaFIOaX2yR2L%2FgBUH%2Fg%3D%0A)
 
 ## Continue with Google
 
diff --git a/content/support/13641943-visual-and-interactive-content.md b/content/support/13641943-visual-and-interactive-content.md
index 9ffd3aa139..d3521e25ba 100644
--- a/content/support/13641943-visual-and-interactive-content.md
+++ b/content/support/13641943-visual-and-interactive-content.md
@@ -18,7 +18,7 @@ Claude can show current weather conditions and forecasts when you ask about the
 
 Claude automatically displays temperatures in Fahrenheit for US locations and Celsius for everywhere else.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2040544927/3a9c695b24df387ecdd766ad308c/8be9f393-dcb0-4ff8-89e8-5fa47bedaa38?expires=1792852200&amp;signature=2399e1bf42c15d598e4c518ae54da66427ecc56ba16d45cefb0af28468e6db97&amp;req=diAjFsx6mYhdXvMW1HO4zXlB7Dyy0BqKdgndksVD5R3kQMn7hGsBE5ydoBVH%0AbX%2FGE%2Fim4i4TxGwn6No%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2040544927/3a9c695b24df387ecdd766ad308c/8be9f393-dcb0-4ff8-89e8-5fa47bedaa38?expires=1792868400&amp;signature=29892a261d17fe4739796a6f9f61e6688223354fe670a86bff1668752ad7d2b7&amp;req=diAjFsx6mYhdXvMW1HO4zXlB7Dyy0xCMdgndksVD5R1cx8AtX3U4x4TBe2tk%0ALgub%2Fe3id4fRiMAt1tI%3D%0A)
 
 Weather is powered by Google Maps (<https://policies.google.com/privacy>).
 
@@ -28,7 +28,7 @@ When you ask about recipes, Claude can display formatted recipe cards that are e
 
 **Note:** Visual recipe cards are available on web and desktop only. On mobile, Claude provides recipe information as text in the conversation.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2040544929/12f4c51eda7779d65d3ea2c7ab16/d0f4a314-cff8-421a-b401-10c2bf50374e?expires=1792852200&amp;signature=40ac7657a4882070061a3db0d72e41847c2c6d9e448fddfb259cf3c3c23f5f15&amp;req=diAjFsx6mYhdUPMW1HO4zUQperId11aVrIPm%2FImZVg1gOhQzMQRogJ2Zqss9%0ApW8L40AIWgSWrqS4jBY%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2040544929/12f4c51eda7779d65d3ea2c7ab16/d0f4a314-cff8-421a-b401-10c2bf50374e?expires=1792868400&amp;signature=7b674d209ac5133302f4f85c7bb42e40db2f027dd9962cb4bc879244bb4280e0&amp;req=diAjFsx6mYhdUPMW1HO4zUQperId1FyTrIPm%2FImZVg22uk1X5ZGRmIRs%2F48x%0AK4fBKciUXAsBpIzkUjY%3D%0A)
 
 ### Custom visuals
 
@@ -76,7 +76,7 @@ For example, if you ask Claude to help you plan a trip, it might ask you to:
 
 This content appears at the bottom of the chat. You can still type a response if you prefer.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2040544930/9ad066e137d11e4b559b0217e12d/9bf30d2d-1715-42b3-9da5-2a9298f41f08?expires=1792852200&amp;signature=c838d70d0a573133ef900de0111d1e6cf30a32bd85c73af853beea15fac9a81f&amp;req=diAjFsx6mYhcWfMW1HO4zWmF5ve2bBygx4wz0C7CTAK9dQXdJZS%2BZ%2FvZqbzw%0ABZB7rYFZm2q5wTWJF%2Fs%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2040544930/9ad066e137d11e4b559b0217e12d/9bf30d2d-1715-42b3-9da5-2a9298f41f08?expires=1792868400&amp;signature=4706cba5eed9ecab5adadabb8a039483379a97bcc5fb5cb025a8242e842e92cb&amp;req=diAjFsx6mYhcWfMW1HO4zWmF5ve2bxamx4wz0C7CTALqy%2FW7Gohunv65nmUA%0AP0VrrUlC%2BAvHfQ3lTYg%3D%0A)
 
 ---
 
diff --git a/content/support/13837440-use-plugins-in-claude.md b/content/support/13837440-use-plugins-in-claude.md
index 0b7af66d28..fe3043ff0c 100644
--- a/content/support/13837440-use-plugins-in-claude.md
+++ b/content/support/13837440-use-plugins-in-claude.md
@@ -58,7 +58,7 @@ In Cowork, open the "Cowork" tab first, then open **Customize**.
 
 You can also upload a custom plugin file if you built one yourself. On Team and Enterprise plans, a colleague can share a plugin with you directly instead of sending you the file. See **[Use a plugin shared with you](#h_ef985546b4)** below. Plugins you add in Claude on the web or in Claude Desktop are saved to your account, not to your computer, so they follow you to chat, Cowork, and Claude Code.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2100409211/fc01614dde1a616fa31ffaa9cb04/47bacf5b-a810-45b5-a468-9769f1a58ef8?expires=1792852200&amp;signature=4edfc506756465e65bfd6b5001245a69db0550abb1868968c4defc74f0854c60&amp;req=diEnFs1%2BlINeWPMW1HO4zZF3IxfVNvdXxakFVfq5WwwjlulxvitLsiEUCvV2%0AfOB4GJIZRnp5vNUiJnQ%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2100409211/fc01614dde1a616fa31ffaa9cb04/47bacf5b-a810-45b5-a468-9769f1a58ef8?expires=1792868400&amp;signature=14bedd85fc6c27cf2a6a9983df6af8e00cb6a9c40833d58af6d5e27d886822a4&amp;req=diEnFs1%2BlINeWPMW1HO4zZF3IxfVNf1RxakFVfq5WwxEeCQHSXUVoW%2FnLDpx%0ABLtGc5BSKRAKDcJGY8g%3D%0A)
 
 If you're on the Enterprise plan and your organization has skill scanning turned on, plugins are checked for malicious content when they're installed or updated. A plugin with malicious content is blocked, and one that may carry risk shows a caution banner. Learn more about **[skill and plugin scanning](https://support.claude.com/en/articles/15927065)**.
 
@@ -68,7 +68,7 @@ If you're on the Enterprise plan and your organization has skill scanning turned
 
 Each plugin you add brings skills and commands you can use while working with Claude. Type "/" or click the "+" button to see the available skills from your plugins, in chat and in Cowork. In Cowork, you can also run a plugin's command by typing `/plugin-name:command`. Click any skill to see its details.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2157396844/4a790e10f5b88df770783df1d7e9/image.png?expires=1792852200&amp;signature=915708a741200aced98f7bb2f178bfa4c9979bb85b0c158d838cfd9f58766a65&amp;req=diEiEcp3m4lbXfMW1HO4zf4NBfT0hkKWmKUxugP2BQsOTGyLfo5oLQzOTEGd%0AopZw14jPi9fbDvVBbps%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2157396844/4a790e10f5b88df770783df1d7e9/image.png?expires=1792868400&amp;signature=a1e8145fd4e634870b3f35e5c31aeac20fc0bce3c163cfc5ed8c3d544c239f12&amp;req=diEiEcp3m4lbXfMW1HO4zf4NBfT0hUiQmKUxugP2BQuPlt1qljtZTsQPKQPf%0AnXxZ4%2BZSol4nqVlCvIo%3D%0A)
 
 ---
 
diff --git a/content/support/14499648-how-scim-sync-works-for-enterprise-organizations.md b/content/support/14499648-how-scim-sync-works-for-enterprise-organizations.md
index ebe5c332d3..84ab78f1cf 100644
--- a/content/support/14499648-how-scim-sync-works-for-enterprise-organizations.md
+++ b/content/support/14499648-how-scim-sync-works-for-enterprise-organizations.md
@@ -50,7 +50,7 @@ You can trigger a manual sync from two places in your admin settings.
 
 2. Click "Check for updates" under **SCIM sync**:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312613548/44cd5970ee3c3b2c7f8dcd592d71/image+%2824%29.png?expires=1792852200&amp;signature=0fb05eaba63571871bf243c47b8bf6ab7f295fd72b41599f8252d239ead4569f&amp;req=diMmFM9%2FnoRbUfMW1HO4zW4gbTelMM%2B2rgfl7PnOiulroSxNliTB3fqdv3IG%0AMbyu%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312613548/44cd5970ee3c3b2c7f8dcd592d71/image+%2824%29.png?expires=1792868400&amp;signature=dde18103365899037e62c6b0957d48d535915cb40ea0dd1c085f0a0327533342&amp;req=diMmFM9%2FnoRbUfMW1HO4zW4gbTelM8Wwrgfl7PnOiuk7OzZh0fzvwOYwEJ6k%0AsM%2Ba%0A)
 
 3. Select whether to sync members, groups, or both.
 
@@ -62,7 +62,7 @@ You can trigger a manual sync from two places in your admin settings.
 
 3. Select whether to sync members, groups, or both:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312608119/e4b0ef4f309f3c4eac8311a6ef47/image.png?expires=1792852200&amp;signature=2c67f645b6b3a3d0b1ccadb23ab90355c840471256677ba425e58b9098e198e7&amp;req=diMmFM9%2BlYBeUPMW1HO4zX%2F4f7j4zjkd43OpyTHzM9R8M1tPwPuEaqnMXfVW%0AjAGu%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312608119/e4b0ef4f309f3c4eac8311a6ef47/image.png?expires=1792868400&amp;signature=8164ea195d30113b504b624bd61d9cbc7d077ccc9196bc6487e8e85385f45df9&amp;req=diMmFM9%2BlYBeUPMW1HO4zX%2F4f7j4zTMb43OpyTHzM9TxCJ3w489kQRB%2FMgB%2F%0AtLlg%0A)
 
 **Note:** If you trigger a manual sync while background changes are processing, your organization takes the most recent change for each member or group. If multiple changes are queued for the same member or group, you may need to resync again to make sure everything applies correctly.
 
diff --git a/content/support/15330088-set-a-default-model-for-your-organization.md b/content/support/15330088-set-a-default-model-for-your-organization.md
index 86ddc55f98..9c6b2dd0b7 100644
--- a/content/support/15330088-set-a-default-model-for-your-organization.md
+++ b/content/support/15330088-set-a-default-model-for-your-organization.md
@@ -50,7 +50,7 @@ The organization default applies to every member. To set it:
 
 4. Click “Save changes.”
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514722139/d05c94072a41ea9090ecf386c53e/c32ee31d-954a-4551-a2da-91677fbd0b6f?expires=1792852200&amp;signature=a32fef09bc7ebb6c6b0dcfc23e3b5165e5e1c8c9bb24d1d652cb87f007abfcc0&amp;req=diUmEs58n4BcUPMW1HO4zelOdjBIKEpFfdGVZ664dGEbOrf%2FOcClfHZWtimB%0AjhHT1dhJUk%2Fr5Qtk4%2Bo%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514722139/d05c94072a41ea9090ecf386c53e/c32ee31d-954a-4551-a2da-91677fbd0b6f?expires=1792868400&amp;signature=d7d771ed4fa83fc0f0e9138fb5fd44cf6f6d46d1292aa9b05127c1079ff6f57a&amp;req=diUmEs58n4BcUPMW1HO4zelOdjBIK0BDfdGVZ664dGF6uzPw46oIMUXnF1h4%0Aatr9s8p9y%2Bps1hGAwUg%3D%0A)
 
 ---
 
diff --git a/content/support/15694740-manage-model-access-for-your-organization.md b/content/support/15694740-manage-model-access-for-your-organization.md
index ab3fc484cb..58308a3f4f 100644
--- a/content/support/15694740-manage-model-access-for-your-organization.md
+++ b/content/support/15694740-manage-model-access-for-your-organization.md
@@ -42,9 +42,9 @@ The organization setting is the ceiling. A role can't grant access to a model th
 
 If any custom role uses the model you’re disabling as its default, you’ll be prompted to change that role’s default before the change can be saved.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514693921/02ea72756f5163f14e5d158516dc/69102088-cd86-498e-97aa-c8a6e0004419?expires=1792852200&amp;signature=d35e5eb561e868c3f6408eeee34aa419b61021076c487d23dfefa2f64d1c3986&amp;req=diUmEs93nohdWPMW1HO4zXlxE%2BWxUtNVQf5Pb7M2Q0snYh8O8iXcRW89fQwr%0A9HYm%2FUUmxGmV6kdjp7Y%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514693921/02ea72756f5163f14e5d158516dc/69102088-cd86-498e-97aa-c8a6e0004419?expires=1792868400&amp;signature=b5415f2f022612f7f938532bd991a6ff61342bfb84415e4759c7406ec234817a&amp;req=diUmEs93nohdWPMW1HO4zXlxE%2BWxUdlTQf5Pb7M2Q0tW0%2FknS9%2FSxjxx1uSc%0AC%2BR74GtL0tStwYArxz8%3D%0A)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514693922/bfc5de6626eb19dca1d7caf818ca/c3cd8bb6-f86c-4d01-92da-6ae4ca966662?expires=1792852200&amp;signature=c2206ac76a55f5a0abd16485aaadce501ab347d43ab49dd0ab6bad34df0f22b7&amp;req=diUmEs93nohdW%2FMW1HO4zTqNsIvNQ1pVAod9uc510lwA4odx44dy8X8AwGpw%0AmEK%2BauacggMdvZML1%2BM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514693922/bfc5de6626eb19dca1d7caf818ca/c3cd8bb6-f86c-4d01-92da-6ae4ca966662?expires=1792868400&amp;signature=6808694462cc4e3c56bf2ecf9d14de52230d4a48eb31f93dce788009f1ee17ff&amp;req=diUmEs93nohdW%2FMW1HO4zTqNsIvNQFBTAod9uc510lyjIXLUnV6cNduw%2FUhA%0ATw0NF%2BxrnmvaiNFsRh0%3D%0A)
 
 ---
 
@@ -78,7 +78,7 @@ If any custom role has an effort cap higher than the new organization cap for th
 
 Only models the role grants access to can be selected as that role’s default model.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514693923/880665a87dbd4776cf19d6063a37/29d30c6d-f9fc-408c-8c72-4320c6d88d14?expires=1792852200&amp;signature=7d7c9b9f64dc7ef6a347fa721c44be23300508383e4daad1b52622f645b92036&amp;req=diUmEs93nohdWvMW1HO4zYj9SPcL6IO%2FXsqpNqvyFRJYD31%2Fphbh%2BueoIq%2F%2B%0AK12RY%2BgIk2sYXIrV0W8%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514693923/880665a87dbd4776cf19d6063a37/29d30c6d-f9fc-408c-8c72-4320c6d88d14?expires=1792868400&amp;signature=def23086f56950fcd1f576a58a2f7e6e2a3ef54101b0aa194029a5934fe185fb&amp;req=diUmEs93nohdWvMW1HO4zYj9SPcL64m5XsqpNqvyFRIiMePGcoyGW8LZn5Rx%0ADVm3eIm71Cx44WyeQqo%3D%0A)
 
 ---
 
@@ -96,7 +96,7 @@ Effort limits determine how much computation members on a role can apply per res
 
 5. Click "Save" to save your changes.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514693927/7a25673b3b075d72adb3cdc371e3/d2d7cd8d-a713-4e91-a706-f589ac46a9fe?expires=1792852200&amp;signature=f5a15aa8f7efb7b148d1305c955fc9a34e3e1c8887237ea743cff2f117836143&amp;req=diUmEs93nohdXvMW1HO4ze1xBzG0drsbDeA1RkowXUHqYNlXxagAZi4f8Rve%0A3K08P2%2BlVdJiO7RSomM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2514693927/7a25673b3b075d72adb3cdc371e3/d2d7cd8d-a713-4e91-a706-f589ac46a9fe?expires=1792868400&amp;signature=9a3a138b074e6a27419282d3d9cbb5e15efa6d0ad0a2333fb35529fa89dad6f2&amp;req=diUmEs93nohdXvMW1HO4ze1xBzG0dbEdDeA1RkowXUESjDfmv%2BEFQqDbea%2BI%0A7rT4OSlI9jRJMZul8a0%3D%0A)
 
 Members on the role see only effort levels at or below the cap in their model menu. Note that available effort levels differ depending on the model, and some models don’t support effort level settings at all. For an explanation of each level, see **[Change the model, effort, and thinking settings](https://support.claude.com/en/articles/8664678)**.
 
diff --git a/content/support/15936181-get-started-with-1password-for-claude.md b/content/support/15936181-get-started-with-1password-for-claude.md
index c9f40d64da..b167bd824b 100644
--- a/content/support/15936181-get-started-with-1password-for-claude.md
+++ b/content/support/15936181-get-started-with-1password-for-claude.md
@@ -52,7 +52,7 @@ Once the requirements are in place, you can set up 1Password from a few places i
 
 4. Toggle on **Password managers**:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2546126596/ba71ca47e2df21cec62c243831f8/5b1c67e1-607d-4c73-8f61-d1ceb081082a?expires=1792852200&amp;signature=d7603a353c2efd6bf3d4c233fb3443ff3a94a25a4a56b859bc92a1d36495a664&amp;req=diUjEMh8m4RWX%2FMW1HO4zU5ln2lmqMdhGkiu4hEpcPUvYpfuWX2YkY%2FeqAU5%0Ad5My2GQM6I%2FBqkaqBnY%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2546126596/ba71ca47e2df21cec62c243831f8/5b1c67e1-607d-4c73-8f61-d1ceb081082a?expires=1792868400&amp;signature=fb5edb782e4311f1aa072450b777dd034fa06daa89cac4462eb4df4fafb42c4e&amp;req=diUjEMh8m4RWX%2FMW1HO4zU5ln2lmq81nGkiu4hEpcPWUA8IcQhgIOM9sj44%2B%0Ak2btm5IaBcf7W11vBO0%3D%0A)
 
 Once enabled, eligible users will see the discovery options above. Users still need to install and set up the required apps and extensions themselves.
 
diff --git a/content/support/16607638-understanding-your-pro-or-max-plan-invoices.md b/content/support/16607638-understanding-your-pro-or-max-plan-invoices.md
index dc770395fa..968e64a2db 100644
--- a/content/support/16607638-understanding-your-pro-or-max-plan-invoices.md
+++ b/content/support/16607638-understanding-your-pro-or-max-plan-invoices.md
@@ -40,7 +40,7 @@ You can also open any invoice from your account:
 
 **Amount due.** The invoice total minus any applied balance. This is what your payment method was charged.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2629072970/c514f489b65072ccad08e803864f/e8c7a7de-905f-4a40-815f-c9c66edcdbf6?expires=1792852200&amp;signature=8bddca758c7651c2e41e9bd049ab4ea915ec25884216f9c51f29ccf5d5798454&amp;req=diYlH8l5n4hYWfMW1HO4zdWraRM361YcPZYKVlMiWEW8WfOEXXYNRorKpDU8%0ARIGiejWSAp85KW77SoM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2629072970/c514f489b65072ccad08e803864f/e8c7a7de-905f-4a40-815f-c9c66edcdbf6?expires=1792868400&amp;signature=d8e28b274ed14e31b3f3307d6d8d5b9e1b72e49586c2059db228a7469da6d8bc&amp;req=diYlH8l5n4hYWfMW1HO4zdWraRM36FwaPZYKVlMiWEVvmUtCqknibPT9VMpr%0ARVqvm2RaBFXCko3vDaA%3D%0A)
 
 ## Billing details on your invoice
 
diff --git a/content/support/16893491-get-started-with-smart-reports.md b/content/support/16893491-get-started-with-smart-reports.md
index 5ac44a70f9..f89122599a 100644
--- a/content/support/16893491-get-started-with-smart-reports.md
+++ b/content/support/16893491-get-started-with-smart-reports.md
@@ -28,13 +28,13 @@ Each report includes the following sections:
 
 Workstreams shows what the group used Claude for most, by sessions and by spend, side by side.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671030907/7b62b605189fe8e9474a20c1eaf2/image.png?expires=1792852200&amp;signature=e0e3812c5ccc62399fd527f746406b393a4e46fc84fa49e8da0c6f42b2d528d9&amp;req=diYgF8l9nYhfXvMW1HO4zZse%2BmCUTgoOVa%2FWhnGS4Gm7%2FGEel%2FG%2FqJNXLq0A%0AsJE7f5xofkcc%2FHaDmBY%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671030907/7b62b605189fe8e9474a20c1eaf2/image.png?expires=1792868400&amp;signature=47d5f948cd975b6a1c9cde916ff97ab55a8681466df62f21681214aeaf000d33&amp;req=diYgF8l9nYhfXvMW1HO4zZse%2BmCUTQAIVa%2FWhnGS4GnG%2BeLzg9tImRFpCCbI%0A%2BF4625b6hFMcSw%2FAWZ4%3D%0A)
 
 ### Deliverables produced
 
 Deliverables produced groups sessions by the type of output that was produced. For example, analysis, documentation, content drafts, and code.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671035220/2a582bc047a6ba46e7dbd6f05d9f/e17881ac-874c-4747-94ca-8679e0301455?expires=1792852200&amp;signature=5444b548521298657397d867dc3dc1b0d23fdae13106441c7900e8cff3054cb2&amp;req=diYgF8l9mINdWfMW1HO4zelj06VTlt%2FwYDEFlKbF9Y%2FCARjP2Z9MBXYDmLkI%0A8T%2FQ3OxfK80g%2F%2BeEzLM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671035220/2a582bc047a6ba46e7dbd6f05d9f/e17881ac-874c-4747-94ca-8679e0301455?expires=1792868400&amp;signature=a7320f6331389b2f3f6d2935bcefcdca0794cb5c49b6328e055377a676a35e8a&amp;req=diYgF8l9mINdWfMW1HO4zelj06VTldX2YDEFlKbF9Y%2FjUBMu2MJJlGaSthts%0AiasS57454ZtaVT8PFtA%3D%0A)
 
 ### Cost per session by type of output
 
@@ -48,17 +48,17 @@ Task outcomes  shows what each session produced.
 
 Most common frictions shows what got in the way, by category. For example, a connector that wasn’t set up, output that didn’t match the ask, approval or sign-in gating, tool failures, or rework loops.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671052365/b69f22b75729e5587563e7ab6830/b1647659-a7ea-403b-89fc-0b150ee97675?expires=1792852200&amp;signature=a26c067114f73ff77b6ed62e2a78fcb4c36f6ecd928e8b6a24e6790685f41571&amp;req=diYgF8l7n4JZXPMW1HO4zdDitrg9Ud9TjFK5P3Uf7Rg2I3zz74zOdfihsZRm%0AE9yrGuojQlxaE6IRtL0%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671052365/b69f22b75729e5587563e7ab6830/b1647659-a7ea-403b-89fc-0b150ee97675?expires=1792868400&amp;signature=7a31fafa225276c4900741e160e7e7db8cb117a429bfbe78160df61a4b4044a1&amp;req=diYgF8l7n4JZXPMW1HO4zdDitrg9UtVVjFK5P3Uf7RgfDXnFVjdhAjDFQw67%0ARpwSMDZf3rGwscBTuJY%3D%0A)
 
 Click into a category to see more information:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671053199/b68936dd5d590c5fbcbbc092b332/5ec247b2-cd67-4f3f-97b5-23479b87a5c6?expires=1792852200&amp;signature=cf5e3c24e88c18351ef44a03febde6cc9325b02bf7835963f43aef35b3cd2c2b&amp;req=diYgF8l7noBWUPMW1HO4zbuGO4kgI7seodOVMLl17PW%2FvRIVtRjbceVNAb9H%0AyXLXwyRMvCRcbdWmE5E%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671053199/b68936dd5d590c5fbcbbc092b332/5ec247b2-cd67-4f3f-97b5-23479b87a5c6?expires=1792868400&amp;signature=bd0929faa36e9a7be70ae0344f7fd163733c0abb3b7a3017771d0c7e37cd6046&amp;req=diYgF8l7noBWUPMW1HO4zbuGO4kgILEYodOVMLl17PX2BxVnxKcTnJD5AGvs%0AR9rxbAerTwXfv8EXsfQ%3D%0A)
 
 ### Inefficiencies
 
 Inefficiencies counts sessions that produced nothing usable and sessions that were personal or off-topic, with their cost (shown only as an aggregate count and cost, with no summaries or drilldown).
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671036122/90dc848a7adf371a872bd89a2f5e/de86945b-ccfe-4e0f-892d-abacc475c5c4?expires=1792852200&amp;signature=d201b6126470d769eb7b34d6e258364546ed2568418b99ca7297588053d98945&amp;req=diYgF8l9m4BdW%2FMW1HO4zcYfhg2eCPYYBas8rgXn%2Fb19vFcHVsH52X1Rqj1x%0Adkc8qylQTwRnlapOdxE%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671036122/90dc848a7adf371a872bd89a2f5e/de86945b-ccfe-4e0f-892d-abacc475c5c4?expires=1792868400&amp;signature=340cad1d9ae5ff890580c1bc14d860d3c5645ebfac570924054a0b97416a9fc7&amp;req=diYgF8l9m4BdW%2FMW1HO4zcYfhg2eC%2FweBas8rgXn%2Fb2iQF8wi7NtgT%2BpeVpX%0AVI1MjamNxMrEv0iMJjM%3D%0A)
 
 ### Reusable skills and workflows to build
 
@@ -68,13 +68,13 @@ Reusable skills and workflows to build identifies repeated patterns that could b
 
 Most expensive sessions lists where spend concentrates.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671032083/2b075387a4a3473f884a8ba26436/image.png?expires=1792852200&amp;signature=f8e83b6805a9a280c8fef1cbaabdaa3606c607d8e450b09a89c5a0bc8143cfc5&amp;req=diYgF8l9n4FXWvMW1HO4zdLkIm2t70QrnUoxuhUXEhgYlkavGp8Nz9Qr2fTe%0AyqhZv4MOvM0Y2kSjKLM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671032083/2b075387a4a3473f884a8ba26436/image.png?expires=1792868400&amp;signature=03cbf5beb7785e40a5750e2dc7df60df9f678f4d21de8ae18720b2712590752b&amp;req=diYgF8l9n4FXWvMW1HO4zdLkIm2t7E4tnUoxuhUXEhhUyCpG%2FXEiBbD9rckz%0AVA3%2FYgCN0Hj%2FZqwa2hQ%3D%0A)
 
 ### Complex, autonomous work
 
 Complex, autonomous work shows  sessions scoring highest on task complexity, time saved, how long Claude worked on its own, and the expertise required.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671031695/3781b98c5cb9cdc069439aa3d9ab/image.png?expires=1792852200&amp;signature=59d20ba06bd75141d6bc8eb5317d979bafa29c79f8bb28d7006a9bda45bc1658&amp;req=diYgF8l9nIdWXPMW1HO4zcPtgjD5Dt3GtjDEKfEvx0OuiNt%2BjDfos3MbL%2B5a%0Ap5LT3w2ldyfMJUHEMQg%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2671031695/3781b98c5cb9cdc069439aa3d9ab/image.png?expires=1792868400&amp;signature=ddf7234a15b9d6761d154b9bb8257fe66e13583b1fb57fc532cd79a426ae5ae8&amp;req=diYgF8l9nIdWXPMW1HO4zcPtgjD5DdfAtjDEKfEvx0OPMo%2B86PpY04igDjII%0Afd7v2AFXVj9xPCPH1f0%3D%0A)
 
 ### Answers to custom questions
 
diff --git a/content/support/16951679-use-claude-in-google-docs-sheets-and-slides.md b/content/support/16951679-use-claude-in-google-docs-sheets-and-slides.md
index 19b1d773ff..24e0a01106 100644
--- a/content/support/16951679-use-claude-in-google-docs-sheets-and-slides.md
+++ b/content/support/16951679-use-claude-in-google-docs-sheets-and-slides.md
@@ -28,11 +28,11 @@ If your organization already allows Marketplace apps, this takes about two minut
 
 2. Open a Google Docs, Sheets, or Slides file and go to Extensions > Claude > “Open Claude":
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2707281468/abc0497defca04936c9a4b97d147/8b17d05f-3fb1-4e49-8d1f-65364ac3f496?expires=1792852200&amp;signature=df0cb9de346a647d6c76c7a763f7ab1b6920cfe520c140ad39368de2f77cc1e1&amp;req=dicnEct2nIVZUfMW1HO4zRwmJT5kUeZNaAKM49NdBLOD23TumC8iOhgMnxYD%0A02Hi%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2707281468/abc0497defca04936c9a4b97d147/8b17d05f-3fb1-4e49-8d1f-65364ac3f496?expires=1792868400&amp;signature=e8f61882220000d280e7f676a0ae593bdb93aaa025809bb2b96942a0801dfd26&amp;req=dicnEct2nIVZUfMW1HO4zRwmJT5kUuxLaAKM49NdBLO8io73lZWtO6aIVaDs%0APy68%0A)
 
 3. The first time, Google asks you to allow two permissions. Review them and click "Allow":
 
-  ![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2707282342/f583a396098ff16e3cbd156d4a2a/112c6459-79c6-4fbb-9bc0-748fda6f592f?expires=1792852200&amp;signature=8b9f91df2f2be7ca2ceb4384ab51170b5cceae8debc62d44cb8c2ccc40e05382&amp;req=dicnEct2n4JbW%2FMW1HO4zeKY3p4OhQzyeBfHlrCfDWfqJKPYL5g8T5BPiR2J%0AQ1F%2B%0A)
+  ![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2707282342/f583a396098ff16e3cbd156d4a2a/112c6459-79c6-4fbb-9bc0-748fda6f592f?expires=1792868400&amp;signature=dac0aeb79d40dd7e960562ea84f241a51450bf2c80c68da94a31d03046c43bf4&amp;req=dicnEct2n4JbW%2FMW1HO4zeKY3p4Ohgb0eBfHlrCfDWeM9nKBz4QD7DH90bJ9%0AFdpv%0A)
 
 4. Sign in with your Claude account in the sidebar, and optionally enable your connectors.
 
diff --git a/content/support/17005973-manage-pooled-group-budgets-on-enterprise-plans.md b/content/support/17005973-manage-pooled-group-budgets-on-enterprise-plans.md
index 6f4b224d03..d0f50d57e4 100644
--- a/content/support/17005973-manage-pooled-group-budgets-on-enterprise-plans.md
+++ b/content/support/17005973-manage-pooled-group-budgets-on-enterprise-plans.md
@@ -76,7 +76,7 @@ If a user belongs to more than one group with a pooled budget, the largest poole
 
 With a custom order, the first pooled budget in your list with budget remaining pays.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2719736736/a4ec8e92af4975a87891357e5dbd/6f58b496-432d-4069-ba18-72a6390ab2ea?expires=1792852200&amp;signature=2b8fab2fb0824e805fc86773dab519ba7ad873b9fd5fc42a701ed9685de74db2&amp;req=dicmH859m4ZcX%2FMW1HO4zU9wBwYQVIoxTLR6JppsyjR4vswUVg0lXsZWZpxv%0AbIU%2FwrB5o4qPQVvIAeU%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2719736736/a4ec8e92af4975a87891357e5dbd/6f58b496-432d-4069-ba18-72a6390ab2ea?expires=1792868400&amp;signature=78dd19770ec0648f20443e28a820201717d1bbd39f9f2d9144197dc3ab09e0d9&amp;req=dicmH859m4ZcX%2FMW1HO4zU9wBwYQV4A3TLR6JppsyjTw6hKKvrktRftp3YTm%0AoMCqs2bhsnh2sxL%2BjyE%3D%0A)
 
 **Note:** Budget priority only decides the order in which pooled budgets pay. To choose which group's member monthly limit applies to a user in more than one group, use the **Member limit from groups** setting under **Spending defaults**.
 
diff --git a/content/support/17203415-set-up-claude-for-intune.md b/content/support/17203415-set-up-claude-for-intune.md
index 019997547b..cf087fdf2d 100644
--- a/content/support/17203415-set-up-claude-for-intune.md
+++ b/content/support/17203415-set-up-claude-for-intune.md
@@ -70,25 +70,25 @@ To add Claude for Intune for enrolled company-owned devices:
 
 1. In the Microsoft Intune admin center, select "Apps" from the left side navigation panel:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700192269/ce2bf95a18aba11042da50f4c1ad/dda0f9a2-d585-4b09-ae4f-a1ff70b1e010?expires=1792852200&amp;signature=790bf2131b48ef8029a18b06971e5eb89df8bd197c04e22da1614abf3cce67d0&amp;req=dicnFsh3n4NZUPMW1HO4ze7khjPZ52liAMLV2Uu0R4X2V7ENeY%2FLA4f2Yrtg%0A87Wp%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700192269/ce2bf95a18aba11042da50f4c1ad/dda0f9a2-d585-4b09-ae4f-a1ff70b1e010?expires=1792868400&amp;signature=caa86f8f0e7565db24d6c03905b7c87f6104ecda66dba36ab489175e257be1bc&amp;req=dicnFsh3n4NZUPMW1HO4ze7khjPZ5GNkAMLV2Uu0R4W6egoI1O9oA8vsagMZ%0A5%2FyG%0A)
 
 2. Under Platforms, select "iOS/iPadOS":
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700195036/b70c6c0bdeff5f2b72568ef4943b/67cc834c-5e91-42da-9d3b-1f32c8dd8c05?expires=1792852200&amp;signature=354296821b16bb0b029b8a1fe0bd1dbc63086f6dce9b3af9f3d896e2717e5d84&amp;req=dicnFsh3mIFcX%2FMW1HO4zeH1oU%2FvtHGWQ7hR7Wh%2Bi70xtSXCzs7lEbnHu6j%2F%0AV2%2F6%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700195036/b70c6c0bdeff5f2b72568ef4943b/67cc834c-5e91-42da-9d3b-1f32c8dd8c05?expires=1792868400&amp;signature=95bb3a58da24432d74aafed4bc3f8b585fa2e200f588725185285ca56cf4af77&amp;req=dicnFsh3mIFcX%2FMW1HO4zeH1oU%2Fvt3uQQ7hR7Wh%2Bi71IIuVT78HykUFycmM0%0AKVmv%0A)
 
 3. Click "+ Create." For the App type, select the "iOS store app," and click the "Select" button on the bottom:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700195791/9a01290b4189e6a39c473af0a448/cfed06da-f35a-4b22-b687-286ea48864c1?expires=1792852200&amp;signature=d322a14782da2e93a9f2b34439ede4ed908d8307974dbe565c12a3589afcd49c&amp;req=dicnFsh3mIZWWPMW1HO4zTni3cQhZ5wu2SRx6amjj9Hf%2F4VSxEh3v13aT1sg%0AMejc%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700195791/9a01290b4189e6a39c473af0a448/cfed06da-f35a-4b22-b687-286ea48864c1?expires=1792868400&amp;signature=a9cf16370e6bbb458d24b87e768e6bbb81bea939405fb5e48e3ceb34dc693a88&amp;req=dicnFsh3mIZWWPMW1HO4zTni3cQhZJYo2SRx6amjj9Fukcw2K%2BEhokrEhT%2Bh%0AR4JB%0A)
 
 4. Search "Claude for Intune" and click the "Select" button on the bottom.
 
 5. In **App Information**, set **Minimum operating system** to iOS 18, then click the "Next" button:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700196458/588327ab209e9524c45111a244a1/258697c2-2f82-471b-9104-2bccb1b01614?expires=1792852200&amp;signature=91379977b27354dfa9a1b0b2ecb7d015c2878e168317d5f91efe86f127a37092&amp;req=dicnFsh3m4VaUfMW1HO4zbxl5YpfcjAsDNNSLAHCCFqOSDwyRDU5Rub0L%2BHG%0AU1XX%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700196458/588327ab209e9524c45111a244a1/258697c2-2f82-471b-9104-2bccb1b01614?expires=1792868400&amp;signature=d781b7274d856f574da63c451deb5b5739fb2f41ace6b455b44472c2271e37ca&amp;req=dicnFsh3m4VaUfMW1HO4zbxl5YpfcToqDNNSLAHCCFoom89SPiUCLrEE39PU%0Av3EM%0A)
 
 6. For **Assignments**, add the groups that should get the app: under Required to install it automatically, or under Available for enrolled devices so employees can install it from Company Portal. You can use user groups or device groups.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2741107114/8f15b0d179a54c2ca4effaad8577/55bed25a-4b20-47b0-9e89-7f8adc86c04f?expires=1792852200&amp;signature=2b62aa2f03069a2a0731197873f1d4aebd6675117b38ff700626f047e8794708&amp;req=dicjF8h%2BmoBeXfMW1HO4zYaZMeq0fPGcmN%2B6UXepdg%2BjgkrKvH4gr1v1qpXD%0AlK1S%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2741107114/8f15b0d179a54c2ca4effaad8577/55bed25a-4b20-47b0-9e89-7f8adc86c04f?expires=1792868400&amp;signature=365f7e31ed4e2b785298a13332cbc92ac1b6057d977f602ba442b12bb03e3aef&amp;req=dicjF8h%2BmoBeXfMW1HO4zYaZMeq0f%2FuamN%2B6UXepdg%2BLZ%2FAlFyRV7DVFRAqm%0AWuAb%0A)
 
 7. Click "Next," review and create.
 
@@ -98,27 +98,27 @@ To add Claude for Intune for enrolled company-owned devices:
 
 1. In the Microsoft Intune admin center, select "Apps" from the left side navigation panel:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700190760/9f6412fe68632cffee29826f7d30/42fdeb30-64af-4089-a976-5094bb6b8292?expires=1792852200&amp;signature=6207829ddadbf66b4f64063408d41f530d1c3693ceb991cc330e6c6bcd124907&amp;req=dicnFsh3nYZZWfMW1HO4zQwrZIgKVtA%2BLtTCoSp4D6psQL57yFIYqeH0%2BuE0%0AgRoo%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700190760/9f6412fe68632cffee29826f7d30/42fdeb30-64af-4089-a976-5094bb6b8292?expires=1792868400&amp;signature=258286096713bfbdf7683816f1ff55d53e2108acbdabf2e2d463b0c7e7fe0838&amp;req=dicnFsh3nYZZWfMW1HO4zQwrZIgKVdo4LtTCoSp4D6p5XUVDN2sNzPLkc5r6%0A3Ij5%0A)
 
 2. Under **Manage apps**, select "Protection":
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700200858/a7ddd4265aeb6d61a7a096297cd5/fc9a1fe2-3d0e-4038-9b2c-f96bd19e4020?expires=1792852200&amp;signature=d8630a938280bdd8effa10127b3524c5bc6b1ba2cc1898c7c400006945627c20&amp;req=dicnFst%2BnYlaUfMW1HO4zeBHXB018P%2FvnJWY0xu8hzI6w7D5p0O34JYTGqqt%0AGFR3%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700200858/a7ddd4265aeb6d61a7a096297cd5/fc9a1fe2-3d0e-4038-9b2c-f96bd19e4020?expires=1792868400&amp;signature=b590a8ca77905bcce0ce81d2024bc49bd2ab1358ef834d698877cc3de918fe38&amp;req=dicnFst%2BnYlaUfMW1HO4zeBHXB018%2FXpnJWY0xu8hzKAnLi2R2C0S0GPymMz%0Avu47%0A)
 
 3. Click "+ Create" and then select "iOS/iPadOS":
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700201382/6240e257b2b498b5fa5ac1111561/11ef4f59-aba1-4d2b-ac58-9aec1dd60a4d?expires=1792852200&amp;signature=0c20e8a945df5abc42c4f1188bd07927f730432c0148c6fd20eacaab9fa2a143&amp;req=dicnFst%2BnIJXW%2FMW1HO4zc89y0leB3hMV2VWh%2B9zzEoXUDv92IxKbeox8xkk%0AUmAH%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700201382/6240e257b2b498b5fa5ac1111561/11ef4f59-aba1-4d2b-ac58-9aec1dd60a4d?expires=1792868400&amp;signature=212aaca11eabc0ad2c83edbc413d76e08eb0b95c069adb4ea74d91aef6d1fc2d&amp;req=dicnFst%2BnIJXW%2FMW1HO4zc89y0leBHJKV2VWh%2B9zzErhJgAMlBZ%2FlmPTuVRF%0AEGVU%0A)
 
 4. Enter Name in the **Basics** tab, then click "Next" to **Apps**. Set **Target policy to** "Selected apps." Click "+ Select custom apps":
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700201929/2edf45cedc0bc03204f86d01a49e/4d96c12d-962b-43f6-8b3f-668e3247d4c1?expires=1792852200&amp;signature=b6527cd0511bbc582ca26323241af119bb85239c5f756656b6ddaa2b33e97091&amp;req=dicnFst%2BnIhdUPMW1HO4zVmMRJMcVj8KKETwku7gMstKQ6PBri7otLJ31wyC%0AMO3y%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700201929/2edf45cedc0bc03204f86d01a49e/4d96c12d-962b-43f6-8b3f-668e3247d4c1?expires=1792868400&amp;signature=c4e7f989f377be14d2b63c5e1cef21157634b315539a08422f91bb05b88f4159&amp;req=dicnFst%2BnIhdUPMW1HO4zVmMRJMcVTUMKETwku7gMss8r%2B4H8Q9ugNYQt0bA%0Aptmi%0A)
 
 5. Type in the bundle ID `com.anthropic.claudeforintune`. Select it so it appears under **Selected Apps** before clicking "Select":
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700202816/3565aea2d1b9c22a5f8d105825c5/3de6d241-6259-463e-a503-a6ca9f2095e0?expires=1792852200&amp;signature=310afef1827f8ac87aa31940df04b204a3641fda0da6498c7d04ed09512006aa&amp;req=dicnFst%2Bn4leX%2FMW1HO4zf6tYiEgzah112LT9vQL0W6gDGnPzq0%2BPzQ5JzjA%0AH9m%2B%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700202816/3565aea2d1b9c22a5f8d105825c5/3de6d241-6259-463e-a503-a6ca9f2095e0?expires=1792868400&amp;signature=a8abe646c5b99e9a1ecb885ddac4b05cef9fc917f00c5b20bc2ebc2ca7cfb35f&amp;req=dicnFst%2Bn4leX%2FMW1HO4zf6tYiEgzqJz12LT9vQL0W5wT%2BiOs4f3C5L9IJ2m%0AIzHf%0A)
 
 6. In Apps, confirm the bundle ID now appears under **Custom apps** before clicking "Next":
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700203780/24ed354ef0de87bf0a0c1bc129a1/46eed662-f488-48ee-a4d1-8a9a76079884?expires=1792852200&amp;signature=78dedc5cfa7bb441e0623d97b977c63521b6372d21b68d53c9ac55ec80dcd977&amp;req=dicnFst%2BnoZXWfMW1HO4zQd95NeC3srd8F6Cfy2R7u80pJjD57sz1AzVJ2e%2F%0Ax65U%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2700203780/24ed354ef0de87bf0a0c1bc129a1/46eed662-f488-48ee-a4d1-8a9a76079884?expires=1792868400&amp;signature=578d574673cf3e852fc020ab7de7b58984b4789efb2b089ef20a23135834f7df&amp;req=dicnFst%2BnoZXWfMW1HO4zQd95NeC3cDb8F6Cfy2R7u%2BGGoGGRu5Dvx7H826P%0AgTcv%0A)
 
 7. Configure the Data protection, Access requirements, and Conditional launch settings as needed.
 
diff --git a/content/support/8114491-get-started-with-claude.md b/content/support/8114491-get-started-with-claude.md
index 4f0d8d567f..f3793949ba 100644
--- a/content/support/8114491-get-started-with-claude.md
+++ b/content/support/8114491-get-started-with-claude.md
@@ -36,7 +36,7 @@ You use **prompts** to communicate with Claude. The best approach is to speak to
 
 Type your prompt into the chat interface and click the submit button to start a conversation with Claude. You can click the "+" button in the lower left or type "/" to view additional options and commands:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1916208578/2cf2ea52f1f884084b57983a8805/image.png?expires=1792852200&amp;signature=5bd7523353f474ccb9b84a426f6b1d840f65aba1f2e5428b1cc70208dd4f4be6&amp;req=dSkmEMt%2BlYRYUfMW1HO4zV2J7C3CsYWD9crMELaMZPyw0LCP7tDvg0la1uLZ%0AWEJkXH6IR4NxIKEvWF8%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1916208578/2cf2ea52f1f884084b57983a8805/image.png?expires=1792868400&amp;signature=5eddd50d8c55a22334f169120ed52ddfd14b584107d819fd211f64c6b3b95a08&amp;req=dSkmEMt%2BlYRYUfMW1HO4zV2J7C3Cso%2BF9crMELaMZPwa7tKx%2BuGdLaM996DS%0A6%2FGoVLLBfFqKCCDCEc8%3D%0A)
 
 ---
 
diff --git a/content/support/8230524-delete-or-rename-a-conversation.md b/content/support/8230524-delete-or-rename-a-conversation.md
index 711c44f1f6..d73e1044e0 100644
--- a/content/support/8230524-delete-or-rename-a-conversation.md
+++ b/content/support/8230524-delete-or-rename-a-conversation.md
@@ -44,15 +44,15 @@ These steps apply to Claude for iOS, listed on the App Store as Claude by Anthro
 
 4. If deleting, tap "Delete" again in the confirmation prompt.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599501318/75c28edc693efbe8befd21e4da64/d18a921a-df4b-4788-833c-12c966a32527?expires=1792852200&amp;signature=ad7332b07239212475f525995d14ce4da832fda21996bc578ed85031d3c0fd1f&amp;req=diUuH8x%2BnIJeUfMW1HO4zSc12KxSjWKp1DBI29QsIlEmB89X7BlR4Zmx29h8%0Ajt7MUbSixhBKHltRtM8%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599501318/75c28edc693efbe8befd21e4da64/d18a921a-df4b-4788-833c-12c966a32527?expires=1792868400&amp;signature=0d9bb7b1772a6467aedc2b1c1f1fbac77822d559d5f7fc52ca9c40db97b13df4&amp;req=diUuH8x%2BnIJeUfMW1HO4zSc12KxSjmiv1DBI29QsIlGQDxSWh1PdHI5KRv94%0A3U2kofcLNHC3HYaEjgQ%3D%0A)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493852/2e58b92d18f307bb79ae30650f26/1bbe52f3-202b-4d5d-9f9a-eeda4d6952c3?expires=1792852200&amp;signature=b3fdd3c277b3bd97a92ea59bdd90fbd4e3faff4322d7b01b93889200f7b4f290&amp;req=diUuH813nolaW%2FMW1HO4zTjXM%2BWEK8Lnj7blKEDtUI0vl7O5BhZ9E3hntugk%0AxvRLtuJSr3S5v4gJuco%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493852/2e58b92d18f307bb79ae30650f26/1bbe52f3-202b-4d5d-9f9a-eeda4d6952c3?expires=1792868400&amp;signature=34c1f7ba983820733e6ced7d41606fa756345a26a82cdadccc5828255bcfb617&amp;req=diUuH813nolaW%2FMW1HO4zTjXM%2BWEKMjhj7blKEDtUI2k3ahwiSYJEjkdtjhB%0AA5cgpT2uaV%2B0JVAWKNU%3D%0A)
 
 You can also delete the conversation you have open: tap the "⋯" button in the top right corner, tap "Delete," then confirm.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493848/997184c386d0e6fb0bd2d7c1f2b6/5d2bc394-25fc-4814-8c2a-2f54d004f83f?expires=1792852200&amp;signature=13812c7c43fe9d1d1da16f087e35882c6aaaa680db0097613eee21f183a2efd1&amp;req=diUuH813nolbUfMW1HO4zVCIq5jHzt5EzQl%2BKgU984yQ5ImthmVPa3YPcaw8%0AIS%2BoBoBxFesTpExNWNg%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493848/997184c386d0e6fb0bd2d7c1f2b6/5d2bc394-25fc-4814-8c2a-2f54d004f83f?expires=1792868400&amp;signature=f974c8bb3d19227d3b58eade7ebdff9b9ac454f7ad698c5c4e78b30879289e47&amp;req=diUuH813nolbUfMW1HO4zVCIq5jHzdRCzQl%2BKgU984ypSnenimSyChTiThQp%0AUHZdLaNXwup0Fb714oQ%3D%0A)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493856/799041da9fa918e90068c5ebf5bd/2e8d5cee-c45a-41d7-a14b-486e50a37f88?expires=1792852200&amp;signature=8bf2d5c8445b4e146c629c7b40a354ba6b91579f0aa8bec960bba0c7eb822025&amp;req=diUuH813nolaX%2FMW1HO4zVCl4Qr61GdPEDIU8RT6jk0lDUfPiul03mZjMzkC%0A2c6OuYlZ2UAcK2Qjk34%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493856/799041da9fa918e90068c5ebf5bd/2e8d5cee-c45a-41d7-a14b-486e50a37f88?expires=1792868400&amp;signature=c641387ce7b6e20a3081e007269ee8e6835a09c1577ac9d24b73c63810e0ce20&amp;req=diUuH813nolaX%2FMW1HO4zVCl4Qr6121JEDIU8RT6jk0EcPcQi587zuvSs3P3%0A4xKRqSBLuMyQz6IjKZE%3D%0A)
 
 ## Delete or rename a conversation on Claude for Android
 
@@ -66,9 +66,9 @@ These steps apply to the Claude for Android, listed on Google Play as Claude by
 
 3. If deleting, tap "Delete" again in the confirmation prompt.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493850/a64e6561222d535f2f5bd03e71f0/5de429c2-d8ed-4e8a-89e8-a13ccaa49767?expires=1792852200&amp;signature=aec67468b9b4940c409a914b5bf7fee7fcdf2de6575e85289d7f50d013b3d556&amp;req=diUuH813nolaWfMW1HO4zVTddtAkx1J3rqtc0YNNUtJwDvCS07kfjEx7cORd%0AEgbawfYO4V6QsdvjGNw%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493850/a64e6561222d535f2f5bd03e71f0/5de429c2-d8ed-4e8a-89e8-a13ccaa49767?expires=1792868400&amp;signature=1cee3d6782b50811bc32af372b0a9ad183298e505b5ab4b724ecebc48db585c6&amp;req=diUuH813nolaWfMW1HO4zVTddtAkxFhxrqtc0YNNUtKsupcmwPzjvd15gde3%0A40G9fphNZP5Z9wxH2Us%3D%0A)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493851/f21b39c60e88050d4b0745325f0d/0a8c0d08-dc53-4ef1-8d9f-2b995242c1f9?expires=1792852200&amp;signature=6d9b77499ddb2178390bf6681690c668e03641b91ca8abbf8aa832c993bd3fcc&amp;req=diUuH813nolaWPMW1HO4zUYvwlcDpzxe%2FjekULCQNzWB5HyHTZp%2BWm6veUHu%0AnVQq%2B4OFHwraSfr9vjw%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493851/f21b39c60e88050d4b0745325f0d/0a8c0d08-dc53-4ef1-8d9f-2b995242c1f9?expires=1792868400&amp;signature=f34c9ec1336d7f56f8e4e271e646e6003a14298d67a424e4d4dabb4d510093cf&amp;req=diUuH813nolaWPMW1HO4zUYvwlcDpDZY%2FjekULCQNzXcLKF%2F%2BFsQgTGsfkD4%0A8ShgvsoUSDrK6wO53xI%3D%0A)
 
 **To delete multiple conversations at once:**
 
@@ -78,9 +78,9 @@ These steps apply to the Claude for Android, listed on Google Play as Claude by
 
 3. Tap the trash icon, then tap "Delete" in the confirmation prompt.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493849/3013a0ab921337b4544f7ffeffa6/e828ec14-fb52-4205-a840-707b6f2a848d?expires=1792852200&amp;signature=02468f76feb00a01d1a71edce43360aa72710de9e2356108d2002af3b8098899&amp;req=diUuH813nolbUPMW1HO4zWGamcV8f4%2Fd4AqhTnZa84Xk2%2FWtIrJ5mIm92Pai%0Axl1fM35Ts984h%2FpXEM8%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493849/3013a0ab921337b4544f7ffeffa6/e828ec14-fb52-4205-a840-707b6f2a848d?expires=1792868400&amp;signature=b8f6565f5912a0cd9573080638006177da13f0ad97ced76431e8c7db60b51d1f&amp;req=diUuH813nolbUPMW1HO4zWGamcV8fIXb4AqhTnZa84Uksk0MuYdr0AkQ5FTc%0AiRUUcRqCNOJ1Rwlpkrw%3D%0A)
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493853/e2507f53cce8a26776a22a457b1a/bd79bb8a-b078-420f-a4e1-75590367aa80?expires=1792852200&amp;signature=3ec6f64f68c609d593b8abf42627b07671ee63ad9864bf49667d87edced5086b&amp;req=diUuH813nolaWvMW1HO4zQTtEhf5wUI6SBGfF3I2bRjCOos6FOiv%2BYyH8uqw%0ATIluj9oyx3S%2FA4tje8I%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2599493853/e2507f53cce8a26776a22a457b1a/bd79bb8a-b078-420f-a4e1-75590367aa80?expires=1792868400&amp;signature=161f7db68f691abbf6f87ea801f83d1cd176cc0b7268bb3eaa9d2278e724aac0&amp;req=diUuH813nolaWvMW1HO4zQTtEhf5wkg8SBGfF3I2bRi4SRddhLkzLXqNOJqG%0ABu5Iqs44VZPaGSJXA2g%3D%0A)
 
 ## What happens when you delete a conversation
 
diff --git a/content/support/8325618-paid-plan-billing-faqs.md b/content/support/8325618-paid-plan-billing-faqs.md
index fcb367f603..8e16b74c3a 100644
--- a/content/support/8325618-paid-plan-billing-faqs.md
+++ b/content/support/8325618-paid-plan-billing-faqs.md
@@ -50,7 +50,7 @@ There's no separate option to remove a card, and updating to a new card replaces
 
 If you want to use a name other than the one tied to your payment method, check the "Use a different name on invoices" box when adding or updating your payment method in **[Settings > Billing](https://claude.ai/settings/billing)**.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1922141785/666191101c11030b05f03a668a74/image.png?expires=1792852200&amp;signature=4aa491ffa72166791ab35423ca5220b6058e3055305d1c7b08d454ad98d2f2bb&amp;req=dSklFMh6nIZXXPMW1HO4zVXW8W%2BjbjHOQoNvNFTb5cekzPPnTd58g3IIaMKb%0AojvS5StMBrhc7d3jdj4%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1922141785/666191101c11030b05f03a668a74/image.png?expires=1792868400&amp;signature=d5a8d5b7804931d3be8369fcb1a4d18969eadb941249d487eff78a19e5234388&amp;req=dSklFMh6nIZXXPMW1HO4zVXW8W%2BjbTvIQoNvNFTb5cffm%2BqnyLW2LS8nHfr%2B%0AfjST8zv8R%2B6n6ENoLnc%3D%0A)
 
 ## How can I edit a paid invoice?
 
diff --git a/content/support/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization.md b/content/support/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization.md
index 9ff4f973e0..30d3ed4829 100644
--- a/content/support/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization.md
+++ b/content/support/9267400-move-your-personal-claude-account-to-a-team-or-enterprise-organization.md
@@ -132,7 +132,7 @@ For the full walkthrough of your options, deadlines, and what happens to your su
 
 You may have both a personal account and an organization account tied to the same email address. You can switch between them by clicking your initials or name in the lower left corner of the screen.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312193347/712f763fc290b2488c103849f20c/0c135a6f-3442-4ee1-9ab7-98673f03ef6e?expires=1792852200&amp;signature=3154e9d2a5ddba235cf3c48c0f15e68f730b29c684b4dd905d4e5c9c54f4af18&amp;req=diMmFMh3noJbXvMW1HO4zXhPnNI%2BzR1jufhmlOXMdYaPhA3AivK1iLz9M8y6%0AZAfB8YCKycWESGDFwqI%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/2312193347/712f763fc290b2488c103849f20c/0c135a6f-3442-4ee1-9ab7-98673f03ef6e?expires=1792868400&amp;signature=f17f773f1a56123b39dbc44da547f3eb6d363d17cbd1e504b2b299bde5a8b2ca&amp;req=diMmFMh3noJbXvMW1HO4zXhPnNI%2BzhdlufhmlOXMdYa3m%2F48qEd0PSN2PiNV%0ADk4LDzxjmZUxgadopNM%3D%0A)
 
 A blue checkmark shows which account you're currently using. Click the other account to switch to it and access its separate conversations and projects.
 
diff --git a/content/support/9519177-how-can-i-create-and-manage-projects.md b/content/support/9519177-how-can-i-create-and-manage-projects.md
index b220a8eda7..9643a58efb 100644
--- a/content/support/9519177-how-can-i-create-and-manage-projects.md
+++ b/content/support/9519177-how-can-i-create-and-manage-projects.md
@@ -104,15 +104,15 @@ Starring a project allows for quick access from your projects and chats list, vi
 
 You can move a standalone chat into a project by clicking on the dropdown arrow next to the chat name, then “Add to project”:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1784190248/0f19c8de18b494a27be252fdfaff/d4e7a5c5-25f5-4623-862b-c593d2dc0b39?expires=1792852200&amp;signature=e8f7d5412e240580b74e2227afaf45189e92af3f740ba858434e037c2c9f3d32&amp;req=dScvEsh3nYNbUfMW1HO4zQABaGNkT6IXBSXNVFXQ%2FVG3AyeJUhGCAlo8N6uS%0A6nllsC6jdW3FyX%2Fj44U%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1784190248/0f19c8de18b494a27be252fdfaff/d4e7a5c5-25f5-4623-862b-c593d2dc0b39?expires=1792868400&amp;signature=38d3935d42b3944470cff7bf66a7ae167856c9676dceae844646f83989eec1a8&amp;req=dScvEsh3nYNbUfMW1HO4zQABaGNkTKgRBSXNVFXQ%2FVEW0%2FjJ5hN%2FHEag4Ukn%0A0fTgDy2KA9FhOWZ33JY%3D%0A)
 
 Browse or search for the correct project in the **Move chat** modal that appears, then click on it to move the chat.
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1784190951/34dc256ccd4c0cf74976f31062e6/55365cf2-059d-41b2-ac95-4b00c4389a76?expires=1792852200&amp;signature=69f2e4e9a08bae9151d13e1a129f905d04cbb21de924a262273b8730461bbd31&amp;req=dScvEsh3nYhaWPMW1HO4zSMECyK4zgsDgYbpTjViBxBqfX0XqaVr4Qg3Pm1K%0Aon0jqmtfX%2Bf2VqYoTQM%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1784190951/34dc256ccd4c0cf74976f31062e6/55365cf2-059d-41b2-ac95-4b00c4389a76?expires=1792868400&amp;signature=3a111092a80103d420a38d38ccfa4e5059dd24a0c26ff4643e01bb9d57866f48&amp;req=dScvEsh3nYhaWPMW1HO4zSMECyK4zQEFgYbpTjViBxCkEnIdC1b9kCRtLZYl%0A2Qd3cgAUaHQvGzccsnc%3D%0A)
 
 You can also remove chats from projects, or move them between projects, using the same dropdown menu within the chat:
 
-![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1784185682/8625eac15b9fa452f148a6c47250/c53a1bc4-a991-4684-a789-5447ed789d35?expires=1792852200&amp;signature=aa79f32d2d548e91112fe07dea481fda21cbc3461817189684ffa1e53ed2ceb5&amp;req=dScvEsh2mIdXW%2FMW1HO4zb6DufUkC0cIS2r1%2FGRlqOT1xuxWqCS8Z%2BHR4cnV%0AAKjFH4Dj6GCk%2BEY8Uqs%3D%0A)
+![](https://downloads.intercomcdn.com/i/o/lupk8zyo/1784185682/8625eac15b9fa452f148a6c47250/c53a1bc4-a991-4684-a789-5447ed789d35?expires=1792868400&amp;signature=1787859c267f348f6e11018e6702c2b416d25b240bd1f025f06404b0d5982902&amp;req=dScvEsh2mIdXW%2FMW1HO4zb6DufUkCE0OS2r1%2FGRlqOTfnZMJxCqwgHnoevMR%0AQ7QyPdBdlAImWJG64Rw%3D%0A)
 
 ---