NousResearch/hermes-agent

Opt-in durable checkpoint before memory compaction

Cluster 93986. Data as of 2026-10-30 11:57 UTC

Nothing open on GitHub. Fix merged in #94639 on 25 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #94639, then check it covers your case.

Read #94639 Pick up a Lab task

These items concern a feature allowing memory providers to require a durable checkpoint before lossy or compressive operations, with a fail-closed contract as an opt-in API mechanism.

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.

#94639 feat(memory): providers can require a durable checkpoint before lossy compaction (#93986, salvage #93996)

merged to main

files: agent/agent_init.py, agent/codex_runtime.py, agent/conversation_compression.py, agent/memory_manager.py, agent/memory_provider.py, agent/native_compaction.py, agent/turn_finalizer.py, cli-config.yaml.example, gateway/run.py, gateway/slash_commands.py, hermes_cli/config_defaults.py, hermes_state.py, hermes_state_common.py, run_agent.py, tests/agent/test_pre_compress_checkpoint_contract.py, tests/run_agent/test_pre_compress_memory_context.py, website/docs/developer-guide/memory-provider-plugin.md

1 PR closed without merging

From the close comments: merged via another change 1

#93996 feat(memory): opt-in fail-closed pre-compress checkpoint contract (API v1) · merged via another change → 1ee524f, #94639

Closed issues · 1

Closed#93986[Feature]: Opt-in fail-closed pre-compress checkpoint contract for memory providers

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.67: 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: #94639
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 25 Aug 2026

For your agent

The same facts, typed.

cluster/93986.json
cluster/93986.md