NousResearch/hermes-agent

Secret-source re-pull losing credentials after cron

Cluster 102041. Data as of 2026-10-24 04:06 UTC

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

open issues

open PRs

items grouped

Known?: Yes. 4 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #107629. 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.

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

Read #107629 Pick up a Lab task

These issues and fixes address a bug where secret-source values are dropped from the multiplex scope after re-pulls or cron job runs, causing credentials to be lost process-wide. The fixes adjust how applied state is tracked to prevent empty or incorrect credential snapshots.

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.

#107629 fix(secrets): multiplex secret-source re-pull no longer empties the default profile's credentials (#102041)

merged to main

files: cron/scheduler.py, hermes_cli/env_loader.py, hermes_cli/plugins.py, tests/cron/test_scheduler.py, tests/hermes_cli/test_secret_source_bootstrap.py, tests/test_env_loader_secret_sources.py, website/docs/developer-guide/secret-source-plugin.md

2 PRs closed without merging

From the close comments: superseded by another PR 2

#102045 fix(secrets): count value-equivalent env vars as applied so re-pulls keep the snapshot · superseded by another PR → 08830ef, #107629, #102041
#102145 fix(env): only mark secret-source home as applied when keys actually applied (fixes #102041) · superseded by another PR → 08830ef, #107629, #102045

Closed issues · 1

Closed#102041Secret-source values are lost from the multiplex scope after any cron job runs (env-shadowed re-apply), breaking credentials process-wide

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: #107629
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 11 Sep 2026

For your agent

The same facts, typed.

cluster/102041.json
cluster/102041.md