mirror of
https://github.com/NeuralNomadsAI/CodeNomad.git
synced 2026-11-17 05:49:28 +00:00
5 commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
296af865a0
|
feat(tauri): embed native WebKit previews on macOS and Linux (#1301)
## Scope Native browser previews, agent browser automation parity, and preview capabilities across **Electron, Tauri Windows, Tauri macOS and Tauri Linux**. - Shared native embedding, geometry, overlay masking, session-owned history and profile-scoped preview storage, isolated from the trusted application renderer. - Public `codenomad.browser`: open, navigate, snapshot, click, type, select, press, scroll, hover, drag, wait and screenshot through the authenticated backend and fenced native-parent channel. - Six native viewport presets, WebKit HTTP/JavaScript mobile identity, reset/reload and per-registration isolation. Native WebKit density/input differences remain explicit. - OAuth pop-ups with opener/postMessage and shared preview storage; downloads with sanitized unique names; native dialogs and owner/opener/renderer lifetime cleanup. - Camera, microphone, location and notifications remain denied. Other classified permissions retain native consent/selection and fail-closed attribution. Guests receive no application privileges, app IPC, page Node access or general evaluation bridge. - Current-state developer documentation and user help in ten languages. **Tauri macOS requires macOS 14 or newer; Electron keeps its own platform baseline.** ## Host matrix | Host | Native preview/history | Agent automation | Mobile profiles | Pop-ups/downloads/dialogs | | --- | --- | --- | --- | --- | | Electron | Chromium | Supported | Chromium | Supported | | Tauri Windows | WebView2 | Supported | Chromium | Supported | | Tauri macOS 14+ | WKWebView | Supported | Native WebKit | Supported | | Tauri Linux | WebKitGTK | Supported | Native WebKit | Supported | ## Qualification - **Ubuntu 24.04 KDE VM:** real application built from the merged sources, real backend and parent channel, private OpenCode daemon and deterministic provider producing actual agent tool calls. Full browser action sequence, OAuth opener messaging, downloaded-file contents, native dialog acceptance and PNG passed under X11/Xwayland. Additional native Wayland qualification uses an owned private KWin compositor; native dialog operator coverage is recorded separately. - **macOS 15.8 Intel VM:** same real-application/agent-tool path, all actions and capability smoke passed with the built UI, private profile/configuration and private OpenCode daemon. The app-window nested-scroll check also qualifies the Cocoa wheel-coordinate correction. - **Windows:** Tauri release executable under its own profile/configuration; all actions, OAuth, completed download, native dialog and PNG passed through actual agent tool calls. The user's main CodeNomad and shared OpenCode service remain untouched. - Native CI qualifies Linux, macOS Intel, macOS ARM64 and Windows. Authorized draft qualification uses no signing secrets. - A **real Mac trial remains a release qualification step**. Graphical macOS ARM64 and physical hardware capabilities retain their own qualification scope; the capability matrix describes supported contracts rather than exhaustive peripheral testing. ## Documented limits - macOS first standalone hover can omit `pointerenter`; ⌘A selects through the native responder while consuming the main A keydown. - WebKit captures script-created closed shadow roots; declarative closed shadow roots remain opaque. - WebKitGTK preserves CVE-2025-13947 dropped-file protection; use the page's native file input. No dropped URI text is converted into host file access. - GTK async clipboard reads lack requesting-frame attribution and are refused; native Ctrl+V and clipboard writing remain available. - WebKit keeps native screen/platform/pointer/hover/touch metadata. WKWebView uses DPR 2.75 when its runtime-checked native selector exists; GTK DPR follows monitor scale × fitted zoom. CSS dimensions remain stable across app zoom/DPI. No JavaScript getter shims. - Cross-origin frame contents retain the documented opaque automation boundary. Page input timeouts have unknown outcomes and are never replayed automatically. ## Integration - Merge ` |
||
|
|
b6bea60dd6
|
build(runtime): separate bundled npm pinning from Node maintenance (#1330)
## Mechanism first, no npm release change Introduce `.npm-version` at the npm release already supplied by the pinned Node archive. Both desktop hosts package that exact registry release. This PR does not adopt npm 12: after it merges, maintenance will be dispatched to test creation of an independent candidate PR. ## Implementation - Download the exact npm registry tarball and verify its canonical metadata, package/version, sha512 integrity, bundled dependencies and engines against each host's Node. Reuse the platform tar extractor; no handwritten archive parser. The registry supplies both metadata and archive, so this checks registry content consistency, not an independent publisher signature. - Preserve Tauri's Node binary and existing per-platform npm layout, and Electron's npm-only resources. Smoke and verification check the npm pin. - Scope lifecycle script permission to the exact `@opencode/cli` release for direct installs and native upgrade. No blanket script permission or user npmrc edits. - Daily maintenance audits the pinned npm and candidate and proposes `.npm-version` changes only when declared engines accept both runtimes. A major is explicitly unqualified and needs maintainer review; engines acceptance is not behavioral validation. No automatic merge or release. - Partial proposals remain visible errors naming the existing branch, with reconciliation instructions; no forced overwrite/deletion. A candidate-audit failure blocks only the npm proposal; pinned audit and metadata failures remain failures. - Documentation references pins rather than copied versions. GitHub token-created proposal validation requires approving the workflow runs, or closing/reopening with a maintainer account; no new credentials added. ## Validation - Unit/packaging/maintenance/Tauri script suites: 47 pass. Server update tests: 70 pass, 1 platform skip. Typecheck passes. - Windows Electron45 package and Tauri release binary build/smoke pass. - Real install, upgrade and legacy-replacement fixtures pass on both Windows layouts with current npm11 and a temporary, uncommitted npm12 candidate. - Ubuntu: both layouts prepare/verify; first-install fixture passes with both npm releases. - The candidate removes the two high audit entries, but their applicability to CodeNomad's prebuilt OpenCode installation is low; 32 moderate entries remain. The proposal requires release-note review and native-fixture qualification rather than equating a lower audit count with safety. macOS candidate behavior still needs CI qualification. No pin to npm12, application release, registry publishing or daemon restart is part of this PR. |
||
|
|
78a734cb6b
|
perf(electron): run the backend with Electron's Node (#1304)
## Summary
Electron already ships the Node runtime the backend needs. The Electron
package now launches the CodeNomad server through `process.execPath`
with `ELECTRON_RUN_AS_NODE=1` and keeps only npm (from the pinned
`.node-version` archive), dropping the redundant standalone `node.exe`
(~89 MiB on Windows). Tauri keeps its full bundled runtime unchanged.
## Changes
- **Launch**: `process-manager.ts` runs the backend with Electron's own
executable in run-as-Node mode; `managed-node.ts` is removed.
- **Resources**: `prepare-node-runtime.cjs` gains an npm-only layout
requested by `electron-app/scripts/prepare-resources.js`; Tauri keeps
the full Node + npm layout.
- **npm discovery**: `bundledNpm()` (`npm-runtime.ts`) finds npm in
Electron resources (Windows, Linux, macOS `.app/Contents/Resources`)
while preserving Node/Tauri layouts.
- **npm lifecycle scripts**: `@opencode/cli` runs `node
./postinstall.mjs`; installation (`shared-installation.ts`) and native
upgrades (`native-upgrade.ts`) get a private, scoped `node` command
pointing at the Electron executable, removed afterwards. The shared
OpenCode daemon never inherits `ELECTRON_RUN_AS_NODE`.
- **Checks/CI**: packaged-resource smoke, `verify-bundled-node`,
`build.js` and `build-and-upload.yml` separate the Electron (npm-only)
and Tauri contracts; `test-opencode-*-native.mjs` and the desktop setup
qualification can target the packaged Electron runtime without a system
Node on PATH.
- **Docs**: `dev-docs/RUNTIME_MAINTENANCE.md` (the Electron package
follows Electron's Node version), `dev-docs/OPENCODE_RUNTIME_SETUP.md`,
and `server.md` / `updates.md` help pages in all ten locales.
## Validation
- Electron 39.0.0 → Node 22.20.0; npm 11.19.0 (engines `^20.17.0 ||
>=22.9.0`).
- Packaged Windows ZIP and Linux (`linux-unpacked` + extracted DEB,
Ubuntu 24.04 VM): backend reaches ready, API answers 200, both backend
processes run as the app executable with `ELECTRON_RUN_AS_NODE=1`, no
Node in resources or on PATH, clean exit with no orphan and the
executable released.
- `test-opencode-install-native` (2.2.3), `test-opencode-upgrade-native`
(→ 2.2.5, isolated service PID kept) and
`test-opencode-legacy-replacement-native` (1.18.10 → 2.2.5) pass on
Windows and Linux with the packaged Electron runtime.
- Typechecks (server, Electron), resource tests 11/11, `opencode-update`
tests (Windows 66 pass / 1 POSIX skip; Linux 62 pass / 5 Windows skips),
help validation.
- The full Electron suite on Windows shows intermittent failures in
`process-stop.test.ts` and `native-service-start.test.ts` (PowerShell
capture timeout of 1.5 s); they reproduce identically on `dev`
(
|
||
|
|
7869e609b3
|
feat(opencode): enforce stable runtime support and add managed setup
Require stable OpenCode >=2.0.11 <3.0.0 from authenticated daemon metadata before functional clients and plugin provisioning. Keep bounded contract recognition, connection-generation fencing and native ownership checks while retiring old request, response and event conversions. Unify missing and outdated runtime recovery with Preferences. Install exact stable releases through bundled Node/npm into a verified versioned user prefix, preserve custom and WSL selections, and separate installation from explicit shared-service restart through the native-parent starter. Fence stale setup responses, retain pending folder opening and never replay prompts. Certify isolated 2.0.3-to-2.0.11 history migration with executable hashes, untouched seed storage, paginated messages, forks, compaction checkpoints, location moves and pending inbox data. Add minimum/latest cross-platform migration and installation gates, packaged npm closure checks, real Solid recovery regressions and supported-contract authority tests. Validated server/UI types, focused unit and reducer suites, browser captures, actual packaging-prepared Node 24.20.0 installation without system Node, and native location, automation and pruning fixtures. Document packaged-desktop, WSL, broader historical-state and remote-CI evidence as remaining release gates. |
||
|
|
61b9218412
|
chore(desktop): upgrade bundled Node to 24.20.0 LTS (#679)
## Summary - Upgrade the standalone Node executable bundled with **both Tauri and Electron** from **22.22.2 to 24.20.0 LTS (Krypton)**. - Add a single exact `.node-version` pin consumed by the runtime preparation script and all Node CI setup steps, replacing the previous Node 20/22 build/test split. Official archive SHA-256 verification and executable-only packaging are preserved. - Set **macOS 13.5 minimum** explicitly in both desktop bundle manifests and update the build documentation. This compatibility change was explicitly accepted by the requester. - Strengthen packaged-resource smoke checks: verify the bundled Node matches the pin, reject stale runtimes, and exercise ESM imports including the native OpenCode V2 client from the packaged server directory. - Add regression coverage for the shared runtime/CI pin and macOS minimum-version parity. ## Scope and compatibility This updates the Node process running the CodeNomad backend. It does **not** upgrade Electron 39 or its internal Node/Chromium, WebView2, the user's Node installation, or the independently managed OpenCode daemon. No application dependencies or lockfile versions are changed. Node 24's official macOS binaries require 13.5 rather than Node 22's 11.0. Windows x64/ARM64 and Linux glibc x64/ARM64 keep their existing Node platform floors. No additional platform or musl support is introduced. The Windows x64 Node executable increases from approximately **83.04 MiB to 89.06 MiB** uncompressed. Final installer/archive size changes have not been measured. This is a runtime maintenance update, not the deferred packaging-size optimization. ## Validation Performed in an isolated worktree on Windows with the official, checksum-verified **Node 24.20.0 / npm 11.19.0** distribution: - [x] Clean `npm ci`; lockfile unchanged. - [x] UI, Electron, and server TypeScript checks. - [x] Server suite: **391 passed, 2 platform-skipped, 0 failed**. - [x] Electron Node-level native-logic suite: **192 passed**. - [x] Packaging/runtime regression tests: **6 passed**. - [x] `npm run bundle:server --workspace @codenomad/tauri-app`: rebuild UI/server resources, stage production dependencies, download/check/extract Node 24, and run packaged startup/import/loading-asset checks. - [x] Negative smoke: the previous release's packaged Node 22.22.2 is rejected with a version mismatch. - [x] Desktop manifest schema checks (Tauri numeric-format annotations ignored by the standalone JSON schema validator). - [x] `git diff --check`. The preliminary compatibility study also loaded all 14 direct server dependencies and the packaged `msgpackr-extract` N-API binary under Node 24, with a successful serialization roundtrip. ## Remaining release gates / existing warnings - [ ] Cross-platform CI builds and tests on the final head. - [ ] Native GUI launch, restore, OpenCode streaming, shutdown, and restart verification for the rebuilt desktop applications. Resource smoke tests and Node-level Electron tests are **not** a complete native-release approval. `npm ci` still reports the existing 49 dependency advisories; this PR does not run an unrelated dependency upgrade. npm 11.19 also warns about existing install scripts awaiting `allowScripts` coverage. `actionlint` reports only the pre-existing constant-false condition in `build-and-upload.yml` (now line 816). The touched `build-and-upload.yml` remains approximately 913 lines; no unrelated workflow refactor is included. |