Remove or improve CronCreate tool - creates unreliable session-only cron jobs

Problem Description

The CronCreate tool creates session-only cron jobs that are unreliable and confusing for users. These jobs:

• Live only in memory during the Claude session
• Do not persist across session restarts
• Fail silently when sessions end
• Are not visible in any scheduler database
• Provide no execution logs or error tracking
• Create false expectations about scheduled task reliability

User Impact

Users schedule important tasks (like sending emails) expecting them to execute reliably, but:

• Jobs fail silently with no error messages
• No execution history available
• No way to monitor or debug failures
• Creates distrust in the scheduling system
• Wastes user time troubleshooting invisible issues

Actual Example

Today I scheduled a cron job to send an email at 1:45 PM:

• Created: 1:34 PM via CronCreate
• Expected execution: 1:45 PM
• Actual result: Never executed
• Evidence: No email sent, no logs, no errors
• Root cause: Session-only job failed silently

Better Alternative

The MyClaw Scheduler (via mcp__myclaw__scheduler_upsert_job) provides:

• ✅ Persistent jobs across sessions
• ✅ Execution history tracking
• ✅ Retry logic for failures
• ✅ Visible in scheduler database
• ✅ Proper error handling
• ✅ Job monitoring and management

Suggested Solutions

Option 1: Remove CronCreate entirely

• Remove the unreliable tool completely
• Direct users to use proper scheduler systems
• Prevent confusion and failures

Option 2: Improve CronCreate significantly

• Make jobs persistent by default
• Add proper error handling and logging
• Show warnings about session-only nature
• Integrate with existing scheduler databases
• Add execution monitoring
• Provide failure notifications

Option 3: Add clear warnings

• Warn users that jobs are session-only
• Suggest alternatives for persistent jobs
• Document limitations clearly
• Add failure detection and notifications

Reproduction Steps

1. Use CronCreate to schedule a task
2. Wait for scheduled time
3. Observe: Task never executes
4. Check: No logs, no errors, no evidence

Expected Behavior

Scheduled tasks should:

• Execute reliably at scheduled times
• Provide execution confirmation
• Log successes and failures
• Survive session restarts
• Be monitorable and debuggable

Environment

• Claude Code (latest version)
• CronCreate tool
• Session: 2026-04-20
• Timezone: Asia/Calcutta (IST)

Priority

High - This affects user trust in scheduling functionality and causes silent failures of important tasks.

---

Workaround: Use mcp__myclaw__scheduler_upsert_job instead for reliable persistent scheduling.