NousResearch/hermes-agent
Background process workdir not forwarded to execution
Cluster 100020 · environments. Data as of
1 open item. Fix attempted, not merged.
The short answer
0open issues
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab task
These items address a bug where the computed working directory is stored but not forwarded when spawning background processes or terminal commands. The fixes ensure the correct cwd is actually passed through to execution.
Open issues0
Open PRs1
- PR#100036fix(terminal): run background commands in their requested workdir
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#100045 fix(process-registry): pass the resolved cwd to env.execute in spawn_via_env · superseded by another PR →
#100036
Closed issues · 1
- Closed#100020background=true ignores workdir; the resolved cwd is stored but never used for execution
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.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
- environments
- Closed issues
- 1
- Attempts
- 1 PR closed without merging