@workser/cli 0.6.22 → 0.6.23

package/dist/index.js

@@ -4575,7 +4575,7 @@ forever; if it does, carry on and state clearly what you assumed.
 ## Asking for an app that does not exist yet
 
 The project needs a kind of app it does not have \u2014 a backend for the phone app, a
-desktop build of the website. **You cannot create one yourself**, by design: apps
+phone version of the website. **You cannot create one yourself**, by design: apps
 are real infrastructure on the owner's account. Ask, and their click creates it.
 The answer gives you the new app's id.
 
@@ -4590,15 +4590,19 @@ workser ask "The phone app needs an API to hold its data. Add one?" \\
 |---|---|
 | \`web\` | Next.js site on Workser hosting |
 | \`mobile\` | Expo / React Native phone app |
-| \`desktop\` | Next.js + Electron, installs on a Mac or PC |
 | \`api\` | backend service \u2014 \`api-hono\` (TypeScript) or \`api-python\` (FastAPI) |
 
 **Name the kind you actually mean.** Asking for \`web\` because you are unsure is
-how a desktop app gets created as a website: the card shows the owner the kind
+how a phone app gets created as a website: the card shows the owner the kind
 you named, they approve THAT, and the wrong app is provisioned under your own
 sentence asking for the right one. An unknown kind is refused with the list
 above rather than guessed at \u2014 read it and ask again.
 
+**There is no desktop app type.** Workser builds websites, phone apps and
+backend services. If the owner asks for a Mac or Windows app, say plainly that
+Workser cannot make one yet \u2014 do not offer a web app dressed as a window, and
+do not build a "desktop-style" page instead. That is not what they asked for.
+
 **Never ask for a secret value this way** \u2014 the answer is stored and displayed. Ask
 *where* a key should go, then have the user set it (\`workser env set\` writes it
 without you ever seeing it).
@@ -4674,105 +4678,6 @@ workser artifact add --url https://acme.workser.app --kind app -t "Storefront"
 \`\`\`
 
 See \`reference/deliverables.md\`.
-`
-  },
-  {
-    topic: "desktop",
-    title: "Desktop apps \u2014 one codebase, a window, and an installer",
-    summary: "How a Workser desktop app is built, what breaks only after it is installed, and how to produce and publish a signed installer.",
-    commands: ["project", "env", "deploy"],
-    source: "skills/workser/reference/desktop.md",
-    body: `# Desktop apps
-
-A Workser desktop app is **one Next.js codebase with two ways to run**: a normal
-web build for development and preview, and an Electron shell that loads the
-static export from disk and gets packaged into an installer.
-
-There is no deploy. A desktop app has no Vercel project and no URL \u2014 its
-preview is the app running locally, and its deliverable is a file someone
-double-clicks.
-
-## The rule that breaks everything, and only after install
-
-**The app must stay statically exportable.** A packaged Electron app loads from
-\`file://\` and has **no Node server**. So none of this exists once it is
-installed:
-
-- server components that fetch at request time
-- server actions (\`"use server"\`)
-- route handlers under \`app/api/*\`
-- \`next/image\` optimisation
-
-Every one of them works in \`npm run dev\` **and** in the local preview, and fails
-only on the owner's machine. That is the one direction of error nobody catches,
-so \`next.config.mjs\` keeps \`output: "export"\` to make the build fail loudly
-instead. Do not remove it to "fix" an import.
-
-Need a server? Use the project's api app \u2014 \`workser project apps\` to find it,
-then read its URL and set \`NEXT_PUBLIC_API_URL\`. See \`workser help apps\`.
-
-## Secrets: this is a public client
-
-Anyone who installs the app can read every string inside it. So:
-
-- \`NEXT_PUBLIC_*\` only, and nothing behind that prefix is private
-- never a database URL, an API key, or a \`wsgw_\` gateway key
-- anything privileged lives in the api app and is reached over HTTP
-
-The manifest deliberately does not declare \`AI_GATEWAY_API_KEY\` for this type,
-which is what stops Workser seeding one. Do not add it.
-
-## The two processes
-
-| File | Runs where | May do |
-| --- | --- | --- |
-| \`electron/main.js\` | Node, on the machine | files, tray, windows, updates |
-| \`app/**\` | the renderer, sandboxed | ordinary web code, no Node |
-| \`electron/preload.js\` | the bridge | expose **named functions** only |
-
-\`contextIsolation: true\` and \`nodeIntegration: false\` are not defaults to tidy
-up \u2014 turning either off hands full filesystem and process access to page code.
-Add a capability by exporting one named function from preload, never by handing
-the renderer \`ipcRenderer\`.
-
-## Building and shipping
-
-\`\`\`bash
-npm run dev            # browser only, fastest loop
-npm run dev:desktop    # the same app inside a real Electron window
-npm run build          # static export -> out/
-npm run dist:desktop   # the installer -> release/
-\`\`\`
-
-In the app, **Publish \u2192 Your installer** does the same thing with a target
-picker, progress, and a download link at the end.
-
-## Signing \u2014 the owner's certificate, never Workser's
-
-An unsigned build runs perfectly on the machine that made it and tells every
-other machine the app is damaged (macOS) or trips SmartScreen (Windows). That
-is the failure an owner cannot diagnose, so say it before they send the file.
-
-\`electron-builder\` reads these from the environment; set them with
-\`workser env set --app <id>\`:
-
-| Platform | Keys |
-| --- | --- |
-| macOS | \`CSC_LINK\`, \`CSC_KEY_PASSWORD\` |
-| macOS notarize | \`APPLE_ID\`, \`APPLE_APP_SPECIFIC_PASSWORD\`, \`APPLE_TEAM_ID\` |
-| Windows | \`WIN_CSC_LINK\`, \`WIN_CSC_KEY_PASSWORD\` |
-
-A Mac app can only be built on a Mac \u2014 \`codesign\` and \`hdiutil\` are Apple's and
-have no substitute.
-
-## Auto-update
-
-Publishing uploads the installer **and** the update metadata
-(\`latest-mac.yml\` / \`latest.yml\`) beside it. \`electron-updater\` reads only that
-metadata, so an installer published alone gives you a download that works once
-and an app that can never update itself \u2014 and nobody notices until release two.
-Keep \`publish.url\` in \`electron-builder.yml\` pointed at the prefix the publish
-step reports back.
 `
   },
   {
@@ -9291,7 +9196,10 @@ var TYPES = [
 var APP_TYPES = [
   "web",
   "mobile",
-  "desktop",
+  // NOT OFFERED AT FIRST LAUNCH (2026-09-05) — `desktop` is `creatable: false`
+  // in core-api, so the card would error on the owner's click. Re-enable
+  // together with that flag; grep the marker.
+  // "desktop",
   // `api` is the shorthand; the two concrete spellings pick the runtime and
   // are accepted at this boundary for an agent that knows which one it wants.
   "api",
@@ -12445,7 +12353,7 @@ function colour(d) {
 
 // src/index.ts
 var pkg = {
-  version: true ? "0.6.22" : "0.0.0-dev"
+  version: true ? "0.6.23" : "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.22",
+  "version": "0.6.23",
   "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

@@ -22,7 +22,6 @@ screen long. Find your row, run that **one** command — every line costs you.
 | Follow the project's brand — colours, fonts, logo | `design …` | `workser help brand` |
 | Provision or query Postgres; list end users | `db …`, `auth …` | `workser help database` |
 | See the project's other apps, and wire one to another | `project …`, `env … --app` | `workser help apps` |
-| Build a desktop app, sign it, ship an installer | `deploy`, `env …` | `workser help desktop` |
 | Deploy, set env vars, read logs, check a domain | `deploy`, `env …`, `logs`, `versions`, `domain`, `open` | `workser help deploy` |
 | Save work before a risky change, undo it, sync this folder | `checkpoint`, `restore`, `sync` | `workser help version-control` |
 | Put files in the project's bucket | `storage …` | `workser help storage` |

package/skills/workser/reference/deliverables.md

@@ -101,7 +101,7 @@ forever; if it does, carry on and state clearly what you assumed.
 ## Asking for an app that does not exist yet
 
 The project needs a kind of app it does not have — a backend for the phone app, a
-desktop build of the website. **You cannot create one yourself**, by design: apps
+phone version of the website. **You cannot create one yourself**, by design: apps
 are real infrastructure on the owner's account. Ask, and their click creates it.
 The answer gives you the new app's id.
 
@@ -116,15 +116,19 @@ workser ask "The phone app needs an API to hold its data. Add one?" \
 |---|---|
 | `web` | Next.js site on Workser hosting |
 | `mobile` | Expo / React Native phone app |
-| `desktop` | Next.js + Electron, installs on a Mac or PC |
 | `api` | backend service — `api-hono` (TypeScript) or `api-python` (FastAPI) |
 
 **Name the kind you actually mean.** Asking for `web` because you are unsure is
-how a desktop app gets created as a website: the card shows the owner the kind
+how a phone app gets created as a website: the card shows the owner the kind
 you named, they approve THAT, and the wrong app is provisioned under your own
 sentence asking for the right one. An unknown kind is refused with the list
 above rather than guessed at — read it and ask again.
 
+**There is no desktop app type.** Workser builds websites, phone apps and
+backend services. If the owner asks for a Mac or Windows app, say plainly that
+Workser cannot make one yet — do not offer a web app dressed as a window, and
+do not build a "desktop-style" page instead. That is not what they asked for.
+
 **Never ask for a secret value this way** — the answer is stored and displayed. Ask
 *where* a key should go, then have the user set it (`workser env set` writes it
 without you ever seeing it).