HERMES_HOME pinning for routed-profile detection
Cluster 119242 · agent. Data as of
1 open item. Fix merged in #120103 on 23 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #120103. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #120103. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
These items address a bug where a mirrored or live HERMES_HOME environment variable can corrupt routed-profile detection across agent, profile, and MCP layers. Fixes center on anchoring a context-local or launch-time home value so background paths and profile routing decisions stay stable under multiplexed or embedding-host scenarios.
Open issues0
Open PRs1
- PR#119355fix(mcp): let embedding hosts pin the process home for routed-profile detection
Fixes on record
-
#120103 Cron, kanban, ledger and adapter background paths follow the owning profile under multiplex (#119858, #119859, #119973, #119242; salvage #119974 #120045 #120019 #120009 #112888)
files:
agent/redact.py,agent/secret_scope.py,contributors/emails/[redacted:email],contributors/emails/[redacted:email],cron/lifecycle_guard.py,gateway/AGENTS.md,gateway/delivery_ledger.py,gateway/platforms/api_server.py,gateway/platforms/api_server_openai_routes.py,gateway/platforms/api_server_runs.py,gateway/run_adapters.py,hermes_cli/env_loader.py,hermes_cli/kanban.py,hermes_cli/kanban_specify.py,hermes_cli/profiles.py,hermes_constants.py,hermes_logging.py,tests/agent/test_i18n.py,tests/agent/test_secret_scope_pinned_launch_home.py,tests/agent/test_serves_routed_profile_pin.py(+14 more)
2 PRs closed without merging
From the close comments: closed without comment 1 · merged via another change 1
Closed issues · 1
- Closed#119242[Bug]: a host that mirrors the served profile into HERMES_HOME defeats serves_routed_profile(): MCP connections fall back to bare cross-profile names
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.40: 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
- agent
- Merged PRs
- #120103
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 23 Sep 2026