@letterstory/cli 0.176.52 → 0.176.53

package/lib/cli.mjs

@@ -85,7 +85,7 @@ import {
 import { fetchParkedSections, withoutParked } from "./parked.mjs";
 
 // Matches cli/package.json; publish-cli.yml rewrites both to the published version.
-export const VERSION = "0.176.52";
+export const VERSION = "0.176.53";
 
 /** The exit code for a gate refusal (CARD_REQUIRED, PAYMENT_FAILED, OUT_OF_TOKENS): 1 is a plain error. */
 export const EXIT_PAYMENT_REQUIRED = 3;
@@ -117,10 +117,12 @@ export const BOOLEAN_FLAGS = new Set([
 	"keep-key",
 	"delete-key",
 	"keep",
-	// automate add/set: on or off; only identified visitors marked hot leads.
+	// automate add/set: on or off; only identified visitors marked hot leads; run the prompt in a Build sandbox.
 	"on",
 	"off",
 	"hot-leads-only",
+	"sandbox",
+	"no-sandbox",
 	// admin crm prospect-org: start (or retry) the org prepared for the booked call.
 	"start",
 	// site research-builds: run now even when the stored pass is under an hour old.
@@ -136,6 +138,8 @@ export const BOOLEAN_FLAGS = new Set([
 	// build: repeat an open build's ask; post its progress in the org's Slack channel.
 	"again",
 	"plan-only",
+	// build: every change reads Letter's tools from its sandbox.
+	"primitives-access",
 	// build list: only Build's Archived tab (--open, already listed, is its Open tab).
 	"archived",
 	// plan pending --queued: only the rows a person queued for later.
@@ -633,17 +637,22 @@ Reviewers:
   automate list                                        Your automations: an event, which ones it acts on,
                                                        and what Letterpress then does
   automate show <automation-id>
-  automate add [--template post_new_issues|recommended_actions|competitor_pages|icp_visitors|vc_visitors|plan_updates]
-               [--name <n>] [--trigger competitor_page|visitor_identified|issue_found|build_suggestion|plan_update|custom]
+  automate add [--template post_new_issues|fix_new_issues|recommended_actions|competitor_pages|competitor_takes|
+                           icp_visitors|vc_visitors|plan_updates|weekly_release_notes|monthly_page_refresh]
+               [--name <n>] [--trigger competitor_page|visitor_identified|issue_found|build_suggestion|plan_update|custom|schedule]
                [--prompt <what Letterpress does with each event>] [--slack-channel <C…>] [--instruction <which events>]
                [--event <name>] [--kind post|landing] [--competitor <host>] [--site <host>]
+               [--every <n> --unit hours|days|weeks|months] [--sandbox]
                [--hot-leads-only] [--per-day <n>] [--backfill all|<YYYY-MM-DD>] [--off]
                                                        Make one (a template fills what you leave out): it starts
                                                        from now (--backfill also runs it on past events, oldest
                                                        first), acts on its own, and posts each event it acts on
-                                                       to --slack-channel with its buttons
+                                                       to --slack-channel with its buttons. --trigger schedule
+                                                       --every 2 --unit weeks is a recurring one (on the calendar:
+                                                       Monday, the 1st); --sandbox always runs its prompt in a Build
+                                                       sandbox (off, Letterpress decides per event)
   automate set <automation-id> [--name <n>] [--instruction <text>] [--prompt <text>] [--slack-channel <C…>|none]
-               [--backfill all|<YYYY-MM-DD>] [--on|--off] ...
+               [--sandbox|--no-sandbox] [--backfill all|<YYYY-MM-DD>] [--on|--off] ...
   automate try [<automation-id>] [--trigger <t> --prompt <text> --instruction <text> ...] [--limit <n>]
                                                        What it would do with the latest events (acts on none)
   automate runs [--automation <id>] [--status acting|acted|skipped|failed|proposed|rejected] [--limit <n>]
@@ -1726,6 +1735,7 @@ Build (a change to your site, or launching what isn't code; the Build box's own
   build <words…> [--prompt <text>] [--site <host>] [--subject <host/path>]... [--action build|build_pr|build_merge|slack|linear]
              [--attach <path>]... [--attach-url <name>=<https url>]... [--attach-ref <path>]... [--attach-url-ref <name>=<https url>]...
              [--harness letterpress-1|claude-code|codex] [--effort low|medium|high|xhigh] [--notify-slack] [--again] [--new-site]
+             [--primitives-access]
                                                        Build from your words: "add a pricing page" opens a preview or PR;
                                                        "launch a phantom for us", "set up mailers" or "onboard my blog" is
                                                        done by Build itself (a phantom site buys its own domain), and the

package/lib/commands/automate.mjs

@@ -7,15 +7,28 @@
 import { CliError } from "../client.mjs";
 import { printResult, ok, argsFromFlags, flagList, flagStr, refuseUnknownFlags } from "./shared.mjs";
 
-const TRIGGERS = ["competitor_page", "visitor_identified", "issue_found", "build_suggestion", "plan_update", "custom"];
+const TRIGGERS = [
+	"competitor_page",
+	"visitor_identified",
+	"issue_found",
+	"build_suggestion",
+	"plan_update",
+	"custom",
+	"schedule",
+];
 const TEMPLATES = [
 	"post_new_issues",
+	"fix_new_issues",
 	"recommended_actions",
 	"competitor_pages",
+	"competitor_takes",
 	"icp_visitors",
 	"vc_visitors",
 	"plan_updates",
+	"weekly_release_notes",
+	"monthly_page_refresh",
 ];
+const UNITS = ["hours", "days", "weeks", "months"];
 const STATUSES = ["pending", "proposed", "acting", "acted", "skipped", "failed", "rejected"];
 
 const triggerParams = {
@@ -26,8 +39,15 @@ const triggerParams = {
 		hot_leads_only: { flag: "hot-leads-only", type: "bool" },
 		event: { flag: "event" },
 		per_day: { flag: "per-day", type: "num" },
+		// --trigger schedule --every 2 --unit weeks: a recurring automation, on the calendar (Monday, the 1st).
+		every: { flag: "every", type: "num" },
+		unit: { flag: "unit", enum: UNITS },
 	},
 };
+// --sandbox / --no-sandbox: always run the prompt in a Build sandbox (the repo and Letter's tools); off, Letterpress decides per event.
+const sandbox = {
+	value: (flags) => (flags["no-sandbox"] === true ? false : flags.sandbox === true ? true : undefined),
+};
 // --slack-channel C0123ABCD (repo slack-targets), or none to post nothing.
 const slackChannel = {
 	value: (flags) =>
@@ -96,6 +116,7 @@ export const ARGS = {
 		instruction: { flag: "instruction" },
 		prompt: { flag: "prompt" },
 		slack_channel: slackChannel,
+		sandbox,
 		enabled,
 		backfill,
 	},
@@ -108,6 +129,7 @@ export const ARGS = {
 		instruction: { flag: "instruction" },
 		prompt: { flag: "prompt" },
 		slack_channel: slackChannel,
+		sandbox,
 		enabled,
 		backfill,
 	},

package/lib/commands/build.mjs

@@ -50,6 +50,8 @@ const ARGS = {
 		files: { value: (_flags, _positionals, extra) => (extra.files?.length ? extra.files : undefined) },
 		delivery: { flag: "action", enum: ["build", "build_pr", "build_merge", "slack", "linear"] },
 		notify_slack: { flag: "notify-slack", type: "bool" },
+		// --primitives-access: every change reads Letter's tools from its sandbox (a read-only MCP key beside the repo).
+		primitives_access: { flag: "primitives-access", type: "bool" },
 		harness: { flag: "harness", enum: ["letterpress-1", "claude-code", "codex"] },
 		// --branch <name>: where its changes start and its pull requests go; omitted, the branch that builds the site.
 		base_branch: "branch",

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@letterstory/cli",
-	"version": "0.176.52",
+	"version": "0.176.53",
 	"description": "Spin up and manage Letter phantom blogs from your terminal.",
 	"type": "module",
 	"license": "UNLICENSED",