NousResearch/hermes-agent

Fix task-specific glob patterns in environment info

Cluster 230. Data as of

Nothing open on GitHub. Fix merged in #231 on 2 Mar 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #231. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #231. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs address a bug where disk usage and active environment lookups used a hardcoded glob pattern instead of a task-specific one. Related work also includes enriching active environment info and improving task ID handling robustness.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

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

  • #231 fix: use task-specific glob pattern in disk usage calculation

    merged to main

    files: tests/tools/test_terminal_disk_usage.py, tools/terminal_tool.py

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #251 fix: use task-specific glob pattern in disk usage calculation · superseded by another PR → #231
Closed issues · 1
  • Closed#230get_active_environments_info() uses hardcoded glob instead of task-specific pattern
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

Merged PRs
#231
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
2 Mar 2026. This confirmation is old and may be out of date (a revert or reopen would not have invalidated it here); re-verify.

For your agent

The same facts, typed.