cicy-desktop 2.1.235 → 2.1.237

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/NOTICE

@@ -0,0 +1,4 @@
+CiCy Desktop
+Copyright 2026 CiCy AI
+
+This product includes software developed by CiCy AI (https://cicy-ai.com).

package/README.md

@@ -1,49 +1,29 @@
 # CiCy Desktop
 
-CiCy Desktop is an Electron-based desktop automation worker with a small cluster control plane.
+CiCy Desktop is an Electron-based desktop automation worker with a small cluster
+control plane. It exposes ~100+ system tools — Chrome/CDP control, in-page
+JavaScript, screenshots, clipboard, file ops, shell/node/python exec, system
+info — over MCP and HTTP, plus a homepage UI for managing local and remote
+teams. The `cicy-code` sidecar daemon is acquired at runtime (`npx cicy-code` on
+mac/linux, Docker-in-WSL on Windows), not bundled.
 
-The project now has **two separate CLIs**:
+## Screenshots
 
-- `cicy` / `cicy-desktop`: start, stop, inspect, and manage the local desktop/cluster lifecycle
-- `cicy-rpc`: call worker RPC tools such as `ping`, `tools`, `open_window`, and `exec_js`
+The homepage — your teams (the local sidecar, private-cloud teams, and custom
+remote nodes), each a card you open as a tab:
 
-If you remember the old unified CLI model, that is no longer the current behavior.
+![CiCy Desktop homepage — team list](assets/my_teams.png)
 
-## CLI split
+A team opened as a tab — the agent roster on the left, a live conversation on
+the right:
 
-### `cicy` / `cicy-desktop`
-Use this for local desktop/cluster management only:
+![CiCy Desktop team workspace](assets/team.png)
 
-```bash
-cicy start
-cicy stop
-cicy status
-cicy restart
-cicy logs
-```
-
-Equivalent alias:
-
-```bash
-cicy-desktop start
-```
-
-Notes:
-- `npm start` runs the same desktop lifecycle entrypoint
-- `cicy --json` / `cicy -j` is not supported
-- RPC/tool commands moved to `cicy-rpc`
+## CLI — `cicy-desktop`
 
-### `cicy-rpc`
-Use this for RPC/tool calls only:
-
-```bash
-cicy-rpc init
-cicy-rpc tools
-cicy-rpc tools open_window
-cicy-rpc ping
-cicy-rpc open_window url=https://example.com
-cicy-rpc --json get_window_info win_id=1
-```
+`cicy-desktop` launches the Electron app — `npm start` and `npx cicy-desktop` run
+the same entrypoint. Self-update with `cicy-desktop --update`; `--version` and
+`--help` print info.
 
 ## Run (end users, no clone)
 
@@ -51,317 +31,100 @@ First run launches the Electron app and drops a desktop shortcut (Windows
 `.lnk` / macOS `.app` / Linux `.desktop`, all with the CiCy icon); double-click
 it afterwards.
 
-**CN needs the electron mirror.** A fresh machine has no cached electron
-binary, so electron's postinstall would hit GitHub releases and fail. Point
-`ELECTRON_MIRROR` + the npm registry at npmmirror.
+**CN needs the electron mirror.** A fresh machine has no cached electron binary,
+so electron's postinstall would otherwise hit GitHub releases and fail — point
+`ELECTRON_MIRROR` and the npm registry at npmmirror.
 
-### Windows — global install (NOT npx)
+### Windows — global install (not npx)
 
-npx's libnpmexec lock false-positives as `ECOMPROMISED` / "Lock compromised" on
-Windows boxes with realtime antivirus (Defender touches `node_modules` mtimes
-mid-install → the lock heartbeat aborts). `npm i -g` has no such lock, so
-Windows installs globally and launches the global bin:
+npx's libnpmexec lock false-positives as "Lock compromised" on Windows boxes
+with realtime antivirus (Defender touches `node_modules` mtimes mid-install).
+`npm i -g` has no such lock:
 
 ```cmd
 cmd /c "set ELECTRON_MIRROR=https://npmmirror.com/mirrors/electron/&& npm i -g cicy-desktop --registry=https://registry.npmmirror.com&& cicy-desktop"
 ```
 
-Re-run the same line to update. The generated `.lnk` runs the global
-`cicy-desktop` bin (no npx).
+Re-run the same line to update.
 
 ### macOS / Linux — npx
 
-npx's lock works fine here:
-
 ```bash
 ELECTRON_MIRROR=https://npmmirror.com/mirrors/electron/ npm_config_registry=https://registry.npmmirror.com npx -y cicy-desktop
 ```
 
 Outside CN (or once electron is cached) a plain `npx -y cicy-desktop` is enough.
 
-## Quick start (development)
-
-### 1. Install
+## Develop
 
 ```bash
 git clone git@github.com:cicy-ai/cicy-desktop.git
 cd cicy-desktop
 npm install
-```
-
-### 2. Start the local desktop worker
-
-```bash
-cicy start
-# or
 npm start
 ```
 
-### 3. Initialize RPC config
-
-```bash
-cicy-rpc init
-```
-
-This creates `~/global.json` if it does not exist.
+Config lives in `~/cicy-ai/global.json` (API token, gateway key, node list). The
+worker reads its `Authorization: Bearer <token>` from there.
 
-### 4. Verify connectivity
+### Homepage UI (`workers/render`)
 
-```bash
-cicy-rpc ping
-```
+The desktop homepage — team cards, tabs, everything the user sees — is a Vite +
+React app in `workers/render/`. The Electron main process loads a **prebuilt
+snapshot** from `src/backends/homepage-react/` (a `file://` SPA: works offline,
+no mixed-content issues embedding the team webview). Source and snapshot are two
+different things — `scripts/build-homepage.cjs` (run on every `build:*` /
+publish) rebuilds the snapshot so it never lags behind `workers/render/`.
 
-### 5. Inspect available tools
+Build → ship the snapshot:
 
 ```bash
-cicy-rpc tools
-cicy-rpc tools open_window
-```
-
-### 6. Open a page
-
-```bash
-cicy-rpc open_window url=https://example.com
-```
-
-## Homepage renderer (`workers/render`)
-
-The cicy-desktop homepage UI lives in `workers/render` — a Vite + React app that
-the Electron main process loads into the primary BrowserWindow.
-
-### Where it's served from
-
-- **All platforms (Win/Mac/Linux)**: local
-  `file:///.../src/backends/homepage-react/index.html` (a synced copy of
-  `workers/render/dist/`). `pickHomepageURL()` returns this unconditionally —
-  the bundled `file://` SPA works offline, is fast, and lets the homepage
-  embed the HTTP team-assistant webview without mixed-content issues.
-- **Dev**: set `CICY_HOMEPAGE_URL=http://localhost:8173` to load the live
-  vite dev server instead. See "Dev workflow" below.
-
-### Build → ship layout
-
-```bash
-# build the SPA
 cd workers/render && npm run build
-# copy into the file:// SPA folder cicy-desktop's main process loads from
 rsync -av --delete dist/ ../../src/backends/homepage-react/
 ```
 
-### Dev workflow
-
-Vite runs **on Mac**. Source edits happen on Linux and are rsynced over —
-Linux itself never serves the SPA. There used to be a Linux-runs-Vite +
-`ssh -R` tunnel option; it was dropped because the tunnel silently dropped
-mid-session and the resulting blank page wasted hours.
-
-```bash
-# On Linux: sync source to Mac
-rsync -avz --delete \
-  --exclude=node_modules --exclude=dist --exclude=.git \
-  ~/projects/cicy-desktop/ mac:~/projects/cicy-desktop/
-
-# On Mac: start Vite + run source-mode Electron
-ssh mac
-cd ~/projects/cicy-desktop/workers/render
-npm install               # first time only
-npm run dev               # serves http://localhost:8173
-
-# In another shell on Mac
-cd ~/projects/cicy-desktop
-pkill -f "MacOS/CiCy Desktop" 2>/dev/null   # stop any installed .app first
-bash -c 'set -a; . ./.env.dev; set +a; npm start'
-# .env.dev sets CICY_HOMEPAGE_URL=http://localhost:8173 so Electron loads
-# the Vite bundle (HMR enabled) instead of the bundled file:// one.
-```
-
-Now edit `workers/render/src/App.jsx` on Linux → `rsync` to Mac →
-Vite HMR picks it up instantly. No Electron restart for React/CSS edits.
-
-> **Fallback**: if `CICY_HOMEPAGE_URL` is set but unreachable (Vite not
-> started, port conflict), `homepage-window.js` falls back to the bundled
-> `file://` SPA so the window never stays blank.
+Fast dev loop (React/CSS HMR, no Electron restart): run Vite and source-mode
+Electron with `CICY_HOMEPAGE_URL=http://localhost:8173` set (via `.env.dev`).
+`src/backends/homepage-window.js` falls back to the bundled `file://` SPA if that
+URL is unreachable, so the window never stays blank. Full platform/loop details
+(Mac fast loop, Windows packaged, the three reload classes) are in the worker's
+`CLAUDE.md`.
 
-`src/backends/homepage-window.js` URL priority:
-1. `CICY_HOMEPAGE_URL` env (dev override) → falls back to `file://` on load failure
-2. All platforms → bundled `file://src/backends/homepage-react/index.html`
+## Calling tools
 
-### Shipping SPA changes to Windows (hotpatch)
-
-Windows loads the same local `file://` SPA as Mac/Linux — the running
-npm-global install reads `src/backends/homepage-react/`. So shipping a SPA
-change = sync the files, **not** redeploy a Worker (there is no remote
-homepage Worker for Windows anymore):
-
-```bash
-# build + mirror into the file:// folder
-cd workers/render && npm run build
-rsync -av --delete dist/ ../../src/backends/homepage-react/
-# package backend + SPA and push to the Windows box
-cd ../.. && tar czf /tmp/cicy-hotpatch.tgz src build bin package.json
-scp /tmp/cicy-hotpatch.tgz win:'C:/Users/Administrator/cicy-hotpatch.tgz'
-ssh win 'cd /d "C:\Users\Administrator\AppData\Roaming\npm\node_modules\cicy-desktop" && tar -xzf C:\Users\Administrator\cicy-hotpatch.tgz'
-# relaunch in the *interactive* session (session 0 can't paint a GUI window)
-ssh win 'schtasks /run /tn StartElectron'
-```
+The worker dispatches its tools three ways:
 
-The `StartElectron` scheduled task is set to "interactive only" so the
-relaunched window appears on the user's RDP desktop. `bin/cicy-desktop`
-always opens `--remote-debugging-port=9221`, so verify the reload over CDP.
-
-## Canonical config
-
-`cicy-rpc` reads `~/global.json`.
-
-Use this format:
-
-```json
-{
-  "api_token": "your-default-token",
-  "cicyDesktopNodes": {
-    "local": {
-      "api_token": "",
-      "base_url": "http://localhost:8101"
-    },
-    "windows": {
-      "api_token": "your-windows-token",
-      "base_url": "http://windows-host:8101"
-    }
-  }
-}
-```
+- **In-page (IPC):** `window.electronRPC(toolName, args)` — the bridge injected
+  into trusted BrowserWindows.
+- **HTTP (REST):** `POST /rpc/:toolName` with `Authorization: Bearer <token>` —
+  served by the master, which forwards to the selected worker. `401
+  Unauthorized` means the token is wrong or missing.
+- **From an agent:** the `agent-desktop` / `agent-electron` / `agent-chrome`
+  skills drive a connected client over WebSocket
+  (`agent-desktop rpc <tool>`, `agent-desktop exec …`, etc.).
 
-Rules:
-- `cicyDesktopNodes.<name>.base_url` is the worker base URL
-- `cicyDesktopNodes.<name>.api_token` overrides the top-level `api_token` for that node
-- `CICY_NODE=<name>` selects the target node
-- default node is `local`
+Discover tools at runtime:
 
-Example:
+- `list_tools` meta-tool (`electronRPC("list_tools")` / `agent-desktop rpc list_tools`)
+- `GET /openapi.json` (browsable at `/docs`)
 
-```bash
-CICY_NODE=windows cicy-rpc get_windows
-```
-
-## Main workflows
-
-### Local lifecycle management
-
-```bash
-cicy start
-cicy status
-cicy logs
-```
-
-### Local tool calls
-
-```bash
-cicy-rpc ping
-cicy-rpc tools
-cicy-rpc open_window url=https://example.com
-cicy-rpc get_window_info win_id=1
-cicy-rpc --json get_window_info win_id=1
-```
-
-### Remote or multi-node tool calls
-
-```bash
-CICY_NODE=windows cicy-rpc ping
-CICY_NODE=windows cicy-rpc get_windows
-CICY_NODE=windows cicy-rpc open_window url=https://example.com
-```
-
-## What the worker can do
-
-The worker exposes automation tools for:
-
-- browser window lifecycle and navigation
-- page interaction through CDP
-- JavaScript execution inside pages
-- screenshots, downloads, and clipboard operations
-- system window control and system information
-- worker/master cluster coordination
-
-For the exact tool list, use:
-
-```bash
-cicy-rpc tools
-```
+The worker exposes automation for: browser window lifecycle and navigation, CDP
+page interaction, in-page JavaScript, screenshots / downloads / clipboard,
+system window control and system info, and worker/master cluster coordination.
 
 ## Architecture
 
-Current source of truth in code:
-
-- worker/server entry: `src/main.js:1`
-- RPC CLI: `src/cli/rpc.js:1`
-- desktop lifecycle CLI: `bin/cicy-desktop:1`
-- tool implementations: `src/tools/*`
-
-At a high level:
-- the **worker** dispatches tools two ways: in-process via `ipcMain.handle("rpc", …)` (`src/main.js`, what `window.electronRPC(tool, args)` rides) and over HTTP. The full, live tool index is `GET /openapi.json` (browse at `/docs`); call `list_tools` to enumerate from the RPC/IPC side.
-- REST tool invocation (`POST /rpc/:toolName`, used by `cicy-rpc`) is served by the **master** (`src/master/master-routes.js`), which forwards to the selected worker.
-- RPC routes are protected by auth and return `401 Unauthorized` when the token is wrong or missing
-- the desktop CLI starts a local master + worker cluster and provides status/log management
-
-## Authentication
-
-RPC requests use the token loaded from `~/global.json`.
-
-- CLI calls made through `cicy-rpc` send `Authorization: Bearer <token>`
-- worker routes return `401 Unauthorized` if auth fails
-- per-node token comes from `cicyDesktopNodes.<name>.api_token`, falling back to top-level `api_token`
-
-## Troubleshooting
-
-### `fetch failed`
-Usually means the target node is unreachable.
-
-Check:
-
-```bash
-cicy status
-cicy-rpc ping
-CICY_NODE=windows cicy-rpc ping
-```
-
-If needed, verify the node's `base_url` in `~/global.json`.
-
-### `HTTP 401 Unauthorized`
-Usually means the URL is correct but the token is wrong.
-
-Check:
-- `api_token`
-- `cicyDesktopNodes.<name>.api_token`
-- `cicyDesktopNodes.<name>.base_url`
-
-Then retry:
-
-```bash
-cicy-rpc ping
-```
-
-### Window opened but page is not ready yet
-Query the window state and wait for loading to finish:
-
-```bash
-cicy-rpc get_window_info win_id=1
-```
-
-For remote nodes:
-
-```bash
-CICY_NODE=windows cicy-rpc get_window_info win_id=1
-```
-
-## Documentation
-
-Use the root README as the entrypoint, then go deeper here:
+- worker/server entry — `src/main.js`
+- desktop lifecycle CLI — `bin/cicy-desktop`
+- tool implementations — `src/tools/*`
+- master (routes `POST /rpc/:toolName` to workers) — `src/master/master-routes.js`
+- homepage source — `workers/render/` → built into `src/backends/homepage-react/`
 
-- [CLI split and usage](./skills/cicy-cli/README.md)
-- [RPC CLI details](./packages/cicy-rpc/README.md)
-- [REST API notes](./docs/REST-API.md)
-- [Desktop service skill](./skills/cicy-desktop-service/README.md)
+The **worker** dispatches tools in-process via `ipcMain.handle("rpc", …)` (what
+`window.electronRPC` rides) and over HTTP; the live tool index is
+`GET /openapi.json`. The desktop CLI starts a local master + worker cluster and
+manages status/logs.
 
 ## License
 
-MIT
+[Apache-2.0](./LICENSE).

package/bin/cicy-desktop

@@ -268,7 +268,7 @@ for (let i = 0; i < args.length; i++) {
   } else if (arg === "-v" || arg === "--version") {
     showVersion = true;
   } else if (arg === "-j" || arg === "--json") {
-    console.error("[x] --json is only supported by cicy-rpc");
+    console.error("[x] --json is not supported");
     process.exit(1);
   } else if (arg === "-cn" || arg === "--cn") {
     useCNMirror = true;
@@ -343,9 +343,7 @@ Examples:
   cicy status
   cicy restart
   cicy logs
-  cicy --port 8201
-
-RPC commands moved to: cicy-rpc`);
+  cicy --port 8201`);
 }
 
 function update() {

package/generate-openapi.js

@@ -1,4 +1,7 @@
 #!/usr/bin/env node
+// Copyright 2026 CiCy AI
+// SPDX-License-Identifier: Apache-2.0
+
 
 const fs = require('fs');
 const path = require('path');