@clize/clize 0.9.1 → 0.10.0

package/README.md

@@ -1,6 +1,6 @@
 # Clize
 
-**The real-world capability layer for AI agents.** Your agent already has a brain — Clize gives it hands: a domain, a working inbox, a live website. One CLI (plus an MCP server) so coding agents in Claude Code / Codex can register domains, run real email, design & ship sites, generate media, and collect payments from their customers.
+**The real-world capability layer for AI agents.** Your agent already has a brain — Clize gives it hands: a domain, a working inbox, a live website. One CLI (plus an MCP server) so coding agents in Claude Code / Codex can register domains, run real email, build & ship sites and short clips, generate media, and collect payments from their customers — across as many projects as you run.
 
 → **[clize.ai](https://clize.ai)**
 
@@ -24,9 +24,11 @@ clize update            # or `clize update --check` to only check for a newer ve
 Log in and go — your agent never touches Cloudflare:
 
 ```bash
-clize login                       # GitHub authorize → creates your account, saves a clize key
+clize login                       # browser authorize → creates your account, saves a clize key
 clize check                       # ✓ connected to the hosted backend
-clize claim acme                  # free handle: acme.clize.app (+ support@ inbox)
+clize claim acme                  # free handle: acme.clize.app (+ support@ inbox, already receiving)
+clize init --handle acme          # bind this directory — deploy / email send infer domain & from
+clize deploy ./site               # ship a static site → https://acme.clize.app
 clize status                      # who's waiting, this month's spend
 clize email inbox acme.clize.app  # read what customers sent
 ```
@@ -38,18 +40,27 @@ clize email inbox acme.clize.app  # read what customers sent
 | **Hosted** (recommended) | `clize login` (GitHub) — or `clize login --api <url> --token clize_…` if you already have a key | Commands call the clize backend; resources run on clize's infra. You never handle Cloudflare. |
 | **Self-host** (bring your own Cloudflare) | `clize login --token <CF_API_TOKEN> --account <CF_ACCOUNT_ID>` | Commands run locally against *your* Cloudflare account. |
 
-Hosted mode covers the full core — `status · check · context · balance · recharge · claim · domain search|list|buy · deploy · design · gen image|video|music · audit · email inbox|show|thread|send · pay connect|link|status|list`. Self-host adds custom-domain email plumbing (`domain import`, `email setup` / `inbox-setup` / `route` / `webhook` / `address`) and `release`.
+Hosted mode covers the full surface — everything in the table below, **including** custom-domain email (`domain import` · `email setup` / `inbox-setup` / `route` / `webhook` / `address`) and `release`.
+
+Hosted-mode specifics to know before you hit them:
+
+- `clize deploy <dir>` and `clize email send` need `--domain` / `--from` — unless the directory is bound with `clize init --handle <slug>`, which lets both be inferred from `./clize.json` (same as local mode). `--html` single-page deploys are local-only.
+- `gen image --ref/--mask` (reference image / mask) and `gen budget` pre-approval are local-only for now — hosted confirms each generation with `--confirm`.
+
+Self-host needs a Cloudflare API token + Account ID (dashboard → overview, right column). Scope the token to what you'll use: Zone **DNS** + **Email Routing** (email), Account **Workers Scripts** (deploy), Account **Registrar** (domain buy). Run `clize check` to verify connectivity. Free `*.clize.app` handles are allocated by the hosted side — self-host uses your own domains (`clize domain import`).
 
 ## What it does
 
 | Area | Commands |
 |---|---|
-| **Claim** | `clize claim <slug>` — first-come, free `<slug>.clize.app` handle with inbox + site in one shot |
+| **Claim** | `clize claim <slug>` — first-come, free `<slug>.clize.app` handle with inbox + site in one shot (`support@` is already receiving — no extra email setup needed) |
 | **Domains** | `clize domain search / tlds / buy / import / list` |
 | **Email** | `clize email setup` → `inbox-setup` → `address add` (`--tag` / `--knowledge`) wires a real send/receive inbox on your domain — or get `support@` instantly with `clize claim`. Then `send` (`--attach`) / `inbox` / `show` / `thread` / `route` / `webhook`. (`address add` only stores tag + knowledge; `inbox-setup` is what opens receiving.) |
 | **Media** | `clize gen image / video / music` — text→image (`gpt-image-2` / `nano-banana-2`), text/image→video (`veo`), text→music (`suno`); long tasks via `gen jobs / status`, spend-gated via `gen budget`. Results land as local files, ready to `deploy` or `email --attach`. |
-| **Design** (hosted) | `clize design start <brief>` — a hosted design system that briefs your agent on a cohesive style *before* it builds, so sites land with taste instead of AI-template sludge. Then `design recommend / list / get / review` for styles + a self-review checklist. |
-| **Deploy** | `clize deploy <dir> --domain <host>` — multi-file static sites; free `*.clize.app` or your own domain |
+| **Build · site** (hosted methods) | `clize build site start <brief>` — a hosted design system that briefs your agent on a cohesive style *before* it writes the site, so pages land with taste instead of AI-template sludge. Then `build site recommend / list / get / search / review` + `build site stack <stack>` for stack-specific guidance (React / Next / SwiftUI / …). The former `clize design …` spelling still works as a hidden alias. |
+| **Build · clip** (hosted methods) | `clize build clip start <brief>` → your agent writes a shot-by-shot blueprint → `build clip check` (free local lint: continuity, dialogue coverage, timing) → `build clip render --confirm` (💰 one summed quote, batch-generate + merge, resumable). One-off footage stays `gen video`. |
+| **Deploy** | `clize deploy <dir> --domain <host>` — multi-file static sites; free `*.clize.app` or your own domain. Preview locally first with `clize serve <dir>` (proper `Range` support — `<video>` pages actually play in Safari). |
+| **Projects** | One project = one directory: `clize init --handle <slug>` binds it (the project record auto-creates on first `claim` / `buy`). `clize projects` to list / `new` / `move` / `rename` / `rm`; `-p <slug>` for one-off cross-project calls; guardrails block sending or deploying with another project's identity (409). `status` / lists / spend all scope to the checked-out project. |
 | **Context** | `clize status [--assets]`, `clize context [address]` — rehydrate who's waiting + identity/knowledge at the start of a session |
 | **Billing** (hosted) | `clize balance` / `clize recharge --amount <usd>` — prepaid clize balance that domain/media spends draw from (Stripe top-up); `clize audit` for the spend log |
 | **Collect** (hosted) | `clize pay connect` → `clize pay link --amount <usd> [--mode direct\|balance]` — bill *your* customers: money lands in your own Stripe (`direct`, clize takes a fee) or your clize balance (`balance`, no fee). `clize pay status` / `clize pay list`. |
@@ -66,7 +77,7 @@ These gates run in plain text, so every spend and every outbound action is visib
 
 ## MCP
 
-A curated subset of the core — domains, email, deploy, claim, status/context, billing, collect (`pay`) — exposed as MCP tools for hosts that prefer structured tools over a shell. (Media generation and the design system stay CLI- and skill-driven, not MCP tools.) Opt-in (`clize install --mcp`), since an MCP server's tool list is a standing per-session context cost — the skill alone already lets the agent drive clize via the CLI. To register by hand:
+A curated subset of the core — domains, email, deploy, claim, status/context, billing, collect (`pay`) — exposed as MCP tools for hosts that prefer structured tools over a shell. (Media generation and the `build` method packs stay CLI- and skill-driven, not MCP tools.) Opt-in (`clize install --mcp`), since an MCP server's tool list is a standing per-session context cost — the skill alone already lets the agent drive clize via the CLI. To register by hand:
 
 ```bash
 claude mcp add clize -- clize-mcp     # Claude Code