Here's a problem you'll run into. By default, cron jobs run inside your active session and share its context. This can cause issues when a long-running conversation pollutes the cron job's prompt with irrelevant history.
The fix? Add --session isolated to give each cron run a fresh context window. Isolated sessions start with only MEMORY.md and today's daily file loaded. They don't carry over conversation history from previous runs or your active session. Use isolated mode for jobs that should produce consistent output regardless of what you were doing when they fire.