container backend detection and cwd-override guard fixes

NousResearch/hermes-agent · cluster 101013 · environments

Data as of

Nothing open on GitHub. Fix merged in #103642. Check it covers your case.

The short answer

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

A new Apple Container backend was added for macOS terminals, alongside several fixes ensuring the cwd-override guard correctly identifies both built-in and plugin-registered container backends via a consistent helper function.

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.

  • #103642 fix(tools): file-tools env creation applies the container cwd guard to plugin container backends too (#101013, salvage #101389)

    merged to main

    files: tests/tools/test_file_tools_plugin_container_cwd.py, tools/file_tools.py

3 PRs closed without merging

From the close comments: done elsewhere 2 · superseded by another PR 1

  • #78035 feat(terminal): add native Apple Container backend for macOS · superseded by another PR → #78035, #109529, #111972, #110390, #6867, #57127
  • #101100 fix(file-tools): route the cwd-override guard through _is_container_backend · done elsewhere
  • #101389 fix(tools): use _is_container_backend() in cwd-override guard (#101013) · done elsewhere → 5035fbd, #103642
Closed issues · 1
  • Closed#101013file_tools cwd-override guard uses _CONTAINER_BACKENDS while the same function uses _is_container_backend(), so plugin-registered container backends skip the guard
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.40: 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
Merged PRs
#103642
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
5 Sep 2026

For your agent

The same facts, typed.