Gagancreates fffa34bf4e fix(code-mode): ship ACP adapters in packaged builds ... Code mode spawns the Claude/Codex ACP adapters as separate `node <entry>` processes resolved at runtime, so each must exist as a real file on disk. esbuild can't inline them (dynamic require.resolve + spawn target), and Forge's `ignore: /node_modules/` rule strips the workspace node_modules — so packaged builds threw `Cannot find module '@agentclientprotocol/claude-agent-acp'` and code mode was broken in every release. Dev worked only because the pnpm symlink was present. Stage the two adapters and their full production dependency closure into .package/acp/node_modules during generateAssets, reconstructing an npm-style nested layout: nest on version conflict (claude and codex keep their own @agentclientprotocol/sdk; the @openai/codex launcher keeps its platform binary) and skip platform-optional deps not installed for the build OS, so each OS ships its own native binary. Exempt .package from the node_modules ignore rule, and make the adapter resolver check the staged location first, falling back to node_modules in dev. Resolve dependency directories by walking node_modules directly rather than require.resolve(`${pkg}/package.json`): the latter throws for packages whose `exports` map doesn't expose package.json (e.g. @anthropic-ai/claude-agent-sdk), which would silently drop them and their subtrees from the staged closure.		2026-06-10 01:16:29 +05:30
..
core	fix(code-mode): ship ACP adapters in packaged builds	2026-06-10 01:16:29 +05:30
shared	feat: run code mode on an in-app ACP client with live approvals (#593)	2026-06-05 14:45:08 +05:30