ClawTick

Cron jobs for AI agents make sense because the boring scheduled work is usually where agents become useful. I’d want strong logs and retry behavior more than fancy setup, since silent failures are the part that hurts in production.

Scheduling AI agents is way harder than it looks - cron is simple enough but retry logic, timeouts, and observability turn into a mess fast. Does ClawTick give you per-job logs and failure alerts out of the box, or is that somthing you wire up yourself?

this is the layer i didn't realize i needed. the "one command, zero infra" framing matters because most agent-cron approaches assume you already have a scheduler running somewhere.quick q: when a cron fires and the agent does work, do you carry the cron run id through to the agent's downstream tool calls, or does it get lost? curious how you handle that for traceability.

Hey PH!
I'm Abdelhak, solo founder of ClawTick.

I built this because I was running AI agents that needed to fire on a schedule — daily reports, periodic data checks, automated follow-ups. The options were: manage my own cron on a VPS, or glue together EventBridge + Lambda + monitoring + alerting myself.

Both felt like too much infrastructure for what should be a simple problem: "run this thing every day at 9am and tell me if it breaks."

So I built ClawTick. One CLI command to schedule a job. Built-in monitoring, failure alerts, and automatic retries. A dashboard to see what's running. No servers to maintain.

It's designed to be agent-friendly — minimal tokens to schedule tasks programmatically, so your AI agents can create their own schedules without burning context.

Free tier: 10 jobs, 1,000 triggers/month. Would love your feedback on what to build next.