Cairn
NousResearch/hermes-agent

Improve checkpoint_required error messaging and warnings

Cluster 106870. Data as of

Nothing open on GitHub. Fix merged in #115394 on 18 Sep 2026. Check it covers your case.

The short answer

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

These issues and fixes address the lack of startup warnings and actionable guidance when compression.checkpoint_required cannot be satisfied due to missing checkpoint API v2 support. The work adds upfront initialization warnings and clearer remediation messaging to replace opaque blocking errors.

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.

  • #115394 checkpoint_required block names the flag and the way out; init warns up front (#106870, consolidates #106879 + #106882)

    merged to main

    files: agent/agent_init.py, agent/conversation_compression.py, tests/agent/test_pre_compress_checkpoint_contract.py, website/docs/developer-guide/memory-provider-plugin.md

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #106879 fix(compression): warn and remediate opaque checkpoint_required blocks · done elsewhere → 96030a3, 02e12e0, 53acc39, #115394, #106870
  • #106882 fix(compression): warn at init and add remediation when checkpoint_required cannot pass · done elsewhere → 96030a3, #115394
Closed issues · 1
  • Closed#106870[Bug]: compression.checkpoint_required=true permanently blocks /compress with an opaque error when the memory provider lacks checkpoint API v2 — no startup warning, no actionable guidance
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.50: 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

Merged PRs
#115394
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/106870.json
cluster/106870.md