cron-claude 2.2.0 → 2.2.1

package/README.md

@@ -46,7 +46,9 @@ cron-claude skill install    # just the slash commands
 
 ```
 cron-claude list
-cron-claude add --id <id> --schedule "<cron>" --prompt "<prompt>" [--model <model>] [--disabled]
+cron-claude add --id <id> --schedule "<cron>" --prompt "<prompt>" [--prompt-file <path>] [--model <model>] [--disabled]
+cron-claude edit <id> [--schedule "<cron>"] [--prompt "<prompt>"] [--prompt-file <path>] [--model <model>] [--enable] [--disable]
+cron-claude show <id>
 cron-claude remove <id>
 cron-claude enable <id>
 cron-claude disable <id>
@@ -65,10 +67,42 @@ cron-claude mark-job-run <id> [--output <text>] [--error <text>]  # mark job com
 |------|----------|---------|-------------|
 | `--id <id>` | ✅ | — | Unique job identifier |
 | `--schedule "<cron>"` | ✅ | — | Cron expression (5-field: `min hour day month weekday`) |
-| `--prompt "<prompt>"` | ✅ | — | Prompt sent to the subagent |
+| `--prompt "<prompt>"` | ✅* | — | Inline prompt text (mutually exclusive with `--prompt-file`) |
+| `--prompt-file <path>` | ✅* | — | Path to a `.md`/`.txt` file containing the prompt (mutually exclusive with `--prompt`) |
 | `--model <model>` | — | `sonnet` | Model for the job |
 | `--disabled` | — | `false` | Create in disabled state |
 
+*One of `--prompt` or `--prompt-file` is required.
+
+### `edit` flags
+
+Edit a job in place — only the flags you provide are updated; everything else stays as-is.
+
+```bash
+cron-claude edit my-job --schedule "0 10 * * *"
+cron-claude edit my-job --prompt "New prompt text"
+cron-claude edit my-job --prompt-file ./prompts/daily.md --model opus --enable
+```
+
+| Flag | Description |
+|------|-------------|
+| `--schedule "<cron>"` | New cron schedule |
+| `--prompt "<prompt>"` | New inline prompt (clears `--prompt-file` if set) |
+| `--prompt-file <path>` | New prompt file path (clears inline prompt if set) |
+| `--model <model>` | New model |
+| `--enable` | Enable the job |
+| `--disable` | Disable the job |
+
+### `show`
+
+Show full details of a single job, including the **complete untruncated prompt**. If the job uses a prompt file, shows the file path and its contents.
+
+```bash
+cron-claude show my-job
+```
+
+`list` truncates prompts to 40 characters — use `show` to see the full text.
+
 ### Cron schedule examples
 
 | Expression | Meaning |
@@ -92,6 +126,8 @@ Available when the MCP server is installed:
 | `enable_cron` | Enable a job |
 | `disable_cron` | Disable a job |
 | `list_crons` | List all jobs (JSON) |
+| `edit_cron` | Edit a job in place (partial update — only provided fields change) |
+| `show_cron` | Show full details of a single job including complete prompt/file contents |
 | `get_status` | Job counts (total, enabled, disabled, running) |
 
 ## Job State & Duplicate Prevention
@@ -125,13 +161,15 @@ When `/cron-loop` is invoked, Claude Code:
 
 ## Editing a Job
 
-There's no edit command. Remove and re-add:
+Use `edit` to modify a job in place — only the fields you specify are changed:
 
 ```bash
-cron-claude remove my-job
-cron-claude add --id my-job --schedule "0 10 * * *" --prompt "New prompt"
+cron-claude edit my-job --schedule "0 10 * * *"
+cron-claude edit my-job --prompt "New prompt" --model opus
 ```
 
+Or via MCP: call `edit_cron` with the job ID and any fields to update.
+
 ## For Claude
 
 If you're an AI agent reading this README:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cron-claude",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "description": "Schedule Claude jobs in agent loop mode — no daemon, full tool access",
   "type": "module",
   "main": "dist/cli.js",