Cairn

Project-scoped memory filtering feature requests

NousResearch/hermes-agent · cluster 16833 · agent

Data as of

3 open items. Fix attempted, not merged.

The short answer

2open issues
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues 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
2 issues and 1 PR. Broad area: open items may be separate problems.

These requests propose memory pools or filtering mechanisms that scope stored memory to a specific project or working directory context. Both target the same concept of isolating or prioritizing memory entries based on project context.

Open issues2

  • Issue#16833[Feature Request] Project-scoped memory pools (global + per-project)
  • Issue#33638Feature: Project-scoped memory — filter built-in MEMORY.md by cwd/project context

Open PRs1

  • PR#96709feat(memory): project-scoped memory — filter built-in MEMORY.md by cwd/project context
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.45: 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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/16833.json
cluster/16833.md