autowrightlisted

# Autowright Autowright runs the user's personal automations on a schedule, entirely on this Mac. Each automation is: a **spec** (plain-markdown description of what it does), ordered **step scripts** (Python, executed by Autowright's engine), **parameters** (user-editable values), **triggers** (cron / one-shot / on-app-start), per-automation **memory** (files kept between executions), and versioned history. You interact through the `autowright` CLI — every operation the app's UI offers is available there. ## Ground rules 1. **Read the contract first.** Before writing or editing any step code, run `autowright instructions` and follow it — it defines the step SDK (`autowright` module: `secrets["<id>"]`, `params`, `memory`/`workspace` dirs, `result.chip()`, `agent.ask()` / `agents["<id>"]`), the allowed imports (stdlib + curated packages + declared packages), and the engine policies. Do not guess the SDK from memory. Every SDK name a step uses must be imported (`from autowright import params, log, result`) — nothing is a global. 2. **Review before it runs.** Before `automation create`, `automation push`, or the first `automation execute` after a change, show the user a short summary of what you built or changed (spec gist, steps, triggers, secrets used) **and the exact command you will run, including every `--grant-agent`/`--grant-secret` flag**, and get their go-ahead. Grants are explicit (spec §20): create grants nothing by default, push never