{"version":"2.1.323","anchor":"teammates-run-in-process-when-file-tool-reads-outside-the-wo","canonical_anchor":"teammates-run-in-process-when-file-tool-reads-outside-the-wo","heading":"Teammates stay in the main window when reads outside the project are blocked","tier":"notice","area":"Agent Teams","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/teammates-run-in-process-when-file-tool-reads-outside-the-wo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Teammates stay in the main window when reads outside the project are blocked\n\nWith `permissions.blockFileToolReadsOutsideWorkingDirectories` on, teammates always run in-process instead of in tmux or iTerm2 panes\n\n**What**\n\nIn 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.\n\nWhen 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.\n\n**Why**\n\nIf this policy is on, a tmux or iTerm2 teammate mode you chose is overridden, and teammates no longer open in their own panes.\n\n- Area: Agent Teams\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}