# NousResearch/hermes-agent · Multiplexed profile ambient bridge isolation fixes

## Open now

- 0 issues, 1 PR open on GitHub.
- PR #107714: fix(terminal): isolate ambient bridge and bind launch scope under multiplexing (#107422)

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.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 1 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #108440. Verify it addresses your case.
- **Recommended:** read PR #108440 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-108440`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #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)

## Prior & competing PRs

- **#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)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - 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)
- **#107442: fix(tools/tui): stop multiplex ambient TERMINAL_* latch from poisoning launch profile (#107422)**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `a5c801c8dcb`, `606903badc4`, `#108440`, `#107422`
- **#107714: fix(terminal): isolate ambient bridge and bind launch scope under multiplexing (#107422)**. open
  - maintainer direction: category `uncategorized`; implication `needs_llm`; refs `#107422`, `#107442`
  - files: `tests/tools/test_terminal_env_bridge.py`, `tests/tools/test_terminal_scope_multiplex.py`, `tools/terminal_scope.py`, `tools/terminal_tool.py`, `tui_gateway/methods_prompt.py`, `tui_gateway/methods_session.py`, `tui_gateway/prompt_turn.py`, `tui_gateway/server.py`

## Fix status

- Merged to main in PR #108440 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-11`.
- Subsystem: `environments`