NousResearch/hermes-agent

Cron config env variable expansion from .env file

Cluster 15890 · cron. Data as of

Nothing open on GitHub. Fix merged in #19872 on 4 May 2026. Check it covers your case.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #19872. 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.

A bug where environment variable references like ${ENV_VAR} are not expanded in cron job configuration, along with related fix attempts addressing this behavior.

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.

  • #19872 fix(cron): expand refs in config.yaml during job execution

    merged to main

    files: cron/scheduler.py, tests/cron/test_scheduler.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #15897 fix(cron): expand ${VAR} refs in config.yaml during job execution (#15890) · merged via another change → #19872
Closed issues · 1
  • Closed#15890Cron job fails to expand ${ENV_VAR} from .env file
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

Subsystem
cron
Merged PRs
#19872
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
4 May 2026

For your agent

The same facts, typed.