Multiplexed profile ambient bridge isolation fixes
Cluster 107422 · environments. Data as of
1 open item. Fix merged in #108440 on 11 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #108440. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #108440. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These issues and PRs address a bug where TERMINAL_* environment variable latches and related config bridges in multiplexed dashboard mode cause one profile's settings to bleed into another, leading to mislabeled or misconfigured container launches. The work focuses on isolating ambient bridge state per launch profile under multiplexing.
Open issues0
Open PRs1
- PR#107714fix(terminal): isolate ambient bridge and bind launch scope under multiplexing (#107422)
Fixes on record
-
#108440 fix(gateway): multiplexed profiles no longer poison each other via config.yaml→env bridges, TERMINAL_* latch and path memos (#80099, #107422, #107327; salvage #100604 #100435 #100448 #91198 #107442 #107335)
files:
contributors/emails/[redacted:email],gateway/config_loader.py,gateway/platforms/_shared.py,gateway/platforms/signal.py,gateway/platforms/yuanbao.py,gateway/run.py,gateway/run_inbound.py,gateway/run_notifications.py,plugins/platforms/dingtalk/adapter.py,plugins/platforms/discord/adapter.py,plugins/platforms/feishu/adapter.py,plugins/platforms/matrix/adapter.py,plugins/platforms/slack/adapter.py,plugins/platforms/telegram/adapter.py,plugins/platforms/whatsapp/adapter.py,tests/gateway/test_discord_allow_bots_yaml_config.py,tests/gateway/test_multiplex_process_global_sinks.py,tests/gateway/test_multiplex_yaml_env_bridge_isolation.py,tests/tools/test_env_passthrough.py,tests/tools/test_file_write_safety.py(+9 more)
1 PR closed without merging
From the close comments: merged via another change 1
-
#107442 fix(tools/tui): stop multiplex ambient TERMINAL_* latch from poisoning launch profile (#107422) · merged via another change →
a5c801c,606903b,#108440,#107422
Closed issues · 1
- Closed#107422[Bug]: Multiplexed dashboard (app-global remote mode): one-shot TERMINAL_* ambient bridge latches a secondary profile's docker policy; primary-profile tool calls spawn mislabeled containers (residual of #68559)
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- environments
- Merged PRs
- #108440
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 11 Sep 2026