@workser/cli 0.6.3 → 0.6.5

package/dist/index.js

@@ -4092,8 +4092,12 @@ user's machine remotely \u2014 you're getting it locally, gated by the same safe
   destructive commands, rate limits. Refusals are the policy working, not a bug to
   route around.
 - **Sensitive actions are approval-gated.** Writing or deleting files, running a shell
-  command, clicking or typing may return \`awaiting_approval\` (exit 5) \u2014 tell the user
-  to approve in Orbit, then retry.
+  command, clicking or typing may return \`awaiting_approval\` (exit 5) \u2014 this is
+  usually an unattended run, so nobody is necessarily watching for it. Say plainly
+  that it needs approval in Orbit and **stop this turn**. Never write a retry loop,
+  a polling script, or a sleep-and-recheck command around it \u2014 that spends the whole
+  run spin-waiting on a click and will simply time out. The same command works on
+  its own, the next time it runs, once approved.
 - **You already have your own tools.** For editing files in this repo, use them. Reach
   for \`workser tool\` when you need something *outside* the project \u2014 the screen, the
   clipboard, a browser, another app on the machine.
@@ -4128,7 +4132,8 @@ workser auth status                 # is auth enabled? + Neon auth mode
 - **\`db url\` is a credential.** Don't print it into the conversation, don't paste it
   into a file the user will commit. The app gets it from its environment already.
 - **Writes are approval-gated.** A \`db query\` that mutates may return
-  \`awaiting_approval\` (exit 5). Ask the user to approve in Orbit, then retry.
+  \`awaiting_approval\` (exit 5). Say it needs approval in Orbit and stop this turn \u2014
+  don't loop or poll waiting for it; the same command works once it's approved.
 - **\`DROP\` / \`TRUNCATE\` are refused** by the safety policy. Change schema with a
   migration in the app's own migration folder, not with a destructive one-off.
 - **The database is the project's, not the app's.** Sibling apps in the same project
@@ -4292,17 +4297,19 @@ Settings \u2014 \`workser env\` \u2014 are their own topic: \`workser help env\`
 - **\`promote\` and \`rollback\` are the same upstream call and two commands on
   purpose.** Promote ships the newest build; rollback puts version N back. Both
   ask the owner and return exit 7 (\`awaiting_approval\`) until they answer \u2014 and
-  that gate holds even on a "just do it" run.
+  that gate holds even on a "just do it" run. Say so and stop this turn; don't
+  loop or poll for the answer (see the \`awaiting_approval\` note below).
 - **There is no \`deployments cancel\`.** Nothing upstream can stop a build that is
   already running. Wait for it and then promote or roll back.
 - **\`--watch\` blocks until there's a live URL.** Without it you get a deploy id and
   have to poll \`deploy status\`.
 - **\`domain add\` and \`domain rm\` ask the owner to confirm** and return exit 7
-  (\`awaiting_approval\`) until they do \u2014 tell them to approve, then retry the same
-  command. Domains Workser owns (\`workser.ai\` and its subdomains) and hostnames
-  the hosting provider assigns (\`*.vercel.app\`) are refused outright: those are
-  not attachable, and the app's own preview and live URLs already exist without
-  attaching anything.
+  (\`awaiting_approval\`) until they do \u2014 say plainly that it needs approval in
+  Orbit and stop this turn; the same command works on its own once it's approved,
+  so don't write a retry loop or poll for it. Domains Workser owns (\`workser.ai\`
+  and its subdomains) and hostnames the hosting provider assigns (\`*.vercel.app\`)
+  are refused outright: those are not attachable, and the app's own preview and
+  live URLs already exist without attaching anything.
 
 ## After a successful deploy
 
@@ -10625,7 +10632,7 @@ function colour(d) {
 
 // src/index.ts
 var pkg = {
-  version: true ? "0.6.3" : "0.0.0-dev"
+  version: true ? "0.6.5" : "0.0.0-dev"
 };
 var program2 = new Command();
 program2.name("workser").description(

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@workser/cli",
-  "version": "0.6.3",
+  "version": "0.6.5",
   "description": "Workser CLI — give your local AI agent native DevOps & infrastructure on Workser. The agent runs `workser …` to provision, deploy, and manage real apps.",
   "license": "MIT",
   "type": "module",

package/skills/workser/SKILL.md

@@ -56,7 +56,7 @@ You operate on **one project's own infrastructure**. You *can* provision and use
 create the Neon database, read its connection string, browse its tables / rows / run
 SQL, provision the bucket + auth, deploy, set env vars, manage files. Sensitive
 actions are **gated** — the daemon may return `error.code = "awaiting_approval"`
-(exit 5) and wait for the user to approve in Orbit; ask them to approve, then retry.
+(exit 5); say so, stop, don't loop (rule 5).
 
 What you **cannot** do is administer the project set or destroy config:
 `project create` · `project use` · `env rm` · `domain set` return
@@ -85,9 +85,10 @@ pick or switch it.
    reserved for the owner in Orbit. Don't retry or look for a workaround — tell the
    user, then continue. Provisioning the *pinned project's own* db / bucket / auth is
    allowed (it may be approval-gated, not owner-only).
-5. **Approvals are normal.** Some allowed actions may return
-   `{"error":{"code":"awaiting_approval"}}` (exit 5) while the user approves in the
-   Orbit UI. Tell the user to approve, then retry — do **not** try to bypass it.
+5. **Approvals are normal — likely unattended, nobody watching.** An action may
+   return `{"error":{"code":"awaiting_approval"}}` (exit 5). Say so, **stop this
+   turn** — never a retry loop or sleep-and-recheck, it just times out. Works next
+   time, once approved.
 6. **Never ask for or store credentials.** Auth is handled by Orbit; you never see keys.
 7. **Verify before "done".** Before telling the user a task is complete, run
    `workser verify --json` (runs the project's typecheck/lint/build). If it
@@ -119,7 +120,7 @@ workser deploy --prod --watch --json              # 8. ship; returns the stable
   - `unauthorized` → user needs to authenticate.
   - `no_project` → no project is linked here; the user links it in Orbit.
   - `owner_only` → an owner action; tell the user to do it in Orbit, then continue.
-  - `awaiting_approval` → user must approve in Orbit; then retry.
+  - `awaiting_approval` → someone must approve in Orbit; say so, stop, don't poll.
   - `needs_local_app` → this machine has no Workser app, so folder commands
     can't run. Say so; don't reach for `git` instead.
 

package/skills/workser/reference/computer-use.md

@@ -28,8 +28,12 @@ user's machine remotely — you're getting it locally, gated by the same safety
   destructive commands, rate limits. Refusals are the policy working, not a bug to
   route around.
 - **Sensitive actions are approval-gated.** Writing or deleting files, running a shell
-  command, clicking or typing may return `awaiting_approval` (exit 5) — tell the user
-  to approve in Orbit, then retry.
+  command, clicking or typing may return `awaiting_approval` (exit 5) — this is
+  usually an unattended run, so nobody is necessarily watching for it. Say plainly
+  that it needs approval in Orbit and **stop this turn**. Never write a retry loop,
+  a polling script, or a sleep-and-recheck command around it — that spends the whole
+  run spin-waiting on a click and will simply time out. The same command works on
+  its own, the next time it runs, once approved.
 - **You already have your own tools.** For editing files in this repo, use them. Reach
   for `workser tool` when you need something *outside* the project — the screen, the
   clipboard, a browser, another app on the machine.

package/skills/workser/reference/database.md

@@ -28,7 +28,8 @@ workser auth status                 # is auth enabled? + Neon auth mode
 - **`db url` is a credential.** Don't print it into the conversation, don't paste it
   into a file the user will commit. The app gets it from its environment already.
 - **Writes are approval-gated.** A `db query` that mutates may return
-  `awaiting_approval` (exit 5). Ask the user to approve in Orbit, then retry.
+  `awaiting_approval` (exit 5). Say it needs approval in Orbit and stop this turn —
+  don't loop or poll waiting for it; the same command works once it's approved.
 - **`DROP` / `TRUNCATE` are refused** by the safety policy. Change schema with a
   migration in the app's own migration folder, not with a destructive one-off.
 - **The database is the project's, not the app's.** Sibling apps in the same project

package/skills/workser/reference/deploy.md

@@ -46,17 +46,19 @@ Settings — `workser env` — are their own topic: `workser help env`.
 - **`promote` and `rollback` are the same upstream call and two commands on
   purpose.** Promote ships the newest build; rollback puts version N back. Both
   ask the owner and return exit 7 (`awaiting_approval`) until they answer — and
-  that gate holds even on a "just do it" run.
+  that gate holds even on a "just do it" run. Say so and stop this turn; don't
+  loop or poll for the answer (see the `awaiting_approval` note below).
 - **There is no `deployments cancel`.** Nothing upstream can stop a build that is
   already running. Wait for it and then promote or roll back.
 - **`--watch` blocks until there's a live URL.** Without it you get a deploy id and
   have to poll `deploy status`.
 - **`domain add` and `domain rm` ask the owner to confirm** and return exit 7
-  (`awaiting_approval`) until they do — tell them to approve, then retry the same
-  command. Domains Workser owns (`workser.ai` and its subdomains) and hostnames
-  the hosting provider assigns (`*.vercel.app`) are refused outright: those are
-  not attachable, and the app's own preview and live URLs already exist without
-  attaching anything.
+  (`awaiting_approval`) until they do — say plainly that it needs approval in
+  Orbit and stop this turn; the same command works on its own once it's approved,
+  so don't write a retry loop or poll for it. Domains Workser owns (`workser.ai`
+  and its subdomains) and hostnames the hosting provider assigns (`*.vercel.app`)
+  are refused outright: those are not attachable, and the app's own preview and
+  live URLs already exist without attaching anything.
 
 ## After a successful deploy