Agents Cron

Standard AI agents are reactive, waiting for a prompt before they act. This skill enables scheduled and recurring agent execution within your local development environment, letting you automate code audits, documentation updates, or status reports without manual intervention.

What it does

• Schedule prompt execution by storing prompts with specific time rules for later or recurring runs.
• Manage task lifecycle through commands to add, enable, disable, or remove tasks in a project-scoped store.
• Inspect run history via a local dashboard that tracks summaries, errors, and session records for every execution.
• Multi-agent support allows tasks to run through Pi, Claude Code, or Codex adapters.
• Granular time control supports ISO timestamps, duration intervals, and standard cron expressions.

How it works

1. Define the task using commands like /loop, /remind, or /schedule followed by your prompt and timing.
2. Assign an agent to handle the task, such as pinning a headless Claude Code session for code-intensive work.
3. External trigger occurs when your system's scheduler calls the CLI to execute due tasks.
4. Monitor via dashboard by launching the local web view to debug failures or review successful completions.

Frameworks & tools

Built for Node.js (v22.19+) environments. Integrates with the agents-cron CLI and supports agent adapters for Pi, Claude Code, and Codex.

Why this beats prompting it yourself

Manually running the same maintenance prompts every morning is a waste of developer time. This skill provides a structured persistence layer and CLI for prompts, ensuring background tasks run reliably and providing a centralized dashboard to audit the results across multiple agent types.

Use cases

• Schedule a daily code quality audit every morning at 8 AM.
• Remind an agent to check for outdated dependencies every Monday.
• Run a recurring documentation sync between source code and README files.
• Automate a project status summary for delivery every Friday afternoon.

Known limitations

Execution requires an external scheduler (like system cron) to invoke the CLI. Headless Claude Code tasks require an explicit tool allowlist to bypass interactive permission prompts.