Agent workspace containment and folder boundaries

NousResearch/hermes-agent · cluster 502 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

3open issues
1open PR
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
3 issues and 1 PR. Broad area: open items may be separate problems.

These issues and PRs concern limiting agent file operations to a designated workspace or project folder, including a reported bug about files scattering outside expected boundaries and feature requests for configurable workspace scoping.

Open issues3

  • Issue#8926[Feature]: I hope the agent only operates within their own workspace.
  • Issue#25279[BUG] Agents do not respect workspace boundaries, scatter files across entire filesystem
  • Issue#56159[Feature]: Specify a folder that al;l Hermes work stays within

Open PRs1

  • PR#98614feat(agent): compose context files with `@` include directives
Closed issues · 1
  • Closed#502Feature: Project Context System — @ References, .hermes.md Config Files & Workspace Awareness
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.21: 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
agent
Closed issues
1
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.