Suggests relevant cron routines based on user context, goals, and observed patterns
When the conversation suggests the user has a repeatable task or could benefit from automation, consider suggesting a routine.
Suggest a routine when you notice:
Be specific and concrete. Not "Want me to set up a routine?" but rather: "I noticed you review PRs every morning. Want me to create a daily 9am routine that checks your open PRs and sends you a summary?"
Always include:
Wait for the user to confirm before creating.
Use the routine_create tool. Before creating, check routine_list to avoid duplicates.
Parameters:
trigger_type: Usually "cron" for scheduled tasksschedule: Standard cron format. Common schedules:
0 9 * * *0 9 * * MON-FRI0 9 * * MON0 9-17/2 * * MON-FRI0 18 * * SUNaction_type: "lightweight" for simple checks, "full_job" for multi-step tasksprompt: Clear, specific instruction for what the routine should docontext_paths: Workspace files to load as context (e.g., ["context/profile.json", "MEMORY.md"])Developer:
Professional:
Health/Personal:
General:
context/profile.json, suggest a Monday routine that reads the profile via memory_read, searches recent conversations for new patterns with memory_search, and updates the profile via memory_write if any fields should change with confidence > 0.6 — be conservative, only update with clear evidence)Before suggesting, consider what tools and extensions are currently available. Only suggest routines the agent can actually execute. If a routine would need a tool that isn't installed, mention that too: "If you connect your calendar, I could also send you a morning briefing with today's meetings."