ClaudeCron
Health Uyari
- License — License: MIT
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Low visibility — Only 5 GitHub stars
Code Basarisiz
- child_process — Shell command execution capability in scripts/dev/check.js
- spawnSync — Synchronous process spawning in scripts/dev/check.js
- fs module — File system access in scripts/dev/check.js
- child_process — Shell command execution capability in scripts/lib/claude.js
- spawnSync — Synchronous process spawning in scripts/lib/claude.js
- fs module — File system access in scripts/lib/config.js
- fs module — File system access in scripts/lib/log.js
- os.homedir — User home directory access in scripts/lib/paths.js
- process.env — Environment variable access in scripts/lib/paths.js
- child_process — Shell command execution capability in scripts/lib/platforms/macos.js
- spawnSync — Synchronous process spawning in scripts/lib/platforms/macos.js
- fs.rmSync — Destructive file system operation in scripts/lib/platforms/macos.js
- os.homedir — User home directory access in scripts/lib/platforms/macos.js
- process.env — Environment variable access in scripts/lib/platforms/macos.js
- fs module — File system access in scripts/lib/platforms/macos.js
- child_process — Shell command execution capability in scripts/lib/platforms/windows.js
- spawnSync — Synchronous process spawning in scripts/lib/platforms/windows.js
Permissions Gecti
- Permissions — No dangerous permissions requested
Bu listing icin henuz AI raporu yok.
pre-starts Claude sessions on a schedule, helping reduce idle wait time before your next work session.
ClaudeCron
Command-line scheduler for running Claude CLI prompts in the background.
Install
npm i -g claudecron-cli
claudecron
Run Claude CLI login first if Claude is not authenticated yet.
claude auth
Manage Schedule
claudecron
Use the arrow keys to choose Configure Schedule, Run Background, Stop Background, Run once now, or Open log. The menu shows whether the background schedule is on, whether a run is active, the last run time, the next run time, and run counts.
Config Tutorial
On first run, ClaudeCron creates claudecron.config.json in your user app data folder.
Windows:
%APPDATA%\ClaudeCron\claudecron.config.json
macOS:
~/Library/Application Support/ClaudeCron/claudecron.config.json
Use Configure Schedule in the menu for the easiest setup. It opens the real JSON config file; save and close the editor, then choose whether to apply the updated background schedule.
You can also edit the config file manually.
{
"taskName": "ClaudeCron",
"macLabel": "com.claudecron",
"prompt": "hi",
"model": "haiku",
"logFile": "claude-run.log",
"wakeToRun": true,
"runWhenLocked": true,
"schedules": [
{
"days": ["Wednesday", "Thursday"],
"times": ["00:00", "05:00", "10:00", "15:00", "20:00"]
},
{
"days": ["Friday", "Saturday", "Sunday", "Monday", "Tuesday"],
"times": ["00:00", "05:00", "10:00", "15:00", "20:00"]
}
]
}
Use English day names: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday. Use 24-hour HH:mm times. Add another schedule block when different days need different times. Keep "model": "haiku" because the runner enforces Haiku only.
After changing the config manually, run claudecron and choose Run Background so Windows Task Scheduler or macOS launchd is updated.
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi