Cairn
NousResearch/hermes-agent

Memory provider context-skip logic broken by hardcoded value

Cluster 80646 · agent. Data as of

Nothing open on GitHub. Fix merged in #115301. Check it covers your case.

The short answer

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

A bug where agent_context is hardcoded to 'primary' causes provider context-skip logic for cron, flush, and subagent scenarios to be dead code. Multiple fixes attempt to derive agent_context from the platform so scoping behaves correctly across execution contexts.

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.

  • #115301 fix(memory): cron and subagent sessions no longer initialize providers as "primary" (#80646, salvage #80691)

    merged to main

    files: agent/agent_init.py, contributors/emails/[redacted:email], tests/agent/test_memory_agent_context.py, website/docs/developer-guide/memory-provider-plugin.md

3 PRs closed without merging

From the close comments: merged via another change 2 · stale or abandoned 1

  • #80691 fix: derive agent_context from platform for memory provider context-skip (#80646) · merged via another change → 6f305f3, #115301, #80646
  • #107045 fix(agent): derive agent_context from platform so provider skip logic is live (#80646) · merged via another change → 6f305f3, e105d45, #115301, #80691
  • #112100 fix(memory): scope providers by execution context · stale or abandoned → 17489a7, d84ece4, 15650b7, #105171, #67045, #85909, #93713
Closed issues · 1
  • Closed#80646`agent_context` is hardcoded to "primary" — provider context-skip logic (cron/flush/subagent) is dead code
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
Merged PRs
#115301
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/80646.json
cluster/80646.md