NousResearch/hermes-agent

Profile updates incorrectly overwrite user cron jobs

Cluster 120823. Data as of

Nothing open on GitHub. Fix merged in #121264 on 24 Sep 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 #121264. 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 profile installation or update operations replace or delete cron job configurations instead of merging them, causing user-defined and runtime cron jobs to be lost. The work involves changing the merge strategy for distributed cron job data.

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.

  • #121264 hermes profile update merges shipped cron jobs instead of replacing the store (#120823, salvage #120910)

    merged to main

    files: cron/job_definition.py, hermes_cli/profile_distribution.py, tests/hermes_cli/test_profile_distribution.py, website/docs/user-guide/profile-distributions.md

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #120824 fix(profiles): merge cron/jobs.json per job so update keeps the installer's jobs · done elsewhere → 68ca2c8, b0aefcc, #120823, #121264, #120910
  • #120910 fix(profiles): merge distributed cron jobs without replacing runtime state · superseded by another PR → 99b7078, 06c3062, 68ca2c8, 5ae3909, a49f13d, d9a6a13, f17b78f, b0aefcc, #121264
Closed issues · 1
  • Closed#120823[Bug]: profile update deletes the user's own cron jobs, and profile install leaves shipped jobs running
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
#121264
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.