Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.323 ·

Teammates stay in the main window when reads outside the project are blocked

With permissions.blockFileToolReadsOutsideWorkingDirectories on, teammates always run in-process instead of in tmux or iTerm2 panes

You'll notice Improvements
JSON All of v2.1.323
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
Agent TeamsArea: what it touches
ImprovementsKind: in v2.1.323,
ImprovementsSection of the release
What

In agent teams, Claude Code can run teammates, which are extra Claude agents working alongside the main one. A setting chooses where they run: inside the main Claude Code process, or in separate tmux or iTerm2 panes, which are split sections of a terminal window.

When the permissions.blockFileToolReadsOutsideWorkingDirectories policy is active, Claude Code now always runs teammates in-process and skips tmux and iTerm2 panes. Before, it went straight to your teammate-mode setting.

Why

If this policy is on, a tmux or iTerm2 teammate mode you chose is overridden, and teammates no longer open in their own panes.

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed a case where the Write and Edit tools could write to a path covered by a Read deny rule

See this entry in the whole of v2.1.323 →

Feedback