Gemini CLI's Nightly Makes Esc Finally Stop the Agent, Claude Code Quits Approving Plans You Meant to Push Back On, and Copilot in Visual Studio Reads Your Pull Requests

At a glance

• Gemini CLI's nightly build, and only its nightly build so far, makes Esc actually stop the agent and keeps its file writes in the repo you are working in.
• The same nightly adds a command that lists available models in a form scripts can read.
• Claude Code fixes a VS Code plan review button that approved your plan when you meant to send feedback, and lets Enterprise admins grant cloud sessions by role.
• Copilot in Visual Studio can now summarize a pull request and offer a fix for vulnerable NuGet packages.

Sunday sources are thin, and we will say it plainly: no new stable release has landed for Claude Code, Copilot CLI, Codex or Gemini CLI since Friday evening, so nothing below forces an upgrade on a stable channel today. What the week left behind is a set of fixes with one theme, the agent doing something other than what you told it.

Treat today as a control check day: find out whether your team runs Gemini CLI from a parent folder or a multi root workspace, update Claude Code in VS Code before your next plan review, and try the Visual Studio Git agent on one open pull request.

Top Stories

1. Gemini CLI's nightly makes Esc stop the agent and keeps writes in the right repo

The Gemini CLI v0.67.0 nightly published on GitHub at 9:15 PM ET Friday fixes a cancel bug that should worry anyone who treats Esc as a brake. According to the pull request, pressing Esc while the CLI was continuing after a batch of tools printed "Request cancelled." and then kept going anyway, nudging the model and running new shell commands such as git status. Cancellation now ends the turn.

A second fix matters for monorepos and for VS Code on WSL. In a multi root or parent folder IDE workspace, the write, edit and read tools could write to a sibling repository. Paths now resolve against the workspace, or the nested Git repository, that holds your active file. The nightly also adds gemini models and a --list-models flag that print model IDs, names and context limits, with -o json output clean enough to pipe into jq. One more fix converts hook timeouts from seconds to milliseconds when you run gemini hooks migrate --from-claude.

These fixes are on the nightly channel only. At our check, latest was still v0.65.0 and preview was v0.66.0-preview.0, and Saturday's nightly was built from the same commit as Friday's.

Practical dev impact: If you open Gemini CLI from a parent folder that holds several repos, check recent sessions for edits in the wrong place, since stable builds still have the old behavior. Until the fixes reach latest, our reading is that Esc is not a reliable stop on stable builds, so watch long agent turns rather than trusting a cancel.

2. Claude Code v2.1.310: the plan review and admin fixes Saturday left out

Saturday we led with the gateway fix in Claude Code v2.1.310. At our 5:49 AM ET check Sunday the release was still on latest and next, with stable on v2.1.308, and its notes hold more for plan reviewers and admins. In the VS Code extension, pressing Enter on the plan review card's "Send feedback and keep planning" button approved the plan instead of sending your comments back, and that is now fixed. A question's auto continue timeout also no longer fires the moment you close the external editor after a long edit.

On the admin side, Claude Code cloud sessions and Remote Control permissions are now part of Enterprise custom roles, so Owners can control access to each by role. Turning on Cloud sessions or Remote Control in admin settings now asks for confirmation and lists the custom roles that already have that permission, and a Choose file button loads a cloud environment's setup script from a file.

Practical dev impact: If you review Claude Code plans from the VS Code panel with the keyboard, update before your next planning session, because the old behavior turned a request for changes into an approval. Enterprise Owners who want cloud sessions or Remote Control for only some developers can now grant them by role, so check which roles already carry them first.

3. Copilot in Visual Studio summarizes pull requests and fixes vulnerable NuGet packages

This one is older. GitHub posted its Copilot in Visual Studio September update at 8:17 PM ET Thursday, and it held more than the Bring Your Own Model breaking change we noted Friday. The Git agent can now explore a pull request: open Copilot Chat, pick the Git agent, and attach a pull request from the Git Repository window to get a summary with links to the comments and files behind it. It needs your Git provider's MCP servers connected, and GitHub and Azure DevOps are both supported. NuGet Audit warnings in the Error List also gain a fixer that opens Copilot Chat in agent mode and asks Copilot to fix the vulnerable packages through the NuGet MCP server, once you sign in and turn that server on from the Copilot Chat tools menu. GitHub says the update reaches all Copilot plans, including Free.

Practical dev impact: .NET teams that triage NuGet Audit warnings by hand can hand the first pass to Copilot from the Error List, but read the package changes before you merge. Reviewers can try the Git agent on one open pull request.

Practical Impact Analysis

The common thread is control. A cancel that does not cancel, a write that lands in the wrong repo and a feedback button that approves are all cases where the agent did not match your intent. The Gemini CLI story leads even though it is only on nightly, because in our reading the risk applies to Gemini CLI's latest and preview channels until the fixes move up, while the Claude Code fix is already on latest, so the move there is simply to update.

Elsewhere at our check, Copilot CLI latest stayed on v1.0.103, and prerelease v1.0.104-3, published at 11:29 AM ET Saturday, notes only "Fixes and changes." Codex latest stayed on v0.164.0. GitHub's public monitoring for leaked secrets gained alert triage, validity checks, a REST API and webhooks, in public preview for GitHub Enterprise Cloud. VS Code was still on v1.143.1.

Tutorial

Read the script before you run it.

1. Run step 1 on a machine that uses Gemini CLI.
2. Run step 2 from the folder you usually open Gemini CLI in.
3. Run step 3 on each machine that uses Claude Code, then update the VS Code extension too.

# We have not run this script end to end on every platform. It only prints and searches unless you uncomment a line.
# 1. Gemini CLI. At 5:49 AM ET Sun 25 Oct npm showed latest v0.65.0, preview v0.66.0-preview.0,
#    and nightly v0.67.0-nightly.20261025.gcd1b45c2d, built from the same commit as Friday's fixes.
npm view @google/gemini-cli dist-tags --json
if command -v gemini >/dev/null; then gemini --version; else echo "gemini not on PATH"; fi
#    Optional, test machines only. Pinned at 5:49 AM ET Sun 25 Oct, nightly channel:
# npm install -g @google/gemini-cli@0.67.0-nightly.20261025.gcd1b45c2d
#    After a nightly install, set try_models=yes to list models as JSON. Skipped by default.
try_models=""
if [ "$try_models" = "yes" ]; then gemini models -o json; else echo "skipping gemini models"; fi

# 2. Nested Git repos under this folder, where the old path bug could write to a sibling. Paths only.
find . -mindepth 2 -maxdepth 4 -name .git -not -path "*/node_modules/*" -prune -print
if [ -d .git ]; then echo "this folder is itself a repo"; else echo "this folder is not a repo root"; fi

# 3. Claude Code. At 5:49 AM ET Sun 25 Oct npm showed latest and next on v2.1.310, stable on v2.1.308.
npm view @anthropic-ai/claude-code dist-tags --json
if command -v claude >/dev/null; then claude --version; else echo "claude not on PATH"; fi
#    Optional, npm installs only. Pinned at 5:49 AM ET Sun 25 Oct, latest and next channel:
# npm install -g @anthropic-ai/claude-code@2.1.310
#    Native installs: update the native way instead, and do not mix the two on one machine.
echo "Done. Nothing was installed or changed."

If step 2 lists more than one repo and you open Gemini CLI from that folder in an IDE workspace, our reading is that you were exposed to the sibling write bug, so review recent agent edits with git status in each repo. Keep the nightly on a test machine, and go back to latest when the fixes reach it.

Sources:

• Gemini CLI v0.67.0-nightly.20261024 release
• Gemini CLI v0.67.0-nightly.20261025 release
• Gemini CLI pull request 29868, cancel fix
• Gemini CLI pull request 29838, workspace paths
• Gemini CLI pull request 29880, models command
• Gemini CLI pull request 29899, hook timeouts
• Claude Code changelog
• Claude Code on npm
• GitHub Copilot in Visual Studio, September update
• Public monitoring adds triage, validity, API, and webhooks
• Copilot CLI releases
• Codex releases
• Visual Studio Code release notes

Recommended AI prompt

Copy this paragraph into ChatGPT, Claude, Gemini, Grok, or whatever AI you use.