NousResearch/hermes-agent

cleanup_vm environment key lookup corrections

Cluster 91440 · environments. Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues 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
1 issue and 2 PRs.

These issues and pull requests address a bug where cleanup_vm referenced a raw session or container ID instead of the lookup key used during environment creation. The corrections ensure the proper key is used so environments are correctly cleaned up.

Open issues1

  • Issue#91440[Bug]: cleanup_vm() uses the raw session ID instead of the resolved "default" environment key

Open PRs2

  • PR#91445fix(terminal): resolve the container key in cleanup_vm so envs stop leaking
  • PR#92380fix: cleanup_vm pops the resolved default environment key

1 PR closed without merging

From the close comments: duplicate 1

  • #91973 fix(tools): resolve task_id in cleanup_vm to match environment creation key (#91440) · duplicate → #91445
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.50: 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
environments
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.