{"version":"2.1.314","anchor":"tmux-swarm-session-uses-a-scrubbed-environment","canonical_anchor":"tmux-swarm-session-uses-a-scrubbed-environment","heading":"Teammate tmux sessions start with a filtered set of environment variables","tier":"notice","area":"Agent Teams","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/tmux-swarm-session-uses-a-scrubbed-environment","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Teammate tmux sessions start with a filtered set of environment variables\n\nThe tmux session for teammate agents now gets a filtered copy of environment variables instead of all of them\n\n**Unclear.** It is not clear which environment variables the filter removes.\n\n**What**\n\ntmux is a program that runs several terminal sessions at once, and Claude Code uses it to run a group of teammate agents (extra copies of Claude working alongside the main one). When Claude Code creates that tmux session, it now passes it a filtered set of environment variables, which are named values that programs read for settings. Before, the session received everything from the current environment.\n\n**Why**\n\nTeammates running in this tmux session may now see a different set of environment variables than your own terminal.\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"}