Automations for Cap Desktop

apps/cli/Cargo.toml

@@ -9,6 +9,7 @@ clap_complete = "4.5.38"
 cap-project = { path = "../../crates/project" }
 cap-recording = { path = "../../crates/recording" }
 cap-export = { path = "../../crates/export" }
+cap-automation = { path = "../../crates/automation" }
 cap-camera = { path = "../../crates/camera" }
 cap-cli-install = { path = "../../crates/cli-install" }
 scap-targets = { path = "../../crates/scap-targets" }
@@ -24,6 +25,7 @@ flume = { workspace = true }
 futures = { workspace = true }
 dirs = "6.0.0"
 image = "0.25.2"
+chrono = "0.4.31"
 tracing.workspace = true
 tracing-subscriber = "0.3.19"
 workspace-hack = { version = "0.1", path = "../../crates/workspace-hack" }

apps/cli/README.md

@@ -81,7 +81,18 @@ step.
 - `cap upload` — upload a `.cap` project or video file and get a shareable link.
 - `cap update` — download and install the latest Cap Desktop bundle, then repair the `cap` shim.
 - `cap doctor` / `version` / `guide` — diagnostics, version info, and the agent capability manifest.
+- `cap automations list` — list the automation rules configured in Cap Desktop that the CLI honors.
 - `cap desktop status|install-cli|uninstall-cli` — manage the `cap` shim on PATH.
 - `cap completions <shell>` — shell completion scripts (bash/zsh/fish/powershell).
 
+## Automations
+
+Automations are `trigger → (conditions) → actions` rules authored in Cap Desktop (Settings →
+Automations) and persisted to its store. Because the CLI shares that store (and the `cap-automation`
+engine), it runs the same rules automatically after `cap screenshot`, a `cap record` finish, and
+`cap upload` — e.g. "on screenshot, save a copy to `~/Shots` and POST a webhook". Clipboard, OCR,
+notification, and open-editor actions are desktop-only and are skipped on the CLI; everything else
+(save, export, upload, run command, webhook, reveal, apply preset, delete) runs. Inspect the active
+rules with `cap automations list --json`.
+
 Run `cap --help` or `cap <command> --help` for full flag documentation.

apps/cli/skill/cap/SKILL.md

@@ -71,6 +71,20 @@ cap upload out.mp4 --json                      # -> {"type":"uploaded","id","lin
 or set `CAP_API_KEY` (a Cap auth key from Settings) for headless use. `cap upload <path.cap> --export
 --json` exports then uploads in one step.
 
+## Automations
+
+Automations are `trigger -> (conditions) -> actions` rules authored in Cap Desktop (Settings →
+Automations) and shared with the CLI. After `cap screenshot`, a `cap record` finish, and `cap upload`,
+the CLI evaluates the matching rules and runs their actions (save to a folder, run a command, send a
+webhook, export, etc.).
+
+```sh
+cap automations list --json   # the rules the CLI will honor
+```
+
+Desktop-only actions (copy to clipboard, OCR, notifications, open editor) are skipped on the CLI; all
+others run. `cap doctor --json` reports the configured rule count under `automations`.
+
 ## Conventions to rely on
 
 - Add `--json` to any command; it overrides each command's `--format`.