openclaw - 💡(How to fix) Fix Cron job messages not accessible from agent's main session context [1 participants]

Problem

When a cron job runs, it executes in an isolated session. Any information the agent discovers during that cron execution (e.g., scanning emails, finding comments, checking statuses) is not visible to the agent when operating in the main session.

This creates a disconnect: the agent can find information via cron but can't act on it or reference it later in the main chat.

Steps to Reproduce

1. Create a cron job that scans for something (e.g., email comments, RSS feeds)
2. Let the cron job run and discover new items
3. Start a new main session conversation
4. Ask the agent about items discovered by the cron job
5. The agent has no memory or context of what the cron job found

Expected Behavior

The agent should be able to access context from cron job executions, either through:

• Shared session state
• Automatic memory injection from cron results
• A way to read cron job output files

Actual Behavior

Cron jobs run in complete isolation. The agent must manually read output files to see what cron jobs discovered, and there's no automatic way to bridge this context gap.

Additional Context

This is particularly problematic for monitoring tasks (email scanning, comment monitoring, RSS feeds) where the cron job's discovery should trigger agent actions in the main session.

I've been running several cron jobs (newsletter scanning, comment monitoring) and discovered that when the cron finds something, I can't act on it in the main session without manually reading the output files first.