Abdelhak Akermi

ClawTick - Cron jobs for AI agents w/ one command, zero infrastructure

ClawTick is a cloud scheduler built specifically for AI agents. Schedule LangChain, CrewAI, or webhook tasks with one CLI command. Get built-in monitoring, failure alerts, automatic retries, and execution logs — without managing servers or writing cron infrastructure. CLI for agents, dashboard for humans. Free tier included

Add a comment

Replies

Best
Abdelhak Akermi
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.
Christian Knaut

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?

Abdelhak Akermi

@christian_knaut Yep, all built in! Every job gets per-run logs (status, duration, errors) and email alerts on failure. Plus a circuit breaker that auto-disables after 3 consecutive failures so you don't burn credits overnight. Zero setup needed, it just works out of the box.

Vivek Kumar

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.

Abdelhak Akermi
@vivek_warrant appreciate that that “one command, zero infra” framing is exactly the gap i kept running into too. and yeah, traceability was important to me from the start. every scheduled run keeps its own identity through execution, so you can follow what happened later instead of it becoming a black-box cron fire. trying to make agent scheduling feel production-ready rather than “hope it worked” 😅
Jimmy Lee

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.

Abdelhak Akermi

@jimmy_lee12 100% agree. Silent failures are the real killer in production. That's exactly why we built the circuit breaker and email alerts as defaults, not add-ons. Logs and retry behavior should just be there from day one without extra config

Samir Asadov

"CLI for agents, dashboard for humans" is the cleanest way to position this — the moment scheduling has to happen, you want CLI; the moment you want to know what fired and what failed, you want UI. We hit the same split on PolyMind, which polls Polymarket trades and pushes alerts: the trigger logic lives in scripts (CLI-shape), but the human side wants a panel showing "what fired in the last hour and was it noise." One thing I'm curious about — do you treat retry-with-exponential-backoff as a knob the agent author sets per job, or as a global default with override? Most failure modes I've seen in scheduled-AI come from wrong defaults, not missing features.

Abdelhak Akermi

@samir_asadov Great question Samir! Right now retry is global (circuit breaker after 3 failures). But "global default with per-job override" is exactly where I'm headed. You're right that most failures come from wrong defaults, not missing features.Curious about PolyMind, how do you handle the signal vs noise threshold on that panel?