@linzumi/cli 0.0.10-beta → 0.0.11-beta

package/README.md

@@ -43,7 +43,7 @@ address.
 To pin this exact beta:
 
 ```bash
-npm install -g @linzumi/cli@0.0.10-beta
+npm install -g @linzumi/cli@0.0.11-beta
 linzumi start ~/code/my-app
 ```
 
@@ -247,7 +247,7 @@ linzumi --version
 Expected:
 
 ```text
-linzumi 0.0.10-beta
+linzumi 0.0.11-beta
 ```
 
 If `linzumi` is not found, your global npm bin directory is not on `PATH`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@linzumi/cli",
-  "version": "0.0.10-beta",
+  "version": "0.0.11-beta",
   "description": "Connect your computer to Kandan for local Codex sessions, editors, and forwarded previews",
   "type": "module",
   "bin": {
@@ -29,5 +29,5 @@
     "node": ">=20",
     "bun": ">=1.2.0"
   },
-  "readme": "# Linzumi CLI\n\nRun an AI coding session on the code that is already on your computer, then\nopen the editor and app preview from a shared browser workspace.\n\nLinzumi is for the common team workflow that is still too painful:\n\n- your branch is only on your laptop\n- your app only runs with your local setup, secrets, database, or devices\n- you want an AI agent to read, edit, run, and explain that code\n- you want a teammate to see the editor or preview without cloning the repo\n- you do not want to move the project into a cloud VM just to collaborate\n\nThe CLI connects your machine to Kandan, Linzumi's shared browser workspace.\nYour code, terminal commands, dev servers, and editor runtime stay local. Kandan\nhandles sign-in, sharing, HTTPS browser access, and permission checks.\n\n## Try It\n\nUse Chrome, Edge, Arc, Brave, or another Chromium-based browser.\n\n```bash\nnpm install -g @linzumi/cli@beta\nlinzumi start ~/code/my-app\n```\n\nThen in the browser:\n\n```text\nExplain this project, open the editor, and tell me how to run it.\n```\n\nIf the project has a dev server, start it locally:\n\n```bash\nnpm run dev\n```\n\nOpen the forwarded preview from Kandan. You should get a normal HTTPS URL that\nyou can share with an approved teammate, without exposing a raw `localhost`\naddress.\n\nTo pin this exact beta:\n\n```bash\nnpm install -g @linzumi/cli@0.0.10-beta\nlinzumi start ~/code/my-app\n```\n\n## What You Get\n\nLinzumi turns your local project into a shared coding workspace:\n\n1. Codex can inspect and edit the folder you allowed.\n2. You can open a browser editor for that local folder.\n3. Local app previews are reachable through Kandan HTTPS URLs.\n4. Approved teammates can join the editor or preview.\n5. Kandan enforces auth, sharing grants, and allowed-port policy.\n\nThe important part: your project does not have to leave your computer for this\nto work.\n\n## What Runs Where\n\nOn your computer, the CLI starts a runner. The runner can:\n\n- launch or connect to Codex\n- download the Kandan-approved editor runtime\n- start code-server for the folder you chose\n- connect to explicitly approved local ports\n- stream editor and preview traffic through Kandan\n\nIn the browser, Kandan provides:\n\n- sign-in and workspace UI\n- local-runner status\n- editor and preview links\n- sharing controls\n- HTTPS termination\n- access checks before traffic reaches your machine\n\nWhen docs mention `127.0.0.1` or `localhost` on the local-service hop, that\nmeans your computer, not the Kandan server.\n\n## Requirements\n\nInstall these before running the beta:\n\n```bash\nnode --version\nnpm --version\nbun --version\ncodex --version\n```\n\nExpected:\n\n- Node.js 20 or newer\n- npm\n- Bun 1.2 or newer\n- Codex CLI\n- Chrome, Edge, Arc, Brave, or another Chromium-based browser\n\nSafari is semi-supported for now. Use Chromium for the best editor and\ncollaboration behavior.\n\n## First Run\n\n```bash\nlinzumi start ~/code/my-app\n```\n\nWhat happens:\n\n1. The CLI opens Kandan.\n2. You sign up or sign in.\n3. Kandan asks permission to connect this computer.\n4. The CLI stores a scoped local-runner token.\n5. The CLI checks Bun, Codex, and the Kandan editor runtime.\n6. Kandan shows the computer as connected.\n\nThe first editor launch can download a Kandan-approved runtime archive. Later\nruns reuse the verified runtime from:\n\n```text\n~/.linzumi/editor-runtimes\n```\n\nThe production path does not use a random local `code-server` install. Kandan\npublishes a checksummed runtime manifest, and the CLI only advertises editor\nreadiness after that runtime is verified locally.\n\n## Good Things To Try\n\nAsk Codex to map the project:\n\n```text\nWhat does this app do? Where should I start reading?\n```\n\nAsk Codex to make a small change:\n\n```text\nFind the main settings page and add a clear empty state.\n```\n\nOpen the editor from Kandan and inspect the changed files.\n\nStart a local dev server:\n\n```bash\nnpm run dev\n```\n\nIf a port is not auto-detected, restart with an explicit approved port:\n\n```bash\nlinzumi start ~/code/my-app --forward-port 3000\n```\n\nFor a collaboration test, invite another user, open the same file in the local\neditor, and type in Chromium. Remote cursor labels and selections should be\nvisible.\n\n## Hosted Kandan\n\nFor a hosted Kandan deployment, point the CLI at the hosted websocket URL:\n\n```bash\nlinzumi start ~/code/my-app --kandan-url wss://<your-kandan-host>\n```\n\nFor Render-hosted Kandan, public TLS should work without local certificate\nflags. The CLI derives the HTTPS API origin from the websocket URL for OAuth,\nruntime manifest download, and runtime archive download.\n\nFor local development with a private CA:\n\n```bash\nKANDAN_TLS_CA_FILE=/path/to/ca.crt linzumi start ~/code/my-app \\\n  --kandan-url wss://linzumi.io:4140\n```\n\n## Tailscale Development\n\nIf your browser needs to reach a local Kandan server through Tailscale:\n\n```bash\nlinzumi start ~/code/my-app \\\n  --kandan-url ws://100.71.192.98:4162 \\\n  --oauth-callback-host 100.71.192.98\n```\n\nUse your own Tailscale IP.\n\n## Commands\n\n```bash\nlinzumi\nlinzumi --help\nlinzumi --version\nlinzumi start <folder>\nlinzumi connect --help\nlinzumi connect [runner options]\nlinzumi auth [auth options]\n```\n\nMost people should use `linzumi start`.\n\n`linzumi connect` is the lower-level command for connecting to an explicit\nworkspace and channel:\n\n```bash\nlinzumi connect \\\n  --kandan-url wss://serve.kandanai.com \\\n  --workspace default \\\n  --channel general \\\n  --cwd ~/code/my-app\n```\n\n## Useful Options\n\n```bash\n--kandan-url <ws-url>       Kandan websocket URL\n--oauth-callback-host <ip>  Callback host reachable by your browser\n--runner-id <id>            Stable id for this computer\n--codex-bin <path>          Codex executable, default codex\n--model <name>              Codex model metadata shown in Kandan\n--reasoning-effort <value>  Codex reasoning metadata shown in Kandan\n--fast                      Mark this runner as low-latency\n--forward-port <ports>      Comma-separated local ports Kandan may expose\n--allowed-cwd <paths>       Comma-separated roots Kandan may use\n--log-file <path>           JSONL runner event log\n```\n\n`--code-server-bin` exists only as a development override. It is not the\nsupported production editor path.\n\n## Troubleshooting\n\nCheck the CLI version:\n\n```bash\nlinzumi --version\n```\n\nExpected:\n\n```text\nlinzumi 0.0.10-beta\n```\n\nIf `linzumi` is not found, your global npm bin directory is not on `PATH`.\n\nIf `bun` is not found, install Bun and rerun `linzumi start`.\n\nIf `codex` is not found, install or configure the Codex CLI, or pass\n`--codex-bin`.\n\nIf OAuth opens but does not return to the CLI, pass an\n`--oauth-callback-host` that your browser can reach.\n\nIf the editor does not become ready, do not install a local code-server package\nas a workaround. The server-managed runtime must download and verify cleanly.\nRerun the CLI and check the runner log.\n\nIf collaboration behaves oddly in Safari, retry in Chromium. Safari is currently\nsemi-supported.\n\n## For Kandan Release Engineers\n\nThe production contract is:\n\n1. Build the server-approved editor runtime archive.\n2. Publish the manifest and archive from Kandan.\n3. Publish the CLI beta.\n4. The CLI downloads only the approved runtime archive.\n5. The CLI verifies the archive SHA before advertising editor readiness.\n\nFor local package verification:\n\n```bash\nbun test\nnpm pack --dry-run\n```\n\nThe npm package must include this README, `bin/linzumi.js`, and the `src`\nruntime files."
+  "readmeFilename": "README.md"
 }

package/src/index.ts

@@ -101,7 +101,7 @@ async function main(args: readonly string[]): Promise<void> {
       process.stdout.write(connectGuideText());
       return;
     case "version":
-      process.stdout.write("linzumi 0.0.10-beta\n");
+      process.stdout.write("linzumi 0.0.11-beta\n");
       return;
     case "auth":
       await runAuthCommand(parsed.args);
@@ -347,7 +347,7 @@ export async function parseRunnerArgs(
   }
 
   if (values.get("version") === true) {
-    process.stdout.write("linzumi 0.0.10-beta\n");
+    process.stdout.write("linzumi 0.0.11-beta\n");
     process.exit(0);
   }