Bug Summary

cron.add tool has inconsistent parameter handling - sometimes accepts the job as a JSON string, sometimes rejects it with 'must be object'

Details

• The first call worked: {"name": "test-reminder", "schedule": {"at": "2026-01-25T17:03:00Z"}, "sessionTarget": "main", "payload": {"kind": "systemEvent", "text": "⏰ Recordatorio de prueba"}}
• Identical subsequent calls fail with error 'job: must be object'
• Inconsistent behavior - the same format sometimes works, sometimes doesn't
• The error message says 'must be object' but the job IS being passed as an object (JSON stringified)

Environment

• Running on Windows (possible platform-specific bug)
• Using cron tool from the main agent session

Reproduction

The issue is intermittent and hard to reproduce consistently.