apunkt/rowboat
1
0
Fork 0
mirror of https://github.com/rowboatlabs/rowboat.git synced 2026-07-12 21:02:17 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions
rowboat/apps/x/pnpm-workspace.yaml

31 lines
419 B
YAML
Raw Normal View History

bootstrap new electron app
2025-12-29 15:30:57 +05:30
packages:
- apps/*
- packages/*
feat: add user-configurable notification settings (#601)
2026-06-11 19:43:26 +05:30
allowBuilds:
fix(x): resolve baileys build approval placeholder blocking package build The mobile-channels feature added baileys, whose install-time scripts require build approval. A placeholder value ("set this to true or false") was left in the allowBuilds block of pnpm-workspace.yaml. pnpm 11 treats an unresolved build decision as a hard error, causing pnpm install to exit non-zero and abort Electron Forge's generateAssets hook during npm run package. Set baileys: true to match the onlyBuiltDependencies entry.
2026-07-06 16:11:38 +05:30
baileys: true
Code mode: make packaged builds work via managed engine provisioning (#625) * fix(code-mode): make packaged code mode work via on-demand engine provisioning Packaged builds could never run code mode: the Claude/Codex ACP adapters are spawned as separate `node <entry>` processes resolved at runtime, but esbuild can't inline a dynamic spawn target and Forge strips the workspace node_modules, so every release threw `Cannot find module '@agentclientprotocol/...'`. Dev worked only because of the pnpm symlink. Rather than bundle the ~400 MB of native engines (one claude + one codex binary per OS), provision them on demand: - forge.config.cjs: stage the two ACP adapters + their JS dependency closure into .package/acp/node_modules (npm-style nested layout, native engines skipped), exempt .package from the node_modules ignore rule, and only sign/notarize when APPLE_ID is set so unsigned local/CI builds can package. - agents.ts: resolve the adapter from the staged location first (node_modules fallback in dev); provision the pinned engine and point the adapter at it via CLAUDE_CODE_EXECUTABLE / CODEX_PATH. No dependence on a user's global install. - engine-provisioner.ts: ensureEngine() downloads the per-platform engine package from npm AT THE EXACT VERSION THE ADAPTER WAS BUILT AGAINST, verifies its sha512 integrity, extracts atomically into ~/.rowboat/engines/<agent>/<version>/, and caches it. Version-pinning keeps the ACP handshake compatible. - engine-manifest.ts + scripts/gen-engine-manifest.mjs: committed manifest of tarball URLs + integrity for all platforms, regenerated from the adapters' pinned versions on a bump. Verified on macOS arm64: both engines provision and run, and both adapters complete the ACP initialize handshake from the packaged .app against the provisioned engines. Installer drops from ~790 MB to 390 MB. * feat(code-mode): explicit per-agent Enable in Settings; no silent chat download Code mode now requires the user to explicitly enable an agent before use, instead of silently downloading a ~200 MB engine on the first chat message. - Settings → Code Mode: each agent shows "Not enabled" + an Enable button that downloads its engine with a live progress indicator (download % → verify → install), then flips to "Engine ready". Driven by a new codeMode:provisionEngine IPC call + a codeMode:engineProgress push channel. The section now states the prerequisite explicitly: the agent must be installed (Enable) and logged in (claude login / codex login — code mode reuses that saved credential). - Chat path no longer auto-downloads: getProvisionedEnginePath() returns the enabled engine or throws a clear "enable it in Settings → Code Mode" error, so there's never a surprise mid-conversation download. getAgentLaunchSpec is sync again. - Agent status: `installed` now means "engine provisioned" (downloaded), driving the Enable/Ready state; the new-session dialog shows "Enable in Settings" and disables un-enabled agents. Dropped the dead PATH-probing for a global CLI. Verified: empty cache -> status installed=false and the chat path throws the enable-in-Settings error (no download); core, renderer, and main typecheck/build; no new lint errors. * fix(code-mode): show only percentage during engine download in Settings * feat(code-mode): prune superseded engine versions after install After a successful provision, remove any other version dirs (and their .meta) for that agent so old ~200 MB engines don't accumulate across version bumps. Best-effort; never fails a good install. Verified: a planted stale version dir + meta are both removed after provisioning the current version. * fix(code-mode): keep showing engine download % after reopening Settings Provisioning state lived in the row component, which unmounts when the Settings dialog closes — so reopening mid-download showed the Enable button again even though the download was still running in the main process. Move provisioning state to a module-level store with one persistent listener on codeMode:engineProgress, so a row remounting (dialog reopened) reflects the live % and resolves to Ready on completion. * fix(code-mode): flip Enable row straight to Ready after install (no Enable flash) On successful provision the in-flight flag was cleared before the async status refresh completed, so the row briefly (or until reopen) showed the Enable button again. Await the status refresh before clearing the flag so it transitions directly to Ready. * fix(code-mode): optimistically show Ready right after Enable completes Awaiting the status refresh wasn't enough — setStatus re-renders the parent separately from the row, leaving a window where the in-flight flag was cleared but the status prop was stale, so the row flashed/stuck on the Enable button until reopen. Track just-enabled agents in a module-level set and treat them as installed immediately; loadStatus still syncs the real status in the background. * fix(code-mode): graft login-shell PATH + add startup deadline #1 (the gh/git "command not found" in packaged builds): GUI/Finder launches inherit launchd's stripped PATH (/usr/bin:/bin:...), so tools the engine spawns — gh, git, rg, bash — fail even though they work from a terminal (e.g. Homebrew's /opt/homebrew/bin/gh). Probe the user's login-shell PATH and graft it onto the engine's env before spawn (shell-env.ts; no-op on Windows / probe failure). #2: add a 60s startup deadline (initialize / session create+load) so a wedged engine fails with a clear, stderr-enriched error instead of an infinite "(pending...)". Overridable via ROWBOAT_ACP_STARTUP_TIMEOUT_MS. Manager now disposes the client on startup failure so the spawned adapter doesn't leak. Verified: getAgentLaunchSpec's env.PATH now includes /opt/homebrew/bin (where gh lives); core builds; no new lint errors. * chore(code-mode): comment out signing/notarization for local builds Revert to the explicit comment-out approach for osxSign/osxNotarize: uncomment them (with APPLE_ID/APPLE_PASSWORD/APPLE_TEAM_ID) for a signed release build. * chore(code-mode): keep signing/notarization active in committed config The repo's forge.config ships with osxSign/osxNotarize enabled (release-ready). Developers comment them out locally for unsigned test builds and don't commit that. * chore: approve workspace build scripts so packaging runs non-interactively The allowBuilds entries were left as "set this to true or false" placeholders, so `pnpm install` / the pre-build deps check aborted with ERR_PNPM_IGNORED_BUILDS and `npm run package` failed. Set them to true (and add node-pty, used by the code-mode embedded terminal) so build scripts are approved and packaging works without a manual `pnpm approve-builds`.
2026-06-17 09:23:15 -07:00
core-js: true
electron: true
electron-winstaller: true
esbuild: true
fs-xattr: true
macos-alias: true
node-pty: true
protobufjs: true
feat: add user-configurable notification settings (#601)
2026-06-11 19:43:26 +05:30
fix(x): unblock codex code-mode (bad cwd + revoked engine cert) code_agent_run failed with a misleading "spawn <Electron> ENOENT" that read as "Codex isn't installed". Two stacked causes: 1. cwd wasn't expanded/validated: a `~` or non-existent path was passed straight to child_process.spawn, which reports ENOENT against the command (Electron) rather than the missing directory. Now expandHome + resolve + existence-check with a clear error. 2. Apple revoked the signing cert on the pinned @openai/codex@0.128.0, so macOS Gatekeeper trashed the binary on launch and the ACP adapter died mid-handshake. Bump the ACP stack off the revoked build: codex-acp 0.0.44 -> 1.1.0, claude-agent-acp 0.39 -> 0.55, sdk 0.22 -> 1.1, regen engine-manifest (codex 0.142.5 / claude 0.3.198). Removed the two now-obsolete patches (contextCompaction upstreamed; the codex windowsHide patch targeted bin/codex.js, which we bypass via CODEX_PATH). Bump fallout handled: - client.ts setModel: sdk 1.x dropped unstable_setSessionModel; model is now a config option -> setSessionConfigOption({configId:'model'}). - engine-provisioner: codex 0.142 moved its binary (codex/ -> bin/) and rg (path/ -> codex-path/); probe both layouts. - pnpm override vscode-jsonrpc to 8.2.0: codex-acp 1.1 pulls jsonrpc 9.x whose restrictive exports break langium's deep import in the renderer (blank screen). codex-acp is the only 9.x consumer and works on 8.x (handshake verified), so pin the workspace to 8.x. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-07-06 12:57:02 +05:30
overrides:
vscode-jsonrpc: 8.2.0
Refactor builtin file tools beyond workspace scope Replace workspace-scoped builtin file tools with general-purpose file-* tools that accept relative, absolute, and ~/ paths. Relative paths still resolve against the configured workdir. File operations within the workdir are auto-approved. File operations outside the workdir now emit file permission metadata and require user approval, with support for once, session, and persistent grants. Add a shared filesystem layer for text-focused read/write/edit/list/search operations, including binary-file safeguards for text reads. parseFile and LLMParse continue to read file buffers for document/image parsing. Update copilot prompts, background/live-note agents, knowledge workflows, and renderer labels/UI to use the new file-* tool surface and permission details. Add package-local Vitest setup for @x/core with colocated filesystem unit tests covering path resolution, canonical permission paths, binary detection, read/write/edit behavior, glob, and grep.
2026-05-25 16:21:40 +05:30
catalog:
vitest: 4.1.7
bootstrap new electron app
2025-12-29 15:30:57 +05:30
onlyBuiltDependencies:
approve baileys build
2026-07-06 10:56:34 +05:30
- baileys
fix pnpm postinstall
2026-01-21 10:47:44 +05:30
- core-js
bootstrap new electron app
2025-12-29 15:30:57 +05:30
- electron
integrate electron forge
2026-01-17 10:27:30 +05:30
- electron-winstaller
bootstrap new electron app
2025-12-29 15:30:57 +05:30
- esbuild
integrate electron forge
2026-01-17 10:27:30 +05:30
- fs-xattr
fix pnpm postinstall
2026-01-21 10:47:44 +05:30
- macos-alias
- protobufjs
Reference in a new issue Copy permalink