Cron jobs incorrectly loading memory despite skip setting

Cluster 91269. Data as of 2026-10-29 11:48 UTC

Nothing open on GitHub. Fix merged in #91384 on 21 Aug 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

A bug where scheduled cron jobs load MEMORY.md even when skip_memory is enabled, along with associated fix attempts addressing this behavior.

Open issues0

No open issues.

No open pull requests.

Merged to main. A stamp counts the issues a fix is linked to.

#91384 fix(cron): do not load MEMORY.md into scheduled jobs

merged to main

files: agent/agent_init.py, cron/scheduler.py, tests/agent/test_skip_memory_store_65429.py, tests/cron/test_agent_scheduling_gate.py, tests/cron/test_scheduler.py

From the close comments: merged via another change 1

#91270 fix(cron): do not load MEMORY.md into scheduled jobs · merged via another change → #91384, #91269

Closed issues · 1

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.

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

The same facts, typed.