cicy-desktop 2.1.150 → 2.1.152

package/.github/workflows/mac-app-release.yml

@@ -211,8 +211,17 @@ jobs:
             SCR="pkgscripts-$ARCH"; rm -rf "$SCR"; mkdir -p "$SCR"
             cp scripts/mac-allinone/postinstall "$SCR/postinstall"; chmod +x "$SCR/postinstall"
             PKG="cicy-desktop-$VER-$ARCH.pkg"
-            if pkgbuild --root "$ROOT" --scripts "$SCR" --identifier com.cicy.desktop \
-                 --version "$VER" --install-location / "$PKG"; then
+            # Disable bundle relocation. Without this the macOS Installer "relocates" the
+            # install to wherever an existing com.cicy.desktop bundle already lives (e.g. a
+            # leftover copy in ~/Downloads from a tarball test) instead of /Applications —
+            # so the app vanishes from /Applications. BundleIsRelocatable=false pins it to
+            # the payload path (/Applications) no matter what's already on disk.
+            PLIST="component-$ARCH.plist"
+            pkgbuild --analyze --root "$ROOT" "$PLIST"
+            /usr/libexec/PlistBuddy -c "Set :0:BundleIsRelocatable false" "$PLIST" 2>/dev/null \
+              || plutil -replace 0.BundleIsRelocatable -bool NO "$PLIST" || true
+            if pkgbuild --root "$ROOT" --component-plist "$PLIST" --scripts "$SCR" \
+                 --identifier com.cicy.desktop --version "$VER" --install-location / "$PKG"; then
               gh release upload "${{ steps.meta.outputs.tag }}" "$PKG" --repo "$GITHUB_REPOSITORY" --clobber
               echo "uploaded $PKG ($(du -h "$PKG" | cut -f1))"
             else

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cicy-desktop",
-  "version": "2.1.150",
+  "version": "2.1.152",
   "description": "CiCy - AI-powered operating system browser",
   "main": "src/main.js",
   "bin": {

package/src/main.js

@@ -1081,13 +1081,18 @@ electronApp.whenReady().then(async () => {
   }
 
   // Periodic WHOLE-desktop snapshot → ~/cicy-files/desktop-snapshot/desktop.b64
-  // (≤600px wide JPEG). ALL PLATFORMS: the cloud (cicy-code) fetches it via the
-  // dedicated non-dangerous `desktop_snapshot` RPC tool, which reads this fresh
-  // file — so there's no per-call screen capture, hence no macOS Screen-Recording
-  // prompt and no consent dialog. On Windows the capture runs in a --disable-gpu
-  // child electron (GDI path, works over RDP; main app GPU intact); on mac/linux
-  // it's an in-process native-capture loop (screencapture / scrot).
-  if (!global.__cicyDesktopSnapStarted) {
+  // so the cloud (cicy-code) can read the screen via the `desktop_snapshot` tool.
+  // Windows uses a --disable-gpu child (GDI, no prompt); linux uses scrot.
+  //
+  // macOS: this spawns `screencapture`, which DOES trigger the Screen-Recording TCC
+  // prompt — and on an ad-hoc-signed build (no Apple cert) the grant never sticks, so
+  // the prompt fires over and over. So it's OFF by default on macOS (most users —
+  // docker/team management — don't need the agent to watch their screen). Opt in with
+  // CICY_DESKTOP_SNAPSHOT=1. Other platforms stay on (opt out with =0).
+  const __snapOn = process.platform === "darwin"
+    ? process.env.CICY_DESKTOP_SNAPSHOT === "1"
+    : process.env.CICY_DESKTOP_SNAPSHOT !== "0";
+  if (!global.__cicyDesktopSnapStarted && __snapOn) {
     global.__cicyDesktopSnapStarted = true;
     try {
       const info = require("./utils/desktop-snapshot").startDesktopSnapshots();