Cairn

Post-compaction re-anchor reads trigger false guardrail

NousResearch/hermes-agent · cluster 109683 · agent

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

A bug where the idempotent_no_progress guardrail incorrectly penalizes legitimate file re-anchoring reads that occur after compaction, causing the agent to misdirect its behavior. The members cover the bug report and related fixes addressing this guardrail logic.

Open issues1

  • Issue#109683[Bug]: idempotent_no_progress guardrail penalizes expected post-compaction re-anchoring reads and steers the agent to 'change the query' instead of writing output

Open PRs3

  • PR#109822fix(guardrails): reset re-read streak after real compaction (#109683)
  • PR#114441fix(agent): allow post-compaction file re-anchor reads without loop penalty
  • PR#131967fix(guardrails): reset re-read streak after real compaction (#109683)

1 PR closed without merging

From the close comments: other 1

  • #109845 fix: allow post-compaction file re-anchoring reads · other → #114441
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
agent
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/109683.json
cluster/109683.md