{
  "name": "local-operator-ui",
  "version": "0.52.13",
  "productName": "Local Operator",
  "description": "User interface for AI agent assistants that run Python code safely on your device through an intuitive chat interface. Supports local and cloud LLM models with built-in security features.",
  "main": "./out/main/index.js",
  "bin": {
    "local-operator-ui": "./bin/local-operator-ui.js"
  },
  "license": "MIT",
  "author": {
    "name": "Radient Inc.",
    "email": "contact@radienthq.com",
    "url": "https://github.com/radient-ml"
  },
  "contributors": [
    {
      "name": "Damian Tran",
      "email": "damian@radienthq.com",
      "url": "https://github.com/damianvtran"
    }
  ],
  "repository": {
    "type": "git",
    "url": "https://github.com/damianvtran/local-operator-ui.git"
  },
  "homepage": "https://github.com/damianvtran/local-operator-ui#readme",
  "bugs": {
    "url": "https://github.com/damianvtran/local-operator-ui/issues"
  },
  "keywords": [
    "local-operator",
    "radient",
    "agent",
    "ai",
    "python",
    "tool use",
    "ui",
    "electron",
    "react"
  ],
  "files": [
    "out",
    "bin",
    "LICENSE",
    "README.md"
  ],
  "publishConfig": {
    "access": "public"
  },
  "scripts": {
    "start": "electron-vite preview",
    "app:headless": "LOCAL_OPERATOR_NO_NOTIFICATIONS=1 LOCAL_OPERATOR_UI_TELEMETRY=off LOCAL_OPERATOR_UI_WINDOW_MODE=headless electron . --window-mode=headless",
    "//app:headless": "The agent-driven launch, so it carries the notification kill switch (scripts/notifications-off.mjs) AND the telemetry switch (scripts/telemetry-off.mjs). `headless` silences this app's OWN banner and cannot reach the backend's: the app spawns a backend, and that backend's parked-gate announcement ends at `osascript` on macOS, whose banner lands in the operator's real Notification Center attributed to Script Editor. The telemetry switch matters because a run of this line boots the real app against the live PostHog project key its build carries, in BOTH processes - main constructs a client and the renderer mounts one - so an unswitched run is counted as a product user and recorded as a session replay. `pnpm start` and `pnpm dev` are a person's own app at their own screen and keep both their banners and their analytics.",
    "//dev": "The `.env` loader is `dotenv-cli`, whose default is NOT to overwrite a variable that is already in the environment - and that non-override is load-bearing rather than incidental. `dev` used to be `npx dotenv-cli -e .env -- bash -c 'export $(grep -v '^#' .env | xargs) && electron-vite dev'`, added so a checkout's `.env` would beat variables a Cursor/vscode terminal injects; that inner re-export runs AFTER any prefix the caller put on the line, so `pnpm dev:headless` (whose whole guarantee is the launch-side switch) could be re-armed by a `.env` line reading LOCAL_OPERATOR_UI_TELEMETRY= (empty, which the app reads as unset, so telemetry stays ON with no off-line printed) or =on. The principle the telemetry and notification switches rest on is that a LAUNCH's environment outranks a FILE, so the clobbering re-export is gone rather than reordered: a variable the launch set now wins for every key, and the file still supplies the ones it did not. The editor-injection case loses that fight, deliberately - one rule for all keys is what makes the switches hold. Pinned by scripts/telemetry-spawn-sites.test.mjs, which runs this body against a scratch `.env` in all three shapes.",
    "dev": "npx dotenv-cli -e .env -- electron-vite dev",
    "//dev:headless": "The env var is the only channel this launch can carry a mode on. electron-vite dev spawns Electron itself from its OWN option parser and forwards nothing extra: measured, neither an appended argument nor its shipped ELECTRON_CLI_ARGS passthrough reaches the app's argv (the run reported the default 1380x900 when the passthrough asked for 1024x768). It does not need the flag: a second launch forwards the mode it resolved to the instance holding the lock (src/main/window-raise.ts), which is the channel this env var already feeds.",
    "dev:headless": "LOCAL_OPERATOR_NO_NOTIFICATIONS=1 LOCAL_OPERATOR_UI_TELEMETRY=off LOCAL_OPERATOR_UI_WINDOW_MODE=headless pnpm dev",
    "build": "electron-vite build",
    "//prebuild": "The build compiles main/preload to V8 bytecode for the pinned Electron, so it needs a real node_modules/electron/dist before electron-vite runs. Since Electron 42 nothing fetches that during an install except our own postinstall, so this hook covers the trees that hook cannot reach (--ignore-scripts, or a dist/ removed by hand) and fails the build by name instead of letting it die inside the bytecode step with an ENOENT. build:npm needs no runtime: it deliberately emits plain JS (LOCAL_OPERATOR_UI_NO_BYTECODE=true).",
    "prebuild": "node ./bin/ensure-electron.js",
    "prebuild:npm": "rm -rf out/main out/preload",
    "build:npm": "LOCAL_OPERATOR_UI_NO_BYTECODE=true electron-vite build",
    "postbuild:npm": "chmod +x ./bin/local-operator-ui.js",
    "postbuild": "chmod +x ./bin/local-operator-ui.js",
    "postinstall": "node ./bin/postinstall.js",
    "//prepare": "Wires this clone's pushes through the tracked .githooks/pre-push, so a worktree that would otherwise push ungated is either gated or refused loudly - git skips a hook file that is not there, in silence, which is exactly the state a fresh worktree is in. Not bin/postinstall.js, whose own contract is that it must never fail the install: a wiring that cannot be verified has to say so rather than report a success. Runs on `pnpm install` in a checkout and on a git-based install, and never for a published tarball's consumer, which has no repository to wire. pnpm hooks:install is the same thing by hand; pnpm hooks:check is the read-only form and a non-zero exit when pushes from this checkout are not gated. See scripts/hooks-install.mjs and docs/hooks.md.",
    "//prepare:evidence-fold": "Wires the clone merge driver for docs/evidence/manifest.json, so `git merge` does not stop on a manifest a sibling lane also rewrote. It runs from `prepare` for the same reason the hooks wiring does: a fresh clone (and every worktree of it, since the config is the clone LOCAL one) would otherwise fold with the driver missing, and the failure that produces is a conflict nobody knows to expect. Same contract as the hooks wiring - it fails loudly by hand and never fails the install, where `postinstall` owns the opposite rule. pnpm evidence:fold:install and pnpm evidence:fold:check are the by-hand forms. The driver is not needed for the ordinary fold any more - with the retired tree stamps gone, a merge that only moved `src/` or `scripts/` does not touch this file at all - but it is still what resolves the 18-in-30 folds where two lanes genuinely both edited it.",
    "prepare": "node scripts/hooks-install.mjs --tolerate-failure && node scripts/evidence-fold.mjs --install --tolerate-failure",
    "//hooks:install": "Idempotent, and safe to run at any time: it repoints core.hooksPath at <common git dir>/lop-hooks, whose pre-push runs the gate THE CURRENT WORKTREE carries. The directory lives in the clone's shared git directory and the path is absolute because a relative core.hooksPath is resolved against the working directory and a path that does not resolve is skipped by git without a word - which is how a worktree pushed ungated while reporting no problem.",
    "hooks:install": "node scripts/hooks-install.mjs",
    "hooks:check": "node scripts/hooks-install.mjs --check",
    "//evidence:fold": "Completes an evidence fold: resolves docs/evidence/manifest.json across a merge a FIELD at a time (not whole-file, and not per entry), re-derives the counts from the merged tree, runs the real guards over the result and stages it - so a fold is ONE commit that carries correct values instead of a merge plus a hand re-lay. Reads the three sides from GIT OBJECTS, so it works on a conflicted working file too. It never weakens a guard - every field the manifest still claims about its tree is written by this tool and then checked by the real guards - and a fold that moved only `src/` or `scripts/` now writes NOTHING (`the manifest already describes this tree`), because the `srcTree`/`scriptsTree` pair that used to change on every such merge is retired and is dropped from whichever side still carries it. pnpm evidence:fold:install wires the clone merge driver so `git merge` does not stop on a manifest conflict at all; pnpm evidence:fold:check is the read-only form and exits non-zero when it is not wired. See scripts/evidence-fold.mjs and the evidence discipline in AGENTS.md.",
    "evidence:fold": "node scripts/evidence-fold.mjs",
    "evidence:fold:install": "node scripts/evidence-fold.mjs --install",
    "evidence:fold:check": "node scripts/evidence-fold.mjs --check",
    "lint": "pnpm biome check src bin scripts/linux-sandbox.test.mjs",
    "lint:fix": "pnpm biome check --write src bin scripts/linux-sandbox.test.mjs",
    "//lint:scripts": "`pnpm lint` names the paths it checks by hand, so the whole of `scripts/` - the proof harnesses, evidence rigs and release gates - sat outside the lint and formatter contracts, and a formatter error rode into a merged pull request green. This gate runs the same `biome check` over the `scripts/` files a change touches against a base ref (`origin/main` locally, the merge commit's first parent in CI), so a violation cannot ride in with the diff that introduces it, while the tree's 106 pre-existing offenders are burnt down file by file rather than turned red at once. Widening `pnpm lint` to name `scripts/` outright is the follow-up once that backlog is gone; scripts/check-scripts-lint.mjs holds the measurements and the full rationale.",
    "lint:scripts": "node scripts/check-scripts-lint.mjs",
    "format": "pnpm biome format src",
    "format:fix": "pnpm biome format --write src",
    "prepack": "pnpm run build:npm",
    "check-types:main": "tsc --noEmit -p tsconfig.node.json",
    "check-types:renderer": "tsc --noEmit -p tsconfig.app.json",
    "check-types": "pnpm run check-types:main && pnpm run check-types:renderer",
    "check-changed": "node scripts/ci-scope.mjs --since \"$(git merge-base origin/main HEAD)\" --run",
    "//merge-gate": "Ask the full suite to run on a pull request's current head, and print the run. The gate's ONLY trigger is a label event (`pull_request: [labeled]`, .github/workflows/full-suite.yml), so this removes and re-adds `ready-to-merge`: that is how a head gets its `Merge gate (full suite)` check, and how a head that moved after a push gets it back. Run it only when the review rounds are clean and the head is final; scripts/merge-gate.mjs carries the rationale.",
    "merge-gate": "node scripts/merge-gate.mjs",
    "check-themes": "node scripts/generate-theme-css.mjs --check && node scripts/contrast-contract.mjs && node scripts/check-contrast-presets.mjs && node scripts/check-design-kit.mjs",
    "test:session-cookies": "node scripts/session-cookie-electron.test.mjs",
    "test:window-guards": "node scripts/window-guards-electron.test.mjs",
    "test:window-glass": "node --test scripts/window-glass-cdp.test.mjs",
    "test:tag-dialogs": "node scripts/run-desktop-tests.mjs scripts/chat-tag-dialogs-immediate.test.mjs",
    "//test:affected": "The targeted run a pull request records as evidence now that the desktop suite runs on main and nightly (full-suite.yml) instead of on every PR: the test files a diff can reach through imports and path mentions, plus the tree-wide GUARD_TESTS. `--run` executes them through the guarded runner, `--evidence` prints the PR block. scripts/affected-tests.mjs carries the rationale.",
    "test:affected": "node scripts/affected-tests.mjs",
    "test:guards": "node scripts/affected-tests.mjs --guards --run",
"test:desktop": "node scripts/desktop-test-inventory.mjs run",
    "check-evidence": "node scripts/check-evidence.mjs",
    "check-evidence:parity": "node scripts/evidence-histogram-parity.mjs",
    "check-edit-diffs": "node scripts/check-edit-diffs.mjs",
    "check-runtime-deps": "node scripts/check-runtime-deps.mjs",
    "check-fold-keys": "node scripts/check-fold-keys.mjs",
    "//check-i18n": "The language policy in one command: generator freshness, the literal ratchet, the base-aware added-copy guard, the translation ledger, context parity, then manifest-backed coverage. Split because CI hands the added-copy and coverage halves their base refs; `pnpm check-i18n` runs all three locally with the base resolved to `origin/main`.",
    "check-i18n": "pnpm check-i18n:catalogues && pnpm check-i18n:added-strings && pnpm check-i18n:coverage",
    "//check-i18n:catalogues": "The five catalogue gates: `generate --check` (committed generated types match the English catalogues), `check-duplicates` (raw-text scan for a duplicate key a merge can create silently), `check-strings` (no untranslated literals), `ledger-check` (every shipped locale is audited and its hashes still match) and `context-parity` (sidecars agree with their catalogues).",
    "check-i18n:catalogues": "node scripts/i18n/generate.mjs --check && node scripts/i18n/check-duplicates.mjs && node scripts/i18n/check-strings.mjs && node scripts/i18n/ledger-check.mjs && node scripts/i18n/context-parity.mjs",
    "//check-i18n:added-strings": "The base-aware guard for copy shapes outside the original ratchet: object-literal properties, expression attributes, static template spans, conditionals and concatenations. It fails only on added lines and keeps no stored list; CI passes HEAD^1, the real base of the checked-out pull-request merge. Copy the base tree already carries at the same path, or whose English catalogue message this diff stopped calling t() for in that same file, is reported as RESTORED and never counted as new, so reverting a keying change passes without a waiver per literal. A new file removes no such call and can never be restored.",
    "check-i18n:added-strings": "node scripts/i18n/check-added-strings.mjs",
    "//check-i18n:coverage": "The manifest-backed coverage gate. CI runs it with `--allowance-base \"$(git rev-parse HEAD^1)\"` so the shrink-only allowance is compared against the pull request's base; locally it resolves `origin/main` on its own.",
    "check-i18n:coverage": "node scripts/i18n/check-coverage.mjs",
    "//check-i18n:clean-view": "The three gates above run against the WORKING TREE, which is the right answer for a developer and the wrong answer for a commit: twice in one day a gate was green because the local checkout was dirty in the helpful direction (an untracked receipt path, an untracked test probe), and both times CI disagreed. This runs them against `git archive HEAD` instead, in a temp export, so the verdict is the one a clean checkout gives. It is NOT wired into `.github/workflows` yet - that is a follow-up - so it is a deliberate manual/opt-in gate rather than a required check.",
    "check-i18n:clean-view": "node scripts/i18n/check-clean-view.mjs",
    "gen-themes": "node scripts/generate-theme-css.mjs",
    "bundle-size": "node scripts/bundle-size.mjs",
    "startup-closure": "node scripts/startup-closure.mjs",
    "pack": "pnpm run build && electron-builder --dir",
    "dist": "pnpm run build && electron-builder",
    "dist:mac": "pnpm run build && electron-builder --mac --publish never",
    "dist:win": "pnpm run build && electron-builder --win --publish never",
    "dist:linux": "pnpm run build && electron-builder --linux --publish never",
    "dist:all": "pnpm run build && electron-builder -mwl --publish never",
    "release": "pnpm run build && electron-builder --publish always",
    "generate-icons": "node scripts/generate-icons.js",
    "notarize-dmg": "node scripts/notarize-artifacts.mjs",
    "verify-macos-artifacts": "node scripts/verify-macos-artifacts.mjs",
    "setup-python": "./scripts/setup-python-resource.sh",
    "setup-python:win": "powershell -NoProfile -ExecutionPolicy Bypass -File scripts/setup-python-resource.ps1",
    "storybook": "storybook dev -p 6006",
    "build-storybook": "storybook build",
    "app:driver": "node scripts/renderer-driver.mjs",
    "app:driver:gate-check": "node scripts/renderer-driver.mjs --gate-check"
  },
  "dependencies": {
    "@electron-toolkit/utils": "^4.0.0",
    "@xterm/headless": "6.0.0",
    "dotenv": "^16.5.0",
    "electron-log": "^4.4.8",
    "electron-updater": "^6.8.9",
    "node-pty": "1.1.0",
    "posthog-node": "^4.11.3",
    "zod": "^3.24.2"
  },
  "//types-node-pin": "Declared in devDependencies and pinned exactly, rather than left to the peer that used to supply it. @electron-toolkit/tsconfig peers on `@types/node: *`, so a full re-resolution floats it to whatever major is current; a range here would re-float the same way. It matters because the renderer typecheck compiles against the lib level this package implies: 22.x carries the es2020 compatibility shims that declare `Array.prototype.at`, 24.x dropped them, and floating it surfaced two TS2550 errors in files nothing here touches. Declaring it makes that a reviewed line instead of a resolution accident.",
  "//packaged-node-modules-exclusions": "The list above excludes Electron's own dependency tree from the packaged app, which electron-builder copies because `electron` is in optionalDependencies (the npm/npx channel needs it at install time). `@electron/get`, `@electron-internal/extract-zip` and their deps exist to download and unpack the Electron runtime during an INSTALL; a packaged app never runs them. Measured on a --dir artifact of 0.19.7: 8 packages outside the production closure, 7.0 MB of them unpacked into app.asar.unpacked and the rest inside a 26 MB app.asar (@types/node alone 2.4 MB). None is a module request anywhere in out/**, and the closure scripts/check-packaged-closure.mjs computes over the six declared runtime dependencies contains none of them. They are named rather than pattern-matched because electron-builder has no 'skip this dependency's tree' switch: a future Electron bump that adds a dependency needs this list re-derived from the same diff.",
  "//electron-pin": "Two pins, one runtime, and they must move together. optionalDependencies.electron is what the npm/npx channel installs and what bin/local-operator-ui.js checks at launch; build.electronVersion is what electron-builder packages into the installers. electron-builder does NOT read optionalDependencies (findFromPackageMetadata inspects devDependencies then dependencies only), so without the explicit build.electronVersion it silently falls back to whatever electron happens to sit in node_modules, and a bump against a stale tree keeps building the old runtime. Bump both, or scripts/test-publish-workflow.mjs fails. dmg-builder and electron-builder-squirrel-windows are app-builder-lib's peers and the builder refuses to resolve when they disagree with it, so all three move as one version.",
  "optionalDependencies": {
    "electron": "45.1.0"
  },
  "devDependencies": {
    "@babel/helpers": "^7.26.10",
    "@babel/runtime": "^7.26.10",
    "@biomejs/biome": "^1.9.4",
    "@chromatic-com/storybook": "^3.2.5",
    "@codemirror/language": "^6.11.1",
    "@codemirror/search": "^6.5.6",
    "@codemirror/state": "^6.5.2",
    "@codemirror/view": "^6.37.1",
    "@electron-toolkit/preload": "^3.0.1",
    "@electron-toolkit/tsconfig": "^1.0.1",
    "@electron/notarize": "^2.5.0",
    "@emotion/react": "^11.14.0",
    "@emotion/styled": "^11.14.0",
    "@formatjs/icu-messageformat-parser": "^3.5.21",
    "@lezer/highlight": "^1.2.1",
    "@mui/material": "^6.4.2",
    "@mui/x-date-pickers": "^8.3.1",
    "@storybook/addon-essentials": "^8.6.4",
    "@storybook/addon-interactions": "^8.6.4",
    "@storybook/blocks": "^8.6.4",
    "@storybook/react": "^8.6.4",
    "@storybook/react-vite": "^8.6.4",
    "@storybook/test": "^8.6.4",
    "@tailwindcss/vite": "4.3.3",
    "@tanstack/react-query": "^5.67.1",
    "@tanstack/react-query-devtools": "^5.67.1",
    "@types/hast": "^3.0.4",
    "@types/node": "22.14.1",
    "@types/react": "18.3.18",
    "@types/react-dom": "18.3.5",
    "@types/react-syntax-highlighter": "^15.5.13",
    "@types/xlsx": "^0.0.36",
    "@uiw/codemirror-extensions-langs": "^4.23.10",
    "@uiw/react-codemirror": "^4.23.10",
    "@vitejs/plugin-react": "^4.3.4",
    "@xterm/addon-unicode11": "0.9.0",
    "@xterm/xterm": "6.0.0",
    "ag-grid-community": "^33.3.2",
    "ag-grid-react": "^33.3.2",
    "class-variance-authority": "0.7.1",
    "clsx": "2.1.1",
    "date-fns": "^4.1.0",
    "dmg-builder": "26.16.1",
    "dotenv-cli": "^8.0.0",
    "electron-builder": "^26.16.1",
    "electron-builder-squirrel-windows": "26.16.1",
    "electron-vite": "^3.0.0",
    "esbuild": "^0.25.1",
    "html-react-parser": "^5.2.2",
    "icns-lib": "^1.0.1",
    "intl-messageformat": "^12.1.3",
    "jest": "^29.7.0",
    "jsdom": "26.1.0",
    "katex": "^0.16.21",
    "lucide-react": "^0.507.0",
    "mdast-util-math": "^3.0.0",
    "mermaid": "^11.6.0",
    "micromark-extension-math": "^3.1.0",
    "posthog-js": "^1.235.0",
    "radix-ui": "1.6.7",
    "pptx-browser": "4.1.5",
    "react": "^18.3.1",
    "react-dom": "^18.3.1",
    "react-error-boundary": "^5.0.0",
    "react-markdown": "^10.1.0",
    "react-router-dom": "^6.16.0",
    "react-shepherd": "^6.1.8",
    "react-syntax-highlighter": "^15.6.1",
    "recharts": "^2.15.3",
    "rehype-katex": "^7.0.1",
    "rehype-parse": "^9.0.1",
    "rehype-remark": "^10.0.1",
    "rehype-source-map": "^1.0.1",
    "rehype-stringify": "^10.0.1",
    "remark": "^15.0.1",
    "remark-gfm": "^4.0.1",
    "remark-math": "^6.0.0",
    "remark-parse": "^11.0.0",
    "remark-rehype": "^11.1.2",
    "remark-stringify": "^11.0.0",
    "sharp": "^0.33.2",
    "shepherd.js": "^14.5.0",
    "sonner": "^2.0.3",
    "storybook": "^8.6.4",
    "tailwind-merge": "3.6.0",
    "tailwindcss": "4.3.3",
    "tw-animate-css": "1.4.0",
    "typescript": "^7.0.2",
    "unified": "^11.0.5",
    "unist-util-visit": "^5.0.0",
    "uuid": "^11.1.0",
    "vite": "^6.2.0",
    "vite-tsconfig-paths": "^5.1.4",
    "xlsx": "^0.18.5",
    "yaml": "^2.7.0",
    "zustand": "^5.0.3"
  },
  "peerDependencies": {
    "react": ">=18.0.0",
    "react-dom": ">=18.0.0"
  },
  "engines": {
    "node": ">=22.13.1"
  },
  "pnpm": {
    "overrides": {
      "jsdom>nwsapi": "2.2.28"
    }
  },
  "build": {
    "appId": "com.local-operator",
    "electronVersion": "45.1.0",
    "productName": "Local Operator",
    "copyright": "Copyright © 2025 Radient Inc.",
    "asar": {
      "smartUnpack": false
    },
    "asarUnpack": [
      "node_modules/node-pty/prebuilds/**/*",
      "node_modules/node-pty/build/Release/**/*"
    ],
    "files": [
      "out/**/*",
      "bin/**/*",
      "LICENSE",
      "README.md",
      "THIRD_PARTY_NOTICES.md",
      "!node_modules/electron/**/*",
      "!node_modules/@electron/get/**/*",
      "!node_modules/@electron-internal/**/*",
      "!node_modules/env-paths/**/*",
      "!node_modules/progress/**/*",
      "!node_modules/sumchecker/**/*",
      "!node_modules/undici/**/*",
      "!node_modules/undici-types/**/*",
      "!node_modules/@types/node/**/*"
    ],
    "directories": {
      "output": "dist",
      "buildResources": "build"
    },
    "afterSign": "scripts/notarize.js",
    "afterPack": "scripts/after-pack.mjs",
    "mac": {
      "icon": "build/icon.icns",
      "extraResources": [
        {
          "from": "resources/python",
          "to": "python-runtime-seed/x64",
          "filter": [
            "**/*"
          ]
        },
        {
          "from": "resources/python_aarch64",
          "to": "python-runtime-seed/arm64",
          "filter": [
            "**/*"
          ]
        },
        {
          "from": "resources/uv",
          "to": "uv/x64",
          "filter": [
            "**/*"
          ]
        },
        {
          "from": "resources/uv_aarch64",
          "to": "uv/arm64",
          "filter": [
            "**/*"
          ]
        }
      ],
      "notarize": false,
      "category": "public.app-category.developer-tools",
      "hardenedRuntime": true,
      "gatekeeperAssess": false,
      "entitlements": "build/entitlements.mac.plist",
      "entitlementsInherit": "build/entitlements.mac.plist",
      "target": [
        {
          "target": "dmg"
        },
        {
          "target": "zip"
        }
      ],
      "artifactName": "${name}-${version}-${arch}.${ext}"
    },
    "dmg": {
      "sign": true,
      "contents": [
        {
          "x": 130,
          "y": 220
        },
        {
          "x": 410,
          "y": 220,
          "type": "link",
          "path": "/Applications"
        }
      ],
      "window": {
        "width": 540,
        "height": 380
      }
    },
    "win": {
      "extraResources": [
        {
          "from": "resources/python",
          "to": "python",
          "filter": [
            "**/*"
          ]
        },
        {
          "from": "resources/python_aarch64",
          "to": "python_aarch64",
          "filter": [
            "**/*"
          ]
        },
        {
          "from": "resources/uv",
          "to": "uv/x64",
          "filter": [
            "**/*"
          ]
        },
        {
          "from": "resources/uv_aarch64",
          "to": "uv/arm64",
          "filter": [
            "**/*"
          ]
        }
      ],
      "target": [
        {
          "target": "nsis",
          "arch": [
            "x64",
            "arm64"
          ]
        }
      ],
      "artifactName": "${name}-setup-${version}-${arch}.${ext}",
      "verifyUpdateCodeSignature": false
    },
    "nsis": {
      "createDesktopShortcut": true,
      "createStartMenuShortcut": true,
      "deleteAppDataOnUninstall": true,
      "displayLanguageSelector": true,
      "multiLanguageInstaller": true
    },
    "linux": {
      "extraResources": [
        {
          "from": "resources/python",
          "to": "python",
          "filter": [
            "**/*"
          ]
        },
        {
          "from": "resources/python_aarch64",
          "to": "python_aarch64",
          "filter": [
            "**/*"
          ]
        },
        {
          "from": "resources/uv",
          "to": "uv/x64",
          "filter": [
            "**/*"
          ]
        },
        {
          "from": "resources/uv_aarch64",
          "to": "uv/arm64",
          "filter": [
            "**/*"
          ]
        }
      ],
      "category": "ArtificialIntelligence",
      "icon": "build/",
      "target": [
        {
          "target": "deb",
          "arch": "x64"
        },
        {
          "target": "AppImage",
          "arch": "x64"
        },
        {
          "target": "rpm",
          "arch": "x64"
        }
      ],
      "artifactName": "${name}-${version}-${arch}.${ext}",
      "desktop": {
        "entry": {
          "Name": "Local Operator",
          "Comment": "AI Agent Assistants On Your Device",
          "Categories": "ArtificialIntelligence"
        }
      }
    },
    "deb": {
      "depends": [
        "python3.12-full",
        "python3.12-venv"
      ]
    },
    "rpm": {
      "depends": [
        "python3.12-full",
        "python3.12-venv"
      ]
    },
    "publish": [
      {
        "provider": "github",
        "owner": "damianvtran",
        "repo": "local-operator-ui",
        "private": false,
        "releaseType": "release"
      }
    ],
    "generateUpdatesFilesForAllChannels": true
  }
}
