setup-agent 0.0.2 → 0.0.4

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 AgentbaseAI Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,9 +1,9 @@
 # setup-agent
 
-One checkout, shared live between the browser that opened it and the coding agent installing its products. The state is a Statewire host (`setup-agent/host`) served from a Cloudflare Durable Object (`apps/checkout-worker`); the CLI (`npx setup-agent <url>`) is a thin Statewire client the agent drives from its shell.
+One setup, shared live between the browser that opened it and the coding agent installing its products. The state is a Statewire host (`setup-agent/host`) served from a Cloudflare Durable Object (`apps/checkout-worker`); the CLI (`npx setup-agent <url>`) is a thin Statewire client the agent drives from its shell.
 
 ```sh
-npx setup-agent <url>              # instructions plus the current checkout
+npx setup-agent <url>              # instructions plus the current setup
 npx setup-agent <url> stream       # one JSON array of events per line; run it under a Monitor
 npx setup-agent <url> wait start   # wait for the user to click Begin plan in their browser
 npx setup-agent <url> log "Sure, I will keep the existing chat route"   # a reply, or something no question or step conveys
@@ -21,13 +21,13 @@ npx setup-agent <url> done --summary "installed the thread and a chat route" --p
 
 ## Phases
 
-A checkout opens `waiting` with its products and nothing else: no steps, no questions. After connecting, the agent tells the user to return to their browser and click **Begin plan**. It keeps the stream running and blocks on `wait start`. The browser sends `checkout/begin-plan`, moving the checkout to `planning` and emitting `planning.started` on the stream. Questions and plan submissions are refused while waiting. When a product needs another one the project lacks, the agent proposes it with `ask "<why>" --product <slug>`; the browser, which owns the catalog, accepts with `checkout/add-product` (the product and its guide join `products`, the input answers `added`) or dismisses the input. In `planning`, the agent investigates the project, asks what the code does not decide, and proposes a markdown plan with `plan` carrying its findings. `log` is for replying to the user and for what no question or step conveys. The user approves the plan or asks for changes with feedback; every revision is kept. Approval moves the checkout to `installing`, where the agent declares its own steps with `add-step` and works through them with `step`. `add-step` and `step` are refused before approval. `done` marks the remaining steps done and proposes closing, with an optional `--summary` and an optional `--preview <url>` naming a dev server the agent left running; a preview must be an http(s) URL on localhost, and the browser offers to open it. `done` does not close. The browser shows the proposal with a close action that sends `checkout/finish`, and the stream prints `finished`. Until then the agent stays idle on the stream, because the user may send a follow-up message; after handling one it runs `done` again to renew the proposal.
+A setup opens `waiting` with its products and nothing else: no steps, no questions. After connecting, the agent tells the user to return to their browser and click **Begin plan**. It keeps the stream running and blocks on `wait start`, which prints `{"ok":true,"status":"planning"}` once planning begins, or `{"ok":false,"status":"cancelled"}` when the user ends the setup first. The browser sends `checkout/begin-plan`, moving the setup to `planning` and emitting `planning.started` on the stream. Questions and plan submissions are refused while waiting. When a product needs another one the project lacks, the agent proposes it with `ask "<why>" --product <slug>`; the browser, which owns the catalog, accepts with `checkout/add-product` (the product and its guide join `products`, the input answers `added`) or dismisses the input. In `planning`, the agent investigates the project, asks what the code does not decide, and proposes a markdown plan with `plan` carrying its findings. `log` is for replying to the user and for what no question or step conveys. The user approves the plan or asks for changes with feedback; every revision is kept. Approval moves the setup to `installing`, where the agent declares its own steps with `add-step` and works through them with `step`. `add-step` and `step` are refused before approval. `done` marks the remaining steps done and proposes closing, with an optional `--summary` and an optional `--preview <url>` naming a dev server the agent left running; a preview must be an http(s) URL on localhost, and the browser offers to open it. `done` does not close. The browser shows the proposal with a close action that sends `checkout/finish`, and the stream prints `finished`. Until then the agent stays idle on the stream, because the user may send a follow-up message; after handling one it runs `done` again to renew the proposal.
 
-The URL is the browser's link to its agent, not one checkout. A finished or cancelled checkout stays on the link, and the browser's next setup replaces it with a new `checkout/create` carrying a new `id`: the plans, steps, inputs and log start over, the agent's presence carries across when it is still connected, and the stream prints `checkout.created` with the new products. The agent keeps the stream running after `finished` or `cancelled` and blocks on `wait start`, which returns once the next checkout begins planning; a checkout already closed when the wait begins is skipped rather than reported.
+The URL is the browser's link to its agent, not one setup. A finished or cancelled setup stays on the link, and the browser's next setup replaces it with a new `checkout/create` carrying a new `id`: the plans, steps, inputs and log start over, the agent's presence carries across when it is still connected, and the stream prints `setup.created` with the new products. The agent keeps the stream running after `finished` or `cancelled` and blocks on `wait start`, which returns once the next setup begins planning; a setup already closed when the wait begins is skipped rather than reported.
 
 ## Inputs
 
-Every input is `text`, `choice` or `model`. A choice carries `options` (`id`, `label`, `description`, `icon`, `variants`), an optional `default` and a `help` note the browser renders as a "help me choose" disclosure. The answer is the option id, `<option>:<variant>` when the option has variants (`langgraph:python`), or the user's own text when none of the options fit; the stream marks that answer `custom`. An agent's own choice is multi-select unless asked with `--single`: the user checks any number of options (none may have variants), and the answer is a JSON array of those entries, which `wait` and the stream print as an array and `status` holds as text. `--single` is for options that exclude each other (one framework, one model, yes or no) and answers one id. Every one of the agent's own options must carry an `icon` from the pack `OPTION_ICONS` exports (`--icons "slack=message,email=mail"`); the CLI refuses the question otherwise. A preset option carries a brand mark instead. Every answer may carry a `note` from the user. A model input lists providers as its options; the browser collects the provider, its API key, the model and an optional reasoning effort, and the answer is that object as JSON (`{"provider","model","reasoningEffort"?}`); the API key is deposited separately and only ever reaches the env file the agent names through `env`.
+Every input is `text`, `choice` or `model`. A choice carries `options` (`id`, `label`, `description`, `icon`, `variants`), an optional `default` and a `help` note the browser renders as a "help me choose" disclosure. Option ids are unique, and neither option nor variant ids may contain `:`. The answer is the option id, `<option>:<variant>` when the option has variants (`langgraph:python`), or the user's own text when none of the options fit (including any text with more than one `:`); the stream marks that answer `custom`. An agent's own choice is multi-select unless asked with `--single`: the user checks any number of options (none may have variants), and the answer is a JSON array of those entries, which `wait` and the stream print as an array and `status` holds as text. `--single` is for options that exclude each other (one framework, one model, yes or no) and answers one id. Every one of the agent's own options must carry an `icon` from the pack `OPTION_ICONS` exports (`--icons "slack=message,email=mail"`); the CLI refuses the question otherwise. A preset option carries a brand mark instead. Every answer may carry a `note` from the user. A model input lists providers as its options; the browser collects the provider, its API key, the model and an optional reasoning effort, and the answer is that object as JSON (`{"provider","model","reasoningEffort"?}`); the API key is deposited separately and only ever reaches the env file the agent names through `env`.
 
 Three standard choices ship as presets (`setup-agent` exports `INPUT_PRESETS` and `presetInput`), so the browser and the CLI agree on their options and brand marks:
 
@@ -35,4 +35,8 @@ Three standard choices ship as presets (`setup-agent` exports `INPUT_PRESETS` an
 - `llm-provider`: OpenAI, Anthropic, Google Gemini, OpenRouter, xAI, Mistral, DeepSeek, Groq, Fireworks AI; defaults to OpenAI. Rendered as the model picker (provider, key, model, reasoning effort).
 - `project`: the React projects the agent found, passed as `--choices "apps/web=Next.js,apps/admin"`, ahead of a fixed "New project" option whose second pick is the meta framework. Answers a path, or `new:<next|vite|react-router|tanstack-start|expo>`.
 
-`--only` restricts a preset to some of its options (a single id locks the choice in) and `--default` preselects one.
+`--only` restricts a preset to some of its options and leaves out `--choices` (a single id locks the choice in) and `--default` preselects one.
+
+## Workspace
+
+The package lives in `packages/setup-agent`; its Cloudflare worker lives in `apps/checkout-worker`. Build the worker dependencies with `pnpm turbo build --filter="checkout-worker^..."`, then run `pnpm --filter checkout-worker dev`. The worker consumes the published `@statewire/cloudflare` adapter.

package/dist/cli.d.ts

@@ -1,64 +1,70 @@
-/// <reference types="node" />
-import { Checkout } from "./protocol.js";
-import { CheckoutClient } from "./client.js";
-//#region src/cli.d.ts
+import type { CheckoutClient } from "./client.js";
+import type { Checkout } from "./protocol.js";
+export declare const HELP: string;
+export declare const INSTRUCTIONS: (url: string) => string;
 type Parsed = {
-  positional: string[];
-  flags: Map<string, string | true>;
+    positional: string[];
+    flags: Map<string, string | true>;
 };
 /** The coding agent this process runs under, from the variables each one exports to its shell. */
-declare const detectAgentKind: (env?: NodeJS.ProcessEnv) => string | undefined;
+export declare const detectAgentKind: (env?: NodeJS.ProcessEnv) => string | undefined;
 /** True when a person typed the command into a terminal rather than an agent running it from its shell. */
-declare const isDirectInvocation: (env?: NodeJS.ProcessEnv, stdin?: {
-  isTTY?: boolean | undefined;
+export declare const isDirectInvocation: (env?: NodeJS.ProcessEnv, stdin?: {
+    isTTY?: boolean | undefined;
 }, stdout?: {
-  isTTY?: boolean | undefined;
+    isTTY?: boolean | undefined;
 }) => boolean;
 type StreamEvent = {
-  event: "planning.started";
+    event: "planning.started";
 } | {
-  event: "message.created";
-  messageId: string;
-  text: string;
+    event: "message.created";
+    messageId: string;
+    text: string;
 } | {
-  event: "input.answered";
-  inputId: string;
-  prompt: string;
-  /** The entries of a multiple choice answer, else the answer text. */
-  answer: string | string[];
-  note?: string;
-  /** True when a choice answer is, or a multiple one contains, the user's own text rather than an option. */
-  custom?: true;
+    event: "input.answered";
+    inputId: string;
+    prompt: string;
+    /** The entries of a multiple choice answer, else the answer text. */
+    answer: string | string[];
+    note?: string;
+    /** True when a choice answer is, or a multiple one contains, the user's own text rather than an option. */
+    custom?: true;
 } | {
-  event: "input.dismissed";
-  inputId: string;
-  prompt: string;
+    event: "input.dismissed";
+    inputId: string;
+    prompt: string;
 } | {
-  event: "plan.approved";
-  revision: number;
+    event: "plan.approved";
+    revision: number;
 } | {
-  event: "plan.changes-requested";
-  revision: number;
-  feedback: string;
+    event: "plan.changes-requested";
+    revision: number;
+    feedback: string;
 } | {
-  event: "finished";
-  next: string;
+    event: "finished";
+    next: string;
 } | {
-  event: "cancelled";
-  next: string;
+    event: "cancelled";
+    next: string;
 } | {
-  event: "checkout.created";
-  products: string[];
+    event: "setup.created";
+    products: string[];
 };
-declare const diffEvents: (before: Checkout.State, after: Checkout.State) => StreamEvent[];
-/** Resolves once a checkout is planning or installing, or once the one being waited on is cancelled; a checkout already closed when the wait begins is over, so the wait is for the next one. */
-declare const waitForStart: (client: Pick<CheckoutClient, "state" | "subscribe">) => Promise<Checkout.Status>;
-declare const askSeed: (rest: readonly string[], flags: Parsed["flags"]) => Checkout.InputSeed & {
-  stepId?: string;
+export declare const diffEvents: (before: Checkout.State, after: Checkout.State) => StreamEvent[];
+/** Resolves once a setup is planning or installing, or once the one being waited on is cancelled; a setup already closed when the wait begins is over, so the wait is for the next one. */
+export declare const waitForStart: (client: Pick<CheckoutClient, "state" | "subscribe">) => Promise<Checkout.Status>;
+export declare const askSeed: (rest: readonly string[], flags: Parsed["flags"]) => Checkout.InputSeed & {
+    stepId?: string;
 };
 /** Sets `key=value` in dotenv text, replacing an existing line for the key. */
-declare const upsertEnvLine: (content: string, key: string, value: string) => string;
-declare const main: (argv: readonly string[]) => Promise<undefined>;
-//#endregion
-export { askSeed, detectAgentKind, diffEvents, isDirectInvocation, main, upsertEnvLine, waitForStart };
+export declare const upsertEnvLine: (content: string, key: string, value: string) => string;
+/**
+ * Write the secret `take` returns to `file` under `key`, leaving the file
+ * owner-only. The file is opened before `take` runs, because taking the
+ * secret consumes it and an unwritable destination must fail while it is
+ * still deposited; it is read after, so lines written meanwhile survive.
+ */
+export declare const writeEnvSecret: (file: string, key: string, take: () => Promise<string>) => Promise<void>;
+export declare const main: (argv: readonly string[]) => Promise<undefined>;
+export {};
 //# sourceMappingURL=cli.d.ts.map

package/dist/cli.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"cli.d.ts","names":[],"sources":["../src/cli.ts"],"mappings":";;;KAsGK;EAAW;EAAsB,OAAO;;;cA8ChC,kBAAmB,MAAK,OAAO;;cA2C/B,qBACX,MAAK,OAAO,YACZ;EAAS;GACT;EAAU;;KA8FP;EACC;;EACA;EAA0B;EAAmB;;EAE7C;EACA;EACA;;EAEA;EACA;;EAEA;;EAEA;EAA0B;EAAiB;;EAC3C;EAAwB;;EACxB;EAAiC;EAAkB;;EACnD;EAAmB;;EACnB;EAAoB;;EACpB;EAA2B;;cAKpB,aACX,QAAQ,SAAS,OACjB,OAAO,SAAS,UACf;;cAkHU,eACX,QAAQ,KAAK,2CAAsC,QAAA,SAAA;cAyExC,UACX,yBACA,OAAO,oBACN,SAAS;EAAc;;;cAoFb,gBAAiB,iBAAiB,aAAa;cA2B/C,OAAc,4BAAuB"}
+{"version":3,"file":"cli.d.ts","sourceRoot":"","sources":["../src/cli.ts"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,cAAc,EAAE,oBAAiB;AAkB/C,OAAO,KAAK,EAAE,QAAQ,EAAE,sBAAmB;AAE3C,eAAO,MAAM,IAAI,QAiChB,CAAC;AAEF,eAAO,MAAM,YAAY,GACvB,KAAK,MAAM,WA0CZ,CAAC;AAEF,KAAK,MAAM,GAAG;IAAE,UAAU,EAAE,MAAM,EAAE,CAAC;IAAC,KAAK,EAAE,GAAG,CAAC,MAAM,EAAE,MAAM,GAAG,IAAI,CAAC,CAAA;CAAE,CAAC;AA6C1E,kGAAkG;AAClG,eAAO,MAAM,eAAe,GAAI,MAAK,MAAM,CAAC,UAAwB,uBACd,CAAC;AAyCvD,2GAA2G;AAC3G,eAAO,MAAM,kBAAkB,GAC7B,MAAK,MAAM,CAAC,UAAwB,EACpC,QAAO;IAAE,KAAK,CAAC,EAAE,OAAO,GAAG,SAAS,CAAA;CAAkB,EACtD,SAAQ;IAAE,KAAK,CAAC,EAAE,OAAO,GAAG,SAAS,CAAA;CAAmB,YAInC,CAAC;AA0FxB,KAAK,WAAW,GACZ;IAAE,KAAK,EAAE,kBAAkB,CAAA;CAAE,GAC7B;IAAE,KAAK,EAAE,iBAAiB,CAAC;IAAC,SAAS,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GAC7D;IACE,KAAK,EAAE,gBAAgB,CAAC;IACxB,OAAO,EAAE,MAAM,CAAC;IAChB,MAAM,EAAE,MAAM,CAAC;IACf,qEAAqE;IACrE,MAAM,EAAE,MAAM,GAAG,MAAM,EAAE,CAAC;IAC1B,IAAI,CAAC,EAAE,MAAM,CAAC;IACd,2GAA2G;IAC3G,MAAM,CAAC,EAAE,IAAI,CAAC;CACf,GACD;IAAE,KAAK,EAAE,iBAAiB,CAAC;IAAC,OAAO,EAAE,MAAM,CAAC;IAAC,MAAM,EAAE,MAAM,CAAA;CAAE,GAC7D;IAAE,KAAK,EAAE,eAAe,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,GAC5C;IAAE,KAAK,EAAE,wBAAwB,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAC;IAAC,QAAQ,EAAE,MAAM,CAAA;CAAE,GACvE;IAAE,KAAK,EAAE,UAAU,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GACnC;IAAE,KAAK,EAAE,WAAW,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,GACpC;IAAE,KAAK,EAAE,eAAe,CAAC;IAAC,QAAQ,EAAE,MAAM,EAAE,CAAA;CAAE,CAAC;AAKnD,eAAO,MAAM,UAAU,GACrB,QAAQ,QAAQ,CAAC,KAAK,EACtB,OAAO,QAAQ,CAAC,KAAK,KACpB,WAAW,EAqEb,CAAC;AA4CF,2LAA2L;AAC3L,eAAO,MAAM,YAAY,GACvB,QAAQ,IAAI,CAAC,cAAc,EAAE,OAAO,GAAG,WAAW,CAAC,6BAiBjD,CAAC;AAwDL,eAAO,MAAM,OAAO,GAClB,MAAM,SAAS,MAAM,EAAE,EACvB,OAAO,MAAM,CAAC,OAAO,CAAC,KACrB,QAAQ,CAAC,SAAS,GAAG;IAAE,MAAM,CAAC,EAAE,MAAM,CAAA;CAiFxC,CAAC;AAQF,+EAA+E;AAC/E,eAAO,MAAM,aAAa,GAAI,SAAS,MAAM,EAAE,KAAK,MAAM,EAAE,OAAO,MAAM,WAWxE,CAAC;AAEF;;;;;GAKG;AACH,eAAO,MAAM,cAAc,GACzB,MAAM,MAAM,EACZ,KAAK,MAAM,EACX,MAAM,MAAM,OAAO,CAAC,MAAM,CAAC,kBAa5B,CAAC;AAkBF,eAAO,MAAM,IAAI,GAAU,MAAM,SAAS,MAAM,EAAE,uBA+LjD,CAAC"}

package/dist/cli.js

@@ -1,22 +1,22 @@
 import { connectCheckout } from "./client.js";
 import { INPUT_PRESETS, isPresetId, presetInput } from "./presets.js";
-import { AGENT_HEARTBEAT_MS, OPTION_ICONS, classifyChoiceAnswer, currentPlan, isAgentPresent, isClosed, isOptionIcon, parseModelAnswer, parseMultipleAnswer, stepProgress } from "./protocol.js";
+import { AGENT_HEARTBEAT_MS, OPTION_ICONS, classifyChoiceAnswer, currentPlan, isAgentPresent, isClosed, isOptionIcon, isValidModelAnswer, parseMultipleAnswer, stepProgress } from "./protocol.js";
 import { spawn } from "node:child_process";
-import { readFile, writeFile } from "node:fs/promises";
+import { open, readFile } from "node:fs/promises";
 import { createInterface } from "node:readline/promises";
 import { resolve } from "node:path";
 //#region src/cli.ts
 const HELP = `setup-agent <url> [command]
 
 Commands (the url always comes first):
-  status                            Print the checkout as JSON.
-  stream                            Follow the checkout: one JSON array of events per line.
+  status                            Print the setup as JSON.
+  stream                            Follow the setup: one JSON array of events per line.
   log <text>                        Send a message to the user: a reply, something no question or step conveys, or one wrap-up when finished.
   ack <message-id>                  Acknowledge a user message.
   ask <prompt> [--placeholder <text>] [--optional] [--step <step-id>] [--wait]
                                     Ask the user for a line of text.
   ask [prompt] --preset <framework|llm-provider|project> [--only <id,id>] [--choices <id=description,...>] [--default <id>] [--optional] [--step <step-id>] [--wait]
-                                    Ask a standard question. --only restricts the options (one id locks it in); --default preselects one.
+                                    Ask a standard question. --only restricts the options and leaves out --choices (one id locks it in); --default preselects one.
                                     "framework" answers "<framework>:<language>"; "llm-provider" answers JSON with provider, model and reasoningEffort; the key itself arrives through "env".
                                     "project" lists the React projects you found as --choices "<path>=<what it is>,..." ahead of "New project"; it answers a path, or "new:<next|vite|react-router|tanstack-start|expo>".
   ask <prompt> --choices <id,id,...> --icons <id=icon,...> [--single] [--default <id>] [--optional] [--step <step-id>] [--wait]
@@ -25,8 +25,8 @@ Commands (the url always comes first):
                                     --single is for options that exclude each other (one framework, one model, yes or no); the answer is then one id.
                                     --icons is required and names an icon for every option, from: ${OPTION_ICONS.join(", ")}.
   ask <prompt> --product <slug> [--wait]
-                                    Propose adding a product to this checkout, such as one another product needs first. Answers "added"; the product and its guide then appear in "status".
-  wait start                        Block until the user clicks Begin plan in their browser; after a finished or cancelled checkout, until the next one begins.
+                                    Propose adding a product to this setup, such as one another product needs first. Answers "added"; the product and its guide then appear in "status".
+  wait start                        Block until the user clicks Begin plan in their browser; after a finished or cancelled setup, until the next one begins.
   wait <input-id>                   Block until the user answers or dismisses an input. A multi-select answer prints as an array.
   plan (<markdown> | --file <path>) [--wait]
                                     Propose the plan for the user to approve. --wait blocks until they decide.
@@ -40,17 +40,17 @@ Commands (the url always comes first):
   done [--summary <text>] [--preview <url>]
                                     Mark every remaining step done and propose closing; the user closes it.
 `;
-const INSTRUCTIONS = (url) => `You are the coding agent for a checkout the user opened in their browser. The browser shows this checkout live; every command below updates it. The user watches the browser, not this terminal: once setup begins, send questions through "ask" so the user can answer in their browser.
+const INSTRUCTIONS = (url) => `You are the coding agent for a setup the user opened in their browser. The browser shows this setup live; every command below updates it. The user watches the browser, not this terminal: once setup begins, send questions through "ask" so the user can answer in their browser.
 
 First, start a persistent Monitor on
   npx setup-agent ${url} stream
-and keep it running: the browser shows you as connected only while it runs, and it is how answers reach you. The URL is the user's link to you from their browser, not one checkout: it outlives this setup, and their next setup arrives on the same stream. Each line is a JSON array of events: "planning.started", "input.answered" ({inputId, answer, note?}; answer is an array for a choice question not asked with --single), "input.dismissed", "plan.approved", "plan.changes-requested" ({feedback}), "message.created" ({messageId, text}), "finished", "cancelled", "checkout.created" ({products}).
+and keep it running: the browser shows you as connected only while it runs, and it is how answers reach you. The URL is the user's link to you from their browser, not one setup: it outlives this one, and their next setup arrives on the same stream. Each line is a JSON array of events: "planning.started", "input.answered" ({inputId, answer, note?}; answer is an array for a choice question not asked with --single), "input.dismissed", "plan.approved", "plan.changes-requested" ({feedback}), "message.created" ({messageId, text}), "finished", "cancelled", "setup.created" ({products}).
 
 The user can message you at any time, including while a question is waiting. Read "message.created" events, acknowledge each with "npx setup-agent ${url} ack <message-id>", and reply using "log" with what you will do. Pending messages are replayed when the stream starts and listed in "status". A message is not an answer or plan approval; keep those decisions explicit.
 
 "log" is a message to the user, and the user reads every one: send it only to reply to their message, to tell them something no question or step conveys (a blocker, a deviation from the plan, a decision you made for them), or once as a wrap-up when the install is finished. Findings go in the plan, progress in step notes, questions in "ask"; do not narrate.
 
-Before planning, check the current checkout status. If it is "waiting", tell the user in your own conversation: "I'm connected. Go back to your browser and click Begin plan. You can watch my progress, answer questions, and steer me there." Then run:
+Before planning, check the current setup status. If it is "waiting", tell the user in your own conversation: "I'm connected. Go back to your browser and click Begin plan. You can watch my progress, answer questions, and steer me there." Then run:
   npx setup-agent ${url} wait start
 Keep the stream running while you wait. Do not inspect the project, fetch guides, ask setup questions, or propose a plan until this command returns {"ok":true}. Only the user in the browser should start planning; never invoke the browser's start command yourself. "planning.started" also arrives on the stream. If the status is already "planning" or "installing", resume that phase without asking the user to begin again. If it is "done" or "cancelled", that setup is over: tell the user you are connected and waiting for their next setup, and run "wait start", which returns once the next one begins.
 
@@ -58,16 +58,16 @@ The remaining phases are plan, then install.
 
 1. Plan. Investigate only; change nothing yet. If the current directory is not an app to install into (a monorepo root, an empty folder, a library), ask where to install first:
   npx setup-agent ${url} ask "Which project should I install into?" --placeholder "An absolute path, or a path for a new Next.js app" --wait
-Read the project: its app framework and package manager, the agent framework and model provider it already uses, where components live, any existing chat route. Fetch each product's "guide" URL from the checkout below; it is the install reference. Ask for what the project does not decide, using the standard questions so the browser can render them well:
+Read the project: its app framework and package manager, the agent framework and model provider it already uses, where components live, any existing chat route. Fetch each product's "guide" URL from the setup below; it is the install reference. Ask for what the project does not decide, using the standard questions so the browser can render them well:
   npx setup-agent ${url} ask --preset framework
   npx setup-agent ${url} ask --preset llm-provider
-If a product's guide needs another product the project does not have yet (most need assistant-ui installed and rendering a thread), do not stop and do not install it on the side. Propose adding it to this checkout:
+If a product's guide needs another product the project does not have yet (most need assistant-ui installed and rendering a thread), do not stop and do not install it on the side. Propose adding it to this setup:
   npx setup-agent ${url} ask "assistant-ui is not installed in this project yet. Add it to this setup?" --product assistant-ui --wait
 On "added", run "status", fetch the new product's guide, and install it first in your plan. If the user dismisses it, follow what the guide says about the missing product.
 Skip a preset the code already answers (a chat route on the AI SDK, a provider key in .env.local) and log why. Ask everything at once, keep investigating, and block with "wait <input-id>" only when nothing else can proceed. A framework answer is "<framework>:<language>", for example "ai-sdk:typescript". A model answer is JSON {"provider","model","reasoningEffort"?}. An answer may carry a "note" from the user; follow it. A choice answer that matches none of the options is the user's own text.
 Then write the plan as markdown and submit it:
   npx setup-agent ${url} plan --file <path> --wait
-Use these headings, each with bullets: "## What I found" (facts as \`- **Label:** value\`: app framework, package manager, agent framework, model provider and model, where components live), "## What I will install" (packages and files, one per bullet), "## Steps" (a numbered list, one line each), and "## Open questions" only if any remain. Keep it under 30 lines; no preamble. "plan --wait" prints {"decision":"approve"} or {"decision":"revise","feedback":"..."}. On revise, address the feedback (ask again if you need to) and submit a new plan; repeat until approved. Do not change the project before approval: the checkout refuses steps until then.
+Use these headings, each with bullets: "## What I found" (facts as \`- **Label:** value\`: app framework, package manager, agent framework, model provider and model, where components live), "## What I will install" (packages and files, one per bullet), "## Steps" (a numbered list, one line each), and "## Open questions" only if any remain. Keep it under 30 lines; no preamble. "plan --wait" prints {"decision":"approve"} or {"decision":"revise","feedback":"..."}. On revise, address the feedback (ask again if you need to) and submit a new plan; repeat until approved. Do not change the project before approval: the setup refuses steps until then.
 
 2. Install. Declare the steps from your plan up front, in order:
   npx setup-agent ${url} add-step "<title>" --detail "<one line>"
@@ -78,9 +78,9 @@ which writes ENV_VAR=<key> into that file. Use the answer's model in the chat ro
 
 When every product is installed and verified, run
   npx setup-agent ${url} done --summary "<one or two lines on what you installed and how to try it>" --preview http://localhost:<port>
-Before that, start the project's dev server in the background when the project has one, check that the page you changed loads, and pass the address as --preview (the page itself when it is not the root); leave the server running so the user can try the result. Omit --preview when there is nothing to open. This proposes closing the checkout; only the user closes it. Do not stop the stream or exit: stay idle on it, because the user may follow up with a "message.created" event. Handle it, then run "done" again. The stream prints "finished" once the user closes the checkout, and "cancelled" if they end it early. Keep the stream running after either: the user's next setup starts on this same URL and arrives as "checkout.created" with its products. Run
+Before that, start the project's dev server in the background when the project has one, check that the page you changed loads, and pass the address as --preview (the page itself when it is not the root); leave the server running so the user can try the result. Omit --preview when there is nothing to open. This proposes closing the setup; only the user closes it. Do not stop the stream or exit: stay idle on it, because the user may follow up with a "message.created" event. Handle it, then run "done" again. The stream prints "finished" once the user closes the setup, and "cancelled" if they end it early. Keep the stream running after either: the user's next setup starts on this same URL and arrives as "setup.created" with its products. Run
   npx setup-agent ${url} wait start
-which returns once that setup begins, then run "status" for its products, guides and instructions and go through plan and install again. A "checkout.created" event while you are still working means the user replaced this setup: drop what you were doing and start over the same way.
+which returns once that setup begins, then run "status" for its products, guides and instructions and go through plan and install again. A "setup.created" event while you are still working means the user replaced this setup: drop what you were doing and start over the same way.
 `;
 const parseArgs = (argv) => {
 	const positional = [];
@@ -193,7 +193,7 @@ const launchAgent = async (url) => {
 	});
 	process.exit(code);
 };
-const requireState = (client) => client.state ?? fail("the checkout has no state");
+const requireState = (client) => client.state ?? fail("the setup has no state");
 const summary = (state) => {
 	const plan = currentPlan(state);
 	return {
@@ -266,7 +266,7 @@ const diffEvents = (before, after) => {
 		next: STAY_CONNECTED
 	});
 	if (after.id !== null && after.id !== before.id) events.push({
-		event: "checkout.created",
+		event: "setup.created",
 		products: after.products.map((product) => product.slug)
 	});
 	return events;
@@ -313,7 +313,7 @@ const stream = async (client) => {
 	process.on("SIGTERM", stop);
 	await new Promise(() => {});
 };
-/** Resolves once a checkout is planning or installing, or once the one being waited on is cancelled; a checkout already closed when the wait begins is over, so the wait is for the next one. */
+/** Resolves once a setup is planning or installing, or once the one being waited on is cancelled; a setup already closed when the wait begins is over, so the wait is for the next one. */
 const waitForStart = (client) => new Promise((resolve) => {
 	let previous;
 	const check = () => {
@@ -446,15 +446,38 @@ const askSeed = (rest, flags) => {
 		...stepId !== void 0 && { stepId }
 	};
 };
+const assertEnvKey = (key) => {
+	if (!/^[A-Za-z_][A-Za-z0-9_]*$/.test(key)) throw new Error(`"${key}" is not an environment variable name`);
+};
 /** Sets `key=value` in dotenv text, replacing an existing line for the key. */
 const upsertEnvLine = (content, key, value) => {
+	assertEnvKey(key);
 	const line = `${key}=${value}`;
 	const lines = content === "" ? [] : content.replace(/\n$/, "").split("\n");
-	const index = lines.findIndex((entry) => new RegExp(`^(export\\s+)?${key}\\s*=`).test(entry));
+	const index = lines.findIndex((entry) => /^(?:export\s+)?([A-Za-z_][A-Za-z0-9_]*)\s*=/.exec(entry)?.[1] === key);
 	if (index === -1) lines.push(line);
 	else lines[index] = line;
 	return `${lines.join("\n")}\n`;
 };
+/**
+* Write the secret `take` returns to `file` under `key`, leaving the file
+* owner-only. The file is opened before `take` runs, because taking the
+* secret consumes it and an unwritable destination must fail while it is
+* still deposited; it is read after, so lines written meanwhile survive.
+*/
+const writeEnvSecret = async (file, key, take) => {
+	assertEnvKey(key);
+	const handle = await open(file, "a+", 384);
+	try {
+		await handle.chmod(384);
+		const value = await take();
+		const current = await handle.readFile("utf8");
+		await handle.truncate(0);
+		await handle.writeFile(upsertEnvLine(current, key, value));
+	} finally {
+		await handle.close();
+	}
+};
 const answerFields = (input, answer) => ({
 	answer: input.multiple && parseMultipleAnswer(answer) || answer,
 	...input.note !== void 0 && { note: input.note },
@@ -483,7 +506,7 @@ const main = async (argv) => {
 				const kind = detectAgentKind();
 				await commands["agent/intro"]({ ...kind !== void 0 && { kind } }).catch(() => {});
 				process.stdout.write(INSTRUCTIONS(url));
-				process.stdout.write("\nCurrent checkout:\n");
+				process.stdout.write("\nCurrent setup:\n");
 				print(summary(requireState(client)));
 				break;
 			}
@@ -579,16 +602,19 @@ const main = async (argv) => {
 				const inputId = rest[0] ?? fail(usage);
 				const envKey = rest[1] ?? fail(usage);
 				if (!/^[A-Za-z_][A-Za-z0-9_]*$/.test(envKey)) fail(`"${envKey}" is not an environment variable name`);
-				const input = requireState(client).inputs.find((candidate) => candidate.id === inputId) ?? fail(`no input "${inputId}"`);
+				const state = requireState(client);
+				const input = state.inputs.find((candidate) => candidate.id === inputId) ?? fail(`no input "${inputId}"`);
+				const setupId = state.id ?? fail("the setup has not been created yet");
+				if (isClosed(state)) fail("the setup is not open");
 				if (input.status !== "answered") fail(`input "${inputId}" is ${input.status}`);
-				if (parseModelAnswer(input.answer ?? "") === void 0) fail(`input "${inputId}" is not an llm-provider answer`);
+				if (input.kind !== "model" || !isValidModelAnswer(input, input.answer ?? "")) fail(`input "${inputId}" is not an llm-provider answer`);
 				const file = resolve(flagText(flags, "file") ?? ".env.local");
-				const response = await fetch(`${url.replace(/\/$/, "")}/secret/${encodeURIComponent(inputId)}`);
-				if (response.status === 404) fail(`the key for "${inputId}" was already taken or never deposited`);
-				if (!response.ok) fail(`could not fetch the key: ${response.status}`);
-				const value = await response.text();
-				const current = await readFile(file, "utf8").catch(() => "");
-				await writeFile(file, upsertEnvLine(current, envKey, value));
+				await writeEnvSecret(file, envKey, async () => {
+					const response = await fetch(`${url.replace(/\/$/, "")}/secret/${encodeURIComponent(inputId)}?setup=${encodeURIComponent(setupId)}`);
+					if (response.status === 404) fail(`the key for "${inputId}" was already taken or never deposited`);
+					if (!response.ok) fail(`could not fetch the key: ${response.status}`);
+					return response.text();
+				});
 				print({
 					ok: true,
 					envKey,
@@ -618,7 +644,7 @@ const main = async (argv) => {
 				print({
 					ok: true,
 					status: "proposed",
-					next: "Keep the stream running and stay idle. The user closes the checkout or sends a follow-up message."
+					next: "Keep the stream running and stay idle. The user closes the setup or sends a follow-up message."
 				});
 				break;
 			}
@@ -631,6 +657,6 @@ const main = async (argv) => {
 	}
 };
 //#endregion
-export { askSeed, detectAgentKind, diffEvents, isDirectInvocation, main, upsertEnvLine, waitForStart };
+export { HELP, INSTRUCTIONS, askSeed, detectAgentKind, diffEvents, isDirectInvocation, main, upsertEnvLine, waitForStart, writeEnvSecret };
 
 //# sourceMappingURL=cli.js.map