This week in Claude Code, Codex and Gemini CLI (week of November 22, 2026)
Claude Code v2.1.328 makes auto mode the starting mode on Bedrock, Vertex and Foundry. Codex makes GPT-6.2 Sol the default, and Gemini CLI fixes several permission-policy matches.
Contents
The biggest change this week is that Claude Code v2.1.328 brings auto mode to Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry and the Claude apps gateway. It was not only added: interactive sessions with no permission mode now start in it. If you work through a third-party provider, how often you see a prompt changes without you touching any setting.
Codex shipped three releases and Gemini CLI two, the latter clustering several fixes around permission-policy matching.
KEY POINT
This week in brief
- Claude Code v2.1.328 adds auto mode on third-party providers and makes it the starting mode when none is set
- Codex v0.171.0 makes GPT-6.2 Sol the default catalog selection and enables the TUI workspace by default
- Gemini CLI v0.69.0 and v0.70.0 fix several shell-command approval and policy-matching behaviours
Claude Code
Five releases, v2.1.326 through v2.1.330. There is no v2.1.324 — the CHANGELOG goes from v2.1.325 straight to v2.1.323.
v2.1.328
The starting mode changed:
Added auto mode for Claude Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry and Claude apps gateway; interactive sessions with no permission mode start in it
In auto mode a separate classifier model reviews actions instead of prompting you. For how the modes differ, see Claude Code starts in auto mode by default.
There is a compaction fix too: "Fixed automatic compaction reusing the session's earlier system prompt instead of rebuilding it the way /compact does." That matters if you changed settings or modes mid-session.
For zsh users: "Fixed Bash commands in zsh stopping with a "not found" error at a word that starts with =", covering echo ==== and [ a == b ]. A =cmd no longer expands to a command's path.
On hooks, mcp_tool gained "onFailure": "block" — "as for command and HTTP hooks: a hook whose call fails blocks the action".
v2.1.327
Two MCP configuration items. The addition keeps tokens off the command line:
claude mcp add-json my-server - < server.json
Added
claude mcp add-json <name> -to read the server's JSON from stdin, so tokens can stay off the command line; not available inside a Claude Code session
The other is a fix: "Fixed claude mcp add and claude mcp remove with project scope deleting other top-level keys from .mcp.json" — a $schema, or another tool's servers key, was being removed. For writing .mcp.json, see Adding MCP servers to Claude Code.
A permission fix landed as well: auto mode was ignoring wildcard PowerShell allow rules that name a script with .\, such as PowerShell(.\scripts\build.ps1 *).
v2.1.326
Two permission-check fixes:
- "Fixed
cpof a file being refused when only its source was covered by anEditdeny rule" - "Fixed a misleading "Dangerous rm operation" warning in the Bash permission prompt on some commands with no rm" — the ones Claude Code cannot read reliably
v2.1.329 and v2.1.330
Mostly settings-file and freeze fixes.
| Fix | Version |
|---|---|
~/.claude.json could be reset to defaults when a network stall or file lock made it unreadable | v2.1.329 |
| Changes to user settings were lost when several Claude Code processes saved at the same time | v2.1.330 |
ExitWorktree and the exit dialog deleted a worktree another running session was working in | v2.1.330 |
| Claude Code froze for up to several minutes right after compacting a very long conversation | v2.1.330 |
v2.1.330 also adds easel, a built-in mod that draws charts on request and under MCP metrics results, on Pro and Max and, where available, Team and Enterprise, on macOS and Linux. Automatic charts can be turned off in /config.
Codex
Three releases: v0.169.1, v0.170.0 and v0.171.0. v0.169.1 has no release notes — under a "Chores" heading it says only "No verified release highlights available.", and its per-PR list is empty.
v0.171.0
Two changes to defaults:
Added GPT-6.2 Sol and Astra to model catalogs, with Sol as the default catalog selection.
Enabled the TUI workspace by default, with searchable document previews, image previews, and subagent transcripts alongside the main conversation.
The TUI workspace arrived in v0.168.0 as features.tui_workspace, and is now on by default. In What changed in Codex CLI v0.168 and v0.169 we noted that this key has no entry in the configuration reference; with it enabled by default, you no longer need to set it.
Non-interactive runs gained "Added codex exec --remote <ADDR> to start or resume noninteractive sessions on an existing app server." Also new: /rc and /remote for managing local remote control and showing device pairing codes, and custom MCP status line selection and authoring through /statusline when tui_extensions_statusline is enabled.
Among the fixes, "Kept permission profiles intact when changing working directories" is the practical one.
v0.170.0
A fix for sandbox restrictions being lost
"Fixed permission updates and child threads losing existing sandbox restrictions." Permission updates and child threads were losing restrictions that were already in place — a failure in the permissive direction, so v0.170.0 or later is worth installing. Windows sandbox permission preservation was fixed in the same release.
On MCP: "Added experimental support for using identically named MCP servers across environments", plus "Fixed MCP OAuth credential races during cancellation, login, and logout."
One documentation item: "Updated sandbox documentation to explain permission profiles and filesystem rules." For the configuration file as a whole, see Switching models, reasoning effort and profiles in Codex config.toml.
Gemini CLI
Two releases, v0.69.0 and v0.70.0, both shipping with no summary prose — just a list of pull requests. What stands out this week is that fixes to shell-command approval and policy matching appear across both.
| Change | Version |
|---|---|
fix(cli): skip system MCP servers with insecure command permissions (#30283) | v0.70.0 |
fix(core): keep ASK_USER for shell commands with unresolved expansion (#30338) | v0.70.0 |
fix(core): match commandPrefix and commandRegex rules against the top-level command argument (#30355) | v0.70.0 |
refactor(core): use re2js for linear-time policy argsPattern evaluation (#30282) | v0.70.0 |
fix(cli): disclose canonical link path and default consent prompt to no (#30289) | v0.70.0 |
fix(core): fix Windows PowerShell substitution false positives and policy handling (#30110) | v0.69.0 |
fix(cli): resolve folder trust before entering the macOS Seatbelt sandbox (#30164) | v0.69.0 |
fix(cli): use isSubpath for theme file home-directory check (#30160) | v0.69.0 |
The keep ASK_USER for shell commands with unresolved expansion entry moves commands whose expansion is unknown toward a prompt rather than an automatic allow. And changing what commandPrefix and commandRegex match against — the top-level command argument — changes how your allow rules land. For MCP server configuration, see Add an MCP server to Gemini CLI.
There are only two features. feat(cli): add /stats heatmap subcommand for daily token usage (#30135, v0.69.0) shows daily token usage as a heatmap, and feat(cli): support standalone theme.json configuration for custom themes (#30119, v0.69.0) lets a custom theme live in its own theme.json.
A timeout override also landed: model.requestTimeoutMs, with the environment variable GEMINI_API_HEADERS_TIMEOUT_MS, overrides the 60-second API headers timeout across all auth modes (#30183, v0.69.0).
What to check now
- If you go through Bedrock, Vertex, Foundry or a gateway, check your starting mode. From v2.1.328, an interactive session with no mode set starts in auto mode. Set
permissions.defaultModeexplicitly to keep prompting - Update Gemini CLI to v0.70.0. Several fixes touch shell-command approval and policy matching
- Update Codex to v0.170.0 or later. It fixes permission updates and child threads losing sandbox restrictions
- If your
.mcp.jsonholds a$schemaor another tool's keys, check it. A pre-v2.1.327claude mcp addorremovemay have dropped them - If you pass MCP server tokens on the command line, move to
claude mcp add-json <name> -. It now reads from stdin
Summary
- Ten releases this week: five for Claude Code, three for Codex, two for Gemini CLI
- Top priority is Claude Code v2.1.328 bringing auto mode to third-party providers, which changes the default starting mode
- Codex v0.171.0 makes GPT-6.2 Sol the default catalog selection and enables the TUI workspace by default
- Codex v0.170.0 fixes permission updates and child threads losing existing sandbox restrictions
- Gemini CLI v0.69.0 and v0.70.0 fix several permission-policy matches and shell-command approval behaviours
FAQ
- I'm on Bedrock or Vertex and my permission prompts stopped appearing. Why?
- v2.1.328. Auto mode was added for Opus 4.6 and Sonnet 4.6 on Amazon Bedrock, Google Cloud's Agent Platform, Microsoft Foundry and the Claude apps gateway, and interactive sessions with no permission mode now start in it.
- Did Codex change its default model?
- In v0.171.0, GPT-6.2 Sol and Astra were added to the model catalogs, with Sol as the default catalog selection.
- Is there anything to install right away this week?
- If you use Gemini CLI, v0.70.0 — it carries several fixes to permission-policy matching and to how system MCP servers are handled. For Claude Code, v2.1.330 fixes settings files being lost.
Primary sources
This article was drafted by AI from official documentation and reviewed by the site operator before publishing. Found a mistake? Let us know via the contact page.