Cairn
NousResearch/hermes-agent

Cross-profile isolation fixes in multiplexed containers

Cluster 101132 · environments. Data as of

1 open item. Fix merged in #101242 on 2 Sep 2026. Check it covers your case.

The short answer

0open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #101242. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #101242. That is separate from the fix event.
Still open
0 issues and 1 PR.

These items address security and correctness issues where Docker volumes, working directories, and backend configs leaked between profiles in multiplexed gateway containers. Fixes enforce per-profile isolation for terminal cwd, Docker configuration, and bind mounts.

Open issues0

No open issues.

Open PRs1

  • PR#101187fix(docker): refuse cross-profile bind mounts in multiplexed containers

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #101242 fix(gateway): routed multiplex profiles get their own terminal cwd/backend/docker config; container boot honors config multiplex_profiles (#68559 #85413, salvage #99225 #85437)

    merged to main

    files: agent/agent_init.py, agent/prompt_builder.py, agent/runtime_cwd.py, agent/skill_utils.py, contributors/emails/[redacted:email], cron/scheduler.py, gateway/platforms/base.py, gateway/run.py, gateway/runtime_footer.py, gateway/slash_commands.py, hermes_cli/container_boot.py, tests/hermes_cli/test_container_boot.py, tests/tools/test_terminal_scope_multiplex.py, tools/browser_tool.py, tools/code_execution_tool.py, tools/env_probe.py, tools/file_tools.py, tools/terminal_scope.py, tools/terminal_tool.py, tui_gateway/server.py (+1 more)

Closed issues · 1
  • Closed#101132Multiplexed gateway: user-declared docker_volumes and cwd leak across profiles (cross-profile write access)
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.67: the share of item 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.

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 Lab

At a glance

Subsystem
environments
Merged PRs
#101242
Closed issues
1
Attempts
0 PRs closed without merging
Fix link checked
2 Sep 2026

For your agent

The same facts, typed.

cluster/101132.json
cluster/101132.md