Cairn
NousResearch/hermes-agent

Supermemory default container sentinel handling fix

Cluster 27226 · agent. Data as of

Nothing open on GitHub. Fix merged in #131272 on 2 Oct 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 #131272. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a bug where the Supermemory default/My Space configuration could create a literal 'default' container, with fixes to resolve sentinel container tags correctly.

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.

  • #131272 Supermemory installs from the plugin catalog — existing setups migrate automatically

    merged to main

    files: CONTRIBUTING.es.md, CONTRIBUTING.md, hermes_cli/config_defaults.py, hermes_cli/subcommands/memory.py, plugins/AGENTS.md, plugins/memory/supermemory/README.md, plugins/memory/supermemory/__init__.py, plugins/memory/supermemory/plugin.yaml, pm/extras.py, pyproject.toml, tests/agent/test_memory_agent_context.py, tests/e2e/core/upgrade/test_fresh_process_entrypoints.py, tests/plugins/memory/test_bom_tolerant_config_reads.py, tests/plugins/memory/test_memory_lazy_install.py, tests/plugins/memory/test_multiplex_memory_identity_scope.py, tests/plugins/memory/test_provider_threads_inherit_profile.py, tests/plugins/memory/test_supermemory_provider.py, tests/plugins/test_secret_scope_plugin_families.py, tests/test_project_metadata.py, website/docs/developer-guide/memory-provider-plugin.md (+5 more)

2 PRs closed without merging

From the close comments: done elsewhere 1 · stale or abandoned 1

  • #27281 fix(supermemory): resolve sentinel container tags to Supermemory default/My Space · stale or abandoned
  • #53385 fix(supermemory): resolve default container sentinels to None (#27226) · done elsewhere → 0a374d1, #131272
Closed issues · 1
  • Closed#27226[Bug]: Supermemory default/My Space config can create a literal `default` container
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

Subsystem
agent
Merged PRs
#131272
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
2 Oct 2026

For your agent

The same facts, typed.

cluster/27226.json
cluster/27226.md