Your VS Code Policy Can Switch Off Claude Chat, GitHub Works Across Repos in Slack, and Claude Code Stops Rerunning Failed Routines

At a glance

• An admin's sandbox or permissions policy can now take Claude and Codex chat out of VS Code.
• Admins can allow assisted approvals without allowing developers to approve everything.
• GitHub in Slack and Teams can handle several repositories in one thread.
• Claude Code routines that fail halfway no longer repeat themselves later.

This is a catch-up day: all three stories are Wednesday to Friday items the week left uncovered, and each is already in your editor, chat app or cloud sessions. Treat today as a settings and side effects check: ask whoever owns your VS Code managed settings whether a sandbox or permissions policy is on, try one cross repository request from Slack or Teams, and read the last run of each scheduled Claude Code routine.

Top Stories

1. VS Code v1.142 lets policy decide which harness your chats run in

VS Code v1.142 was released on Wednesday 14 October. When an organization configures a nonempty permissions object or sets sandbox.enabled to true in enterprise managed settings, VS Code now requires the Copilot harness in Agent Host for full chat sessions, because that is where it can enforce those policies. Opening an existing, unarchived Local chat moves it to Copilot and keeps the transcript and any unsent draft, including attachments. The notes say nothing is sent automatically.

The catch: while these policies apply, Claude, Codex and terminal chat are unavailable, and editor inline chat remains for limited read and edit tasks. An empty permissions object or a legacy policy alone does not trigger the move. Admins who need more time can set vscode.temporaryDefaultToLocalHarness to true in unified managed settings, though the notes warn that Local does not enforce the runtime only sandbox and permission rules.

The same release lets admins permit Assisted approvals while blocking Allow All, using permissions.disableBypassPermissionsMode and permissions.disableAssistedPermissionsMode; permissions.defaultMode only sets a starting mode. Assisted is not yet compatible with permissions.allow, permissions.ask or permissions.deny, so teams using those lists should set disableAssistedPermissionsMode to true until the next release.

Practical dev impact: If Claude or Codex chat disappeared from VS Code this week, in our view a managed policy is a likelier cause than a broken extension, so ask your admin before reinstalling. Our advice to admins is to warn developers before turning on a sandbox policy.

2. GitHub in Slack and Teams now spans repositories in one conversation

A GitHub Changelog post at 10:16 PM ET Thursday 15 October says @GitHub in Slack and Microsoft Teams now supports working across multiple repositories in a single conversation, for creating issues, opening pull requests and investigating bugs. GitHub's examples include filing an issue from a thread's context and investigating a bug using code from both frontend and backend repositories.

You can also mention @GitHub anywhere in a message, and in Slack it can use shared messages and threads as context.

Practical dev impact: A bug spanning two services no longer needs two chat threads. Because one thread can now open pull requests in several repositories, in our reading it is worth confirming which repositories your GitHub app installation can reach. The post says nothing about admin scoping, so that check is our suggestion.

3. Claude Code v2.1.302 stops repeating failed routines and refuses huge images

Saturday's brief covered the new defaults in Claude Code v2.1.302, which has held npm latest and next since 12:48 PM ET Friday 16 October and still did at our 5:54 AM ET check Sunday, with stable at v2.1.292. It also carries fixes that are easy to miss. In cloud sessions, a scheduled routine run that failed partway was being run again from the start an hour or more later, which the changelog says could repeat work such as posting the same report twice, and that is fixed. Routine runs whose cloud session stopped unexpectedly now show as failed instead of Completed, and a routine's page now carries a banner explaining why its last run did not start, such as your organization reaching its limit on concurrent cloud sessions.

Locally, the Read tool no longer loads an image file of any size, or a pipe or device named like an image, entirely into memory, and image sources over 128 MB are now refused. MCP servers that negotiate protocol version 2026-07-28 but omit resultType, ttlMs or cacheScope no longer show no tools, and Windows projects on exFAT or FAT32 drives no longer have every file write refused.

Practical dev impact: If a routine posted a duplicate report or claimed Completed on a run that never finished, this release explains it, and our advice is to review the past week of runs after updating. We would also have teams whose MCP servers went quiet after a protocol upgrade retest on v2.1.302 before filing a bug.

Practical Impact Analysis

All three stories changed quietly underneath work you already do, so in our view the Sunday move is checking settings and recent runs, not installing. VS Code v1.142 is the likeliest surprise, because a sandbox policy switched on for safety also changes which chat tools developers get. GitHub's change widens what one thread can touch. Claude Code v2.1.302 is a reasonable update for individuals from latest, while teams that prefer slower change can stay on stable at v2.1.292 and audit routine history instead.

Elsewhere, at our 5:54 AM ET check Sunday, no main npm pointer had moved since Saturday. Copilot CLI latest held at v1.0.98 with prerelease at v1.0.100-1 from 6:46 PM ET Friday, Codex latest held at v0.163.0 with alpha at v0.164.0-alpha.3 from 12:14 AM ET Saturday, and Gemini CLI held at v0.64.0 with preview at v0.65.0-preview.0. Friday's 9:31 PM ET Gemini nightly added a banner saying Gemini CLI is not optimized for Gemini 4, so far in nightlies only. Both Cursor changelogs, main and CLI, had nothing new at 5:54 AM ET Sunday. GitHub also lets Team and Enterprise Cloud admins download Code Quality license usage as a CSV, posted 4:11 PM ET Thursday.

Tutorial

We have not run this script end to end on every platform, so read it before you run it. It prints versions and changes nothing; installs and the admin example are comments only.

1. Run steps 1 to 3 and compare with this brief.
2. Uncomment one install line only to change channels.
3. Pass step 5 to whoever owns managed settings.
4. Try step 6 in Slack or Teams.

# We have not run this script end to end on every platform. Nothing below installs or changes anything unless you uncomment it.
# 1. VS Code build on this machine (v1.142 released Wed 14 Oct)
if command -v code; then code --version; else echo "VS Code CLI not on PATH"; fi

# 2. Claude Code channel pointers. At 5:54 AM ET Sun 18 Oct npm showed
#    stable v2.1.292, latest and next v2.1.302.
npm view @anthropic-ai/claude-code dist-tags --json

# 3. What this machine runs
if command -v claude; then claude --version; else echo "claude not on PATH"; fi

# 4a. Optional, Claude Code latest and next channel, npm installs only, at 5:54 AM ET Sun 18 Oct:
# npm install -g @anthropic-ai/claude-code@2.1.302

# 4b. Optional, Claude Code stable channel, npm installs only, at 5:54 AM ET Sun 18 Oct:
# npm install -g @anthropic-ai/claude-code@2.1.292

# 5. Admins only. VS Code v1.142 release notes example: Assisted on, Allow All off.
#    Not applied by us. A nonempty permissions object also moves full chats to
#    Copilot Agent Host. Skip it if you use permissions.allow, ask or deny.
# {
#   "permissions": {
#     "disableBypassPermissionsMode": "disable",
#     "disableAssistedPermissionsMode": false
#   }
# }

# 6. In Slack or Teams, try one of GitHub's own example prompts:
#    @GitHub Show me all my open PRs across repositories and highlight which ones need my attention.

Check routine history on each routine's page in cloud sessions. Do not mix npm and native installs of Claude Code on one machine.

Recommended AI prompt

Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use. You are my developer tooling lead for Sunday 18 October 2026. VS Code v1.142, released Wednesday 14 October, requires the Copilot harness in Agent Host for full chats when an organization sets a nonempty permissions object or sandbox.enabled to true, makes Claude, Codex and terminal chat unavailable while those policies apply, and offers vscode.temporaryDefaultToLocalHarness as a temporary opt out. @GitHub in Slack and Teams now works across multiple repositories in one conversation (GitHub Changelog, 10:16 PM ET Thursday 15 October). Claude Code v2.1.302, on npm latest and next since 12:48 PM ET Friday 16 October, stops rerunning failed routine runs from the start and marks unexpectedly stopped runs as failed. Ask me whether we manage VS Code centrally, which chat tools our developers use in it, whether we use GitHub in Slack or Teams, and whether we run scheduled Claude Code routines. Then give me a short Monday checklist to review our VS Code policy before it hides tools people rely on, scope the GitHub app's repository access, and audit last week's routine runs, and link me to the official release notes or changelog for each step instead of inventing names.