Show HN: Daymon – Open-source app that gives Claude scheduled tasks(github.com)
github.com
Show HN: Daymon – Open-source app that gives Claude scheduled tasks
https://github.com/daymonio/daymon
11 comments
[deleted]
Just curious, is there any risk of Anthropic detecting this and banning the account?
Daymon uses Claude CLI, which is Anthropic's own official tool. Running claude -p "prompt" is exactly what it's designed for. MCP is also their own protocol. You're not scraping, reverse-engineering, or bypassing authentication.
How is this different from just writing a bash script with cron + claude CLI?
That's exactly how I started. It works for one or two tasks. Then you want session continuity so runs build on each other. Then you want different system prompts for different tasks. Then you want to see run history, retry failures, pause schedules. Then you want one task's knowledge available to another. Daymon is what that bash script evolves into after you get tired of duct-taping it together.
What stops Anthropic from just building this and killing your project?
Nothing. They probably will, eventually. But their consumer business model relies on session limits pushing users from Pro ($20) to Max ($200). Native scheduling would directly undermine that — if Claude can queue work across your idle time, there's less reason to upgrade. I think that conflict of interest delays it longer than people expect. And if they do ship it? Great, the problem gets solved either way. Until then, Daymon exists.
Tools like OpenClaw exist, but they run on API calls. If you're already paying $20/mo for Pro or $200/mo for Max, why pay again per token? Heavy automation on the API can easily hit $100–2,000+/month on top of your subscription.
Daymon works with your existing Claude subscription. No API keys, no per-token billing. It's a Mac desktop app that connects to Claude via MCP. You install it, and Claude gains new capabilities: Task scheduling — cron, one-time, or on-demand. "Summarize my inbox every morning at 8" just works. Session continuity — scheduled tasks resume previous sessions, so a daily research task builds on yesterday's work. Workers — named agent configs with system prompts. Set up a "Research Analyst" or "Code Reviewer" and assign tasks to them. File watchers — trigger actions when files change in a directory. The name is a nod to Unix daemons — background processes that run without user interaction.
Tasks get smarter every time they run. First run, Claude figures out the approach from scratch — that might take 30 seconds. By the third run, session continuity means it already knows what worked. Same task, 4 seconds. You don't configure anything. It just happens because each run builds on the context of previous ones.
When you hit your session limit and Claude tells you to come back later, you don't have to stop. Say "schedule this to continue" and Daymon queues it up.
Everything runs locally. Tasks execute via claude -p "prompt" as subprocesses. MIT licensed.
Stack: Electron, TypeScript, React, Tailwind, better-sqlite3, node-cron, chokidar, MCP SDK.
Limitations: Mac only for now (Linux planned). Requires Claude CLI. DMG is ~250MB due to Electron. Early stage, solo developer. On whether Anthropic will build this natively: Probably, eventually. But their consumer model relies on session limits to push users from Pro to Max. Native scheduling would undermine that — if Claude can queue work across your limit window, there's less pressure to upgrade. Your subscription sits idle every time you close the tab, and that idle time is arguably working as intended. Daymon exists because I don't think you should have to wait for them to figure out their incentives.
Would love feedback on the architecture and what you'd want to see next.