@drawsy/companion 0.1.30 → 0.1.32

package/README.md

@@ -1,78 +1,67 @@
-# Drawsy Companion from your terminal
+# Install Drawsy Companion
 
-The CLI runs the same local Companion server without the desktop app. It connects Drawsy to your existing Codex/OpenCode installation. It does not install either engine, sign you in, or change their authentication settings.
+Choose the desktop app unless you specifically want to control Companion from a terminal.
 
-## Requirements
+## Desktop app: one line, no Node.js needed
 
-- Windows, macOS, or Linux.
-- Node.js 22 or later with npm, installed for your user account.
-- The public npm package [@drawsy/companion](https://www.npmjs.com/package/@drawsy/companion).
+Open Terminal on macOS/Linux, or Command Prompt or PowerShell on Windows. The desktop app does not need Node.js, npm, administrator access, or `sudo`.
 
-The package is published under Drawsy's npm account. A public package does not require a paid private npm plan. No paid app signing certificate or Microsoft Store approval is required for this Node.js CLI package; the separate desktop app has its own release requirements.
+macOS (Apple Silicon) or Linux (x64):
 
-## Install permanently
+```sh
+curl -fsSL https://raw.githubusercontent.com/DrawsyAI/drawsy-ai-companion/main/scripts/install.sh | sh
+```
 
-Install the public npm package:
+Windows (64-bit), in Command Prompt or PowerShell:
 
-```sh
-npm install --global --ignore-scripts @drawsy/companion
+```cmd
+winget install --id 9PD4MGJ9BW4F --source msstore
 ```
 
-This installs the CLI globally; npx is not needed. npm must be configured so your user account can install global packages; this flow does not request administrator access.
+This installs the Store version. You can also [open the Microsoft Store listing](https://apps.microsoft.com/detail/9PD4MGJ9BW4F). The GitHub release page still includes an unsigned Windows `.exe` and `.zip` for people who specifically need those files; Windows may show a security warning for them.
 
-Once installed, run:
+The macOS/Linux command downloads the latest stable GitHub release, checks its SHA-256 checksum, installs it for your account, and opens Companion. To update the desktop app, close Companion and run the same install command again. To update the Windows Store app, update it through Microsoft Store. Supported builds are Apple Silicon macOS, 64-bit Windows, and x64 Linux.
 
-```sh
-drawsy-companion setup
-```
+The desktop app stays available in the tray/menu bar while it is open. It does not start automatically when you sign in. Closing its window leaves it running in the background; choose **Quit Drawsy Companion** from the tray/menu to stop it.
 
-Running `drawsy-companion` by itself shows the local status without changing startup settings. `setup` starts Companion in the background and enables startup when you sign in. Then open [Drawsy](https://drawsyai.com), the URL allowed by the Companion connection policy. Closing the terminal does not stop the background server.
+## Terminal CLI: background service and controls
 
-To install and set up in one line:
+Choose this if you want Companion to run without its desktop window and start when you sign in. It requires Node.js 22 or later to remain installed. Use npm, pnpm, or Bun only if you already have it; there is no need to install another package manager.
 
-macOS/Linux:
+macOS/Linux, using npm:
 
 ```sh
-npm install --global --ignore-scripts @drawsy/companion && drawsy-companion setup
+npm install --global --ignore-scripts @drawsy/companion@latest && drawsy-companion setup
 ```
 
-Windows PowerShell:
+Windows PowerShell, using npm:
 
 ```powershell
-npm.cmd install --global --ignore-scripts @drawsy/companion; if ($LASTEXITCODE -eq 0) { drawsy-companion.cmd setup }
+npm.cmd install --global --ignore-scripts @drawsy/companion@latest; if ($LASTEXITCODE -eq 0) { drawsy-companion.cmd setup }
 ```
 
-The Windows `.cmd` commands avoid requiring a PowerShell script execution policy change.
-
-### Optional GitHub tarball source
-
-If you prefer to install a GitHub release tarball, use its versioned `.tgz` asset. For CLI version 0.1.30:
-
-```sh
-npm install --global --ignore-scripts https://github.com/DrawsyAI/drawsy-ai-companion/releases/download/cli-v0.1.30/drawsy-companion-0.1.30.tgz
-```
+If you already use a different package manager, run only its command:
 
-The tarball is built by this repository's CLI release workflow and is available after its draft release is published. Use the tarball asset, not the desktop ZIP or AppX.
+- macOS/Linux with pnpm: `pnpm add --global --ignore-scripts @drawsy/companion@latest && drawsy-companion setup`
+- macOS/Linux with Bun: `bun add --global --ignore-scripts @drawsy/companion@latest && drawsy-companion setup`
+- Windows PowerShell with pnpm: `pnpm.cmd add --global --ignore-scripts @drawsy/companion@latest; if ($LASTEXITCODE -eq 0) { drawsy-companion.cmd setup }`
+- Windows PowerShell with Bun: `bun add --global --ignore-scripts @drawsy/companion@latest; if ($LASTEXITCODE -eq 0) { drawsy-companion.cmd setup }`
 
-## Commands
+`setup` starts Companion in the background and enables it when you sign in. Useful commands:
 
 ```sh
-drawsy-companion start
-drawsy-companion stop
 drawsy-companion status
 drawsy-companion logs
-drawsy-companion serve
-drawsy-companion autostart enable
+drawsy-companion start
+drawsy-companion stop
 drawsy-companion autostart disable
 ```
 
-`serve` keeps the server visible in your current terminal. Press Ctrl+C to stop it. `status` reports whether the local server is running. Startup at login uses Windows Task Scheduler, macOS launchd, or Linux's user systemd service; Linux requires a working user systemd session. `start` alone does not enable startup at login.
-
-The desktop app and CLI use the same local server address. Quit the desktop app before switching to the CLI; an existing server is not silently replaced or stopped.
+On Windows, use `drawsy-companion.cmd` in PowerShell. Desktop app and CLI use the same local server; close the desktop app before starting the CLI. The CLI will not stop or replace another Companion.
 
-## Update or remove
+## Updates and removal
 
-The CLI does not update itself. npm distributes the package; Node runs it. To update, stop the running server first. If startup at sign-in is enabled, `autostart disable` also stops it:
+The desktop app and CLI update separately. To update the desktop app, close it and run its installer command again. To update the CLI, disable sign-in startup, stop it, install the latest package with the same package manager, then run setup again. Example for npm:
 
 ```sh
 drawsy-companion autostart disable
@@ -80,9 +69,7 @@ npm install --global --ignore-scripts @drawsy/companion@latest
 drawsy-companion setup
 ```
 
-Run `setup` after installation only if you want Companion to start at sign-in. Otherwise, run `drawsy-companion start` when you want it for the current login session. If startup was already disabled, use `drawsy-companion stop` before installing the update instead.
-
-Before removing the package, disable startup at login, stop Companion, and remove the package:
+To remove the CLI, disable startup and stop it first, then uninstall the package with the same package manager:
 
 ```sh
 drawsy-companion autostart disable
@@ -90,12 +77,12 @@ drawsy-companion stop
 npm uninstall --global @drawsy/companion
 ```
 
-This does not uninstall your Codex/OpenCode installation.
-
-## Release preparation
+Neither install route installs, updates, or signs in to Codex or OpenCode. Keep using the installation and login flow you already have for those tools.
 
-The first public version, 0.1.28, was built and uploaded by GitHub Actions and approved through npm's staged publication flow. Follow [the npm publishing guide](https://github.com/DrawsyAI/drawsy-ai-companion/blob/main/docs/npm-publishing.md) for GitHub trusted publishing setup. Future public package releases use this repository's **Publish Companion CLI to npm** GitHub workflow. It requires the current `main` commit, rejects a mismatched existing CLI version tag, builds and packages the CLI, and publishes the package with npm provenance. It runs no tests and launches no app or server.
+## Release sources
 
-The **Build Companion CLI release** GitHub workflow builds and packages a selected commit, runs no tests, and launches no app or server. It uploads the tarball and `CLI-SHA256SUMS` to a draft release named `cli-v` followed by the package version. Review and manually verify the draft before publishing it; existing published releases are never replaced. This GitHub tarball is an optional install source.
+- macOS and Linux desktop installers are built and published to this repository's [GitHub Releases](https://github.com/DrawsyAI/drawsy-ai-companion/releases/latest). The release page also retains the unsigned Windows `.exe` and `.zip` alternate. The Windows Store package is built separately and submitted through Partner Center.
+- The npm CLI is published separately by the repository's **Publish Companion CLI to npm** GitHub workflow. Installing or updating the desktop app does not publish or update the npm package.
+- The CLI release tarball excludes Electron, the desktop window, build dependencies, personal configuration, and credentials.
 
-The package contains the compiled local server, bundled Drawsy skills, and npm runtime dependency declarations. It excludes Electron, the desktop UI, build dependencies, personal configuration, and credentials. npm installs the declared runtime dependencies when installing the tarball.
+For maintainers: desktop releases follow a version tag matching `package.json` (`v` followed by the package version) and are built by the release workflow. npm releases require a package version bump on `main` and a deliberate run of **Publish Companion CLI to npm** in GitHub Actions. The two release routes do not trigger each other.

package/dist/drawsy/bridge.js

@@ -331,7 +331,9 @@ export const createDrawsyBridge = (options = {}) => {
             }
         }
     };
-    const closeSession = (session) => {
+    const closeSession = (session, event) => {
+        if (event)
+            emit(session, event);
         sessions.delete(session.id);
         if (session.conversationId &&
             conversationSessions.get(session.conversationId)?.id === session.id) {
@@ -1767,8 +1769,9 @@ export const createDrawsyBridge = (options = {}) => {
                 selections.delete(id);
         }
         for (const session of sessions.values()) {
-            if (now - session.touchedAt > 30 * 60 * 1000)
-                closeSession(session);
+            if (now - session.touchedAt > 30 * 60 * 1000) {
+                closeSession(session, { type: "session.closed", data: { reason: "idle" } });
+            }
         }
     }, 60_000);
     cleanup.unref();

package/dist/drawsy/codex-app-server.js

@@ -774,6 +774,7 @@ export class CodexAppServer {
     nextId = 1;
     threadId = null;
     turnActive = false;
+    hasSubmittedTurn = false;
     activeTurnId = null;
     activeDrawMode = false;
     nativeBrowserFailureInterruptSent = false;
@@ -1319,6 +1320,9 @@ export class CodexAppServer {
         this.activeDrawMode = pointerDrawMode;
         this.nativeBrowserFailureInterruptSent = false;
         try {
+            // Once a user turn reaches Codex, never replace a missing rollout with an
+            // empty thread while changing settings.
+            this.hasSubmittedTurn = true;
             const result = (await this.request("turn/start", {
                 threadId: this.threadId,
                 cwd: this.folderPath,
@@ -1675,12 +1679,27 @@ export class CodexAppServer {
         const previousMetadata = { ...this.agentMetadata };
         const previousControls = this.lastControls;
         if (internetChanged) {
-            await this.startAgentThread({
+            const threadOptions = {
                 internetEnabled: nextInternet,
                 model: selectedModel?.model || this.agentMetadata.model,
                 effort: settings.effort || this.agentMetadata.reasoningEffort,
-                nativeThreadId: previousThreadId,
-            });
+            };
+            try {
+                await this.startAgentThread({
+                    ...threadOptions,
+                    nativeThreadId: previousThreadId,
+                });
+            }
+            catch (error) {
+                if (!isCodexThreadMissingError(error) ||
+                    this.session.nativeThreadId ||
+                    this.hasSubmittedTurn) {
+                    throw error;
+                }
+                // Codex does not persist a new thread until its first user turn.
+                // Reconfigure this empty thread without trying to resume its rollout.
+                await this.startAgentThread(threadOptions);
+            }
         }
         try {
             await this.request("thread/settings/update", {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@drawsy/companion",
-  "version": "0.1.30",
+  "version": "0.1.32",
   "private": false,
   "type": "module",
   "description": "Drawsy's local Companion server and background command-line controls",

package/skills/drawsy-fast-diagrams/SKILL.md

@@ -8,7 +8,7 @@ description: Generate semantic Mermaid source and render it through Drawsy Fast
 Use this skill only for Fast Mode canvas diagram work.
 
 - Read the current canvas and call `get_canvas_capabilities`. When present, treat `diagramCode.nativeEditableTypes` and `diagramCode.sourceMaxBytes` as the converter's runtime authority. Choose Mermaid syntax from the request's meaning and actual support; do not use a fixed intent-to-family mapping or prescribe a visual style. Keep the user's facts, supplied numbers, canvas context, and existing visual language intact. Never invent data to force a chart.
-- The current converter has editable native handlers for flowchart/graph, packet, architecture, ER, use case, mindmap, tree view, XY chart, pie, radar, and Sankey families. The installed parser may accept more syntax and render it as an image. Check `outputKind` (`editable-vector` or `image-fallback`) and `diagramType`; do not promise that fallback content stays editable. Mermaid's official syntax references follow `https://mermaid.js.org/syntax/<diagram-name>.html`; documentation can describe newer syntax than Drawsy's bundled parser.
+- Discover editable diagram families from the live `diagramCode.nativeEditableTypes` catalog rather than a bundled list, so newly installed converters are available automatically. The installed parser may accept more syntax and render it as an image. Check `outputKind` (`editable-vector` or `image-fallback`) and `diagramType`; do not promise that fallback content stays editable. Mermaid's official syntax references follow `https://mermaid.js.org/syntax/<diagram-name>.html`; documentation can describe newer syntax than Drawsy's bundled parser.
 - Use `render_diagram_code` to create a whole diagram. Fast Mode still supports normal canvas management: use `apply_canvas_changes` to update existing elements or delete existing elements, including failed or intermediate work you created; never delete unrelated content. Use `create_or_update_connector` and `set_container_label` for existing objects, and image insertion/replacement, canvas capture, and live preview when requested. The runtime checks raw upserts against the live canvas; never use them to create new shapes or diagram structures. The diagram result includes `outputKind`, `diagramType`, `elementCount`, inserted `elementIds`, and `bounds`; use those IDs and bounds to review the inserted group.
 - Do not use native pointer gestures or another canvas path to bypass the diagram converter when creating a whole diagram. Preserve the user's visual choices when managing existing content.
 - A syntax correction is for a request that failed conversion: make at most one focused correction and retry with a new `operationId`; reuse an id only to retry the same unchanged request. A post-render correction follows a successful conversion after inspection: read the canvas again, make a focused correction, and set `replaceOperationId` to the prior successful operation id so only that converter-created group is replaced.