Compression child sessions losing cwd and workspace context
NousResearch/hermes-agent · cluster 42228 · agent
Data as of
Nothing open on GitHub. Fix merged in #52658. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 2 issues already closed.
- Fix event
- A fix was merged to main in PR #52658. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PR #69343. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Multiple issues and fixes address a bug where compressed or split child sessions fail to inherit the parent session's working directory and git repo metadata, causing sessions to appear in no workspace or lose project sidebar entries.
Open issues0
Open PRs0
Fixes on record
-
#52658 feat(compression): flip in_place default to True + guard fix (#38763) [salvage #51959]
files:
gateway/run.py,gateway/slash_commands.py,hermes_cli/config.py,scripts/release.py,tests/agent/test_compression_concurrent_fork.py,tests/agent/test_compression_logging_session_context.py,tests/agent/test_compression_rotation_state.py,tests/gateway/test_compression_concurrent_sessions.py,tests/gateway/test_session_hygiene.py,tests/run_agent/test_compression_boundary_hook.py,tests/run_agent/test_in_place_compaction.py -
#69343 fix(state): compression child sessions inherit cwd and repo metadata
files:
hermes_state.py,tests/agent/test_compression_rotation_state.py,tests/test_hermes_state.py
3 PRs closed without merging
From the close comments: superseded by another PR 2 · merged via another change 1
-
#42233 Fix #42228: Inherit parent session cwd in compressed continuation sessions · superseded by another PR →
#52658,#38763 -
#42240 fix(agent): inherit parent session cwd during compression rotation · superseded by another PR →
#52658,#38763 -
#64731 fix(state): inherit cwd/git_repo_root on parent_session_id children · merged via another change →
75099ca,#69343
Closed issues · 2
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.26: 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 Lab