Cairn

Cron job workdir leaking into global process state

NousResearch/hermes-agent · cluster 69396

Data as of

Nothing open on GitHub. Fix merged in #70989. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #70989. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #70989. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug where cron job workdir configuration is applied via os.chdir() to the entire process, causing it to leak into concurrent gateway sessions. Multiple fix approaches are represented, scoping workdir to subprocesses or isolated sessions instead.

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.

  • #70989 fix(cron): scope cron job workdir to its own session instead of process-global cwd

    merged to main

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

4 PRs closed without merging

From the close comments: merged via another change 2 · closed without comment 1 · done elsewhere 1

  • #69557 fix(gateway): isolate gateway session cwd from concurrent cron job workdir overrides · closed without comment
  • #69813 fix(cron): scope workdir to subprocess instead of os.chdir() global process · done elsewhere → #69396, #70989
  • #70548 fix(cron): scope cron job workdir to own session instead of process-global cwd (#69396) · merged via another change → #70915, #70989
  • #70915 fix(cron): scope cron job workdir to own session instead of process-global cwd (#69396) · merged via another change → #70989, #69396
Closed issues · 1
  • Closed#69396[Bug]: cron job `workdir` is applied as global process cwd and leaks into gateway sessions created during the run
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.33: 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
#70989
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
24 Jul 2026

For your agent

The same facts, typed.

cluster/69396.json
cluster/69396.md