hermes - 💡(How to fix) Fix cron: skip_memory=True blocks fact_store/memory tools from all cron jobs [1 pull requests]

Problem

The cron scheduler hardcodes skip_memory=True for all cron jobs:

# cron/scheduler.py line 1652
agent = AIAgent(
    ...
    skip_memory=True,  # Cron system prompts would corrupt user representations
    ...
)

This disables the entire memory system — including the holographic memory provider and its fact_store/fact_feedback tools, plus the memory tool.

Impact

Any cron job that needs to read or write to holographic memory cannot do so. This blocks legitimate use cases like:

• Nightly memory optimisation jobs that mine session history for facts
• Cron jobs that need to check user preferences before acting
• Jobs that discover new routing rules or account info and want to persist them

The current design forces a choice: either all cron jobs run without memory (status quo), or all run with memory (risking "corrupt user representations" as the comment warns).

Proposed fix

Make skip_memory a per-job setting, defaulting to True for backward compatibility. Users who want memory-aware cron jobs can opt in:

# cron job config
memory_enabled: true  # default: false

Or add it as a parameter in the cronjob tool.

Related

• #34084 — holographic memory silently degrades when numpy is missing
• This issue blocks the "Nightly Memory Optimisation" cron job from populating holographic memory with session-derived facts