jobs

Manage cron jobs for the heartbeat daemon. Use $ARGUMENTS to determine the action.

Resolving the jobs directory

Read .claude/claudeclaw/settings.json. If the jobsDir field is set, use that path (resolve relative paths against the project root). Otherwise use the default: .claude/claudeclaw/jobs/.

CRITICAL: Job files MUST live under the project-relative jobs directory, NOT under ~/.claude/claudeclaw/jobs/. The daemon only watches the project directory. Using the home directory path will silently fail — the job will never fire.

Parse $ARGUMENTS to identify the sub-command. If no arguments are given, list all jobs.

Sub-commands

list (default when no arguments)

1. List all .md files in the jobs directory.
2. For each file, read it and display:
   • Job name (filename without .md)
   • Schedule (cron expression from frontmatter)
   • Notify (true, false, or error — from frontmatter, default true)
   • Prompt (body text, truncated to 100 chars if long)
3. If no jobs exist, tell the user and show how to create one.

create or add

Create a new cron job interactively.

1. Use AskUserQuestion to ask:

   • "What should this job be called?" (header: "Job name", options: suggest 2 contextual names based on the project, e.g. "git-summary", "test-runner")
   • "When should it run?" (header: "Schedule", options: "Every hour (0 * * * *)", "Every 6 hours (0 */6 * * *)", "Daily at 9am (0 9 * * *)", "Daily at midnight (0 0 * * *)")

2. Then ask:

   • "What prompt should Claude execute?" (header: "Prompt", options: suggest 2-3 prompts relevant to the project context)
   • "Should this job send notifications?" (header: "Notify", options: "Always (default)", "Errors only", "Never")

3. Create the job file at <jobs-directory>/<name>.md with this exact format:

   ---
   schedule: "<cron expression>"
   notify: <true|error|false>
   ---
   <prompt>
   

   Map the notify answer: "Always" → true, "Errors only" → error, "Never" → false. Omit the notify line if the user chose "Always" (it's the default).