NousResearch/hermes-agent

multiplex profile config isolation and key leakage fixes

Cluster 95470. Data as of 2026-10-30 11:57 UTC

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

open issues

open PRs

items 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: Nothing open on GitHub.

Next step: read #101242, then check it covers your case.

Read #101242 Pick up a Lab task

These items address bugs where multiplex profiles incorrectly inherited or leaked the TERMINAL_DOCKER_SHARED_CONTAINER_KEY and other terminal/docker configuration that should be scoped per-profile. Fixes ensure each routed multiplex profile receives its own isolated terminal, cwd, backend, and Docker config.

Open issues0

No open issues.

Open PRs0

No open pull requests.

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)

1 PR closed without merging

From the close comments: merged via another change 1

#95471 fix(docker): do not leak the shared-container key across multiplex profiles · merged via another change → 4a7f228, #101242

Closed issues · 1

Closed#95470[Bug]: multiplex leaks TERMINAL_DOCKER_SHARED_CONTAINER_KEY to profiles that did not set it

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

Merged PRs: #101242
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 2 Sep 2026

For your agent

The same facts, typed.

cluster/95470.json
cluster/95470.md