NousResearch/hermes-agent

Cron env reload order fix for no-agent jobs

Cluster 59030 · cron. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items address a bug where environment variables (including credentials) are not refreshed before the no-agent short-circuit path in the cron run_job function. The fix moves the .env reload to occur earlier, before that code path is reached.

Open issues1

  • Issue#59030no_agent cron jobs deliver with stale os.environ credentials — env reload happens after the no_agent short-circuit in run_job()

Open PRs1

  • PR#61148fix(cron): refresh env before no-agent runs

1 PR closed without merging

From the close comments: done elsewhere 1

  • #59080 fix(cron): reload .env before the no_agent short-circuit in run_job · done elsewhere
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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.