Cairn
NousResearch/hermes-agent

Agent logging tied to wrong profile home directory

Cluster 125974 · agent. Data as of

1 open item. Fix merged in #126145 on 28 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 #126145. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #126145. That is separate from the fix event.
Still open
0 issues and 1 PR.

Issues and a fix addressing how the desktop agent incorrectly uses the import-time home directory for logging and related profile-scoped resources, causing session data to be written to the wrong profile's context.

Open issues0

No open issues.

Open PRs1

  • PR#126005fix(agent): log to the active profile home, not the import-time freeze (#125974)

Fixes on record

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

  • #126145 Served profiles no longer inherit the launch profile's logs, log ownership, slash gating, TTS credentials or skipped .env (#125974 #120151 #121705 #120481 #125530)

    merged to main

    files: agent/agent_init.py, gateway/run_busy.py, gateway/slash_access.py, gateway/slash_commands.py, gateway/slash_commands_login.py, gateway/slash_commands_session.py, hermes_cli/env_loader.py, hermes_logging.py, tests/agent/test_setup_logging_profile_scope.py, tests/agent/test_skip_background_review.py, tests/gateway/test_multiplex_credential_isolation.py, tests/gateway/test_slash_access_dispatch.py, tests/hermes_cli/test_local_runtime.py, tests/test_hermes_logging.py, tests/tools/test_tts_command_providers.py, tests/tools/test_tts_lifecycle_leases.py, tools/tts_command_provider.py, tools/tts_tool_lifecycle.py, website/docs/user-guide/multi-profile-gateways.md

Closed issues · 1
  • Closed#125974Desktop serve backend logs other profiles' sessions into the launch profile's agent.log (agent_init uses the import-time home)
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
agent
Merged PRs
#126145
Closed issues
1
Attempts
0 PRs closed without merging
Fix link checked
28 Sep 2026

For your agent

The same facts, typed.

cluster/125974.json
cluster/125974.md