# NousResearch/hermes-agent · Fix task-specific glob patterns in environment info

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #231. Verify it addresses your case.
- **Recommended:** read PR #231 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-231`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #230: get_active_environments_info() uses hardcoded glob instead of task-specific pattern

## Prior & competing PRs

- **#231: fix: use task-specific glob pattern in disk usage calculation **. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `tests/tools/test_terminal_disk_usage.py`, `tools/terminal_tool.py`
- **#251: fix: use task-specific glob pattern in disk usage calculation**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#231`

## Fix status

- Merged to main in PR #231 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-03-02`. This confirmation is old and may be out of date (a revert/reopen would not have invalidated it here); re-verify.