[AJV009]

Problem

On Linux the Terminal tab mounts but never connects. The plugin backend exits immediately with:

Error: [web-terminal] Cannot find module 'node-pty' - run npm install in .../dist
Failed to start plugin server for web-terminal

The message is misleading — node-pty is installed. The loader's generic re-throw masks the real error:

Failed to load native module: pty.node, checked: build/Release, build/Debug,
prebuilds/linux-x64: Cannot find module './prebuilds/linux-x64//pty.node'

Cause

node-pty@1.1.0 ships prebuilds for darwin-arm64, darwin-x64, win32-arm64 and win32-x64 only — there is no linux-x64 prebuild, and no build/ output either, so there is nothing to load.

Only the 1.2.0-beta line ships Linux binaries. Since semver ranges exclude prereleases, ^1.1.0 can never resolve to it, so no amount of reinstalling fixes this on Linux.

Fix

Bump to ^1.2.0-beta.12 — the same range CloudCLI itself already uses, so this aligns the plugin with its host rather than introducing a new constraint.

Verification

Linux x64, Node 22.18.0, clean rm -rf node_modules && npm install:

• resolves node-pty@1.2.0-beta.15
• prebuilds/linux-x64/pty.node present
• require('node-pty') succeeds with no source build (also verified with --ignore-scripts)
• npm run build succeeds
• Terminal tab connects; plugin server starts and the WS proxy attaches

macOS and Windows are unaffected — the beta line ships their prebuilds too.

🤖 Generated with Claude Code

https://claude.ai/code/session_011WfoF1z5anUFtH61ECn1ZF

[brianKing88]

Independent evidence for this bump, from a different angle than Linux prebuilds: 1.1.0 leaks a PTY master fd on every session teardown, and no amount of fixing the teardown code makes that go away.

I ran into it as a machine-wide outage rather than a plugin bug — after ~2.5 days of use the plugin server held 508 /dev/ptmx handles with zero live children, which exhausts kern.tty.ptmx_max (511 on macOS) and leaves nothing on the host able to open a terminal. Ghostty, Terminal.app and Cursor were all failing to allocate a PTY.

20 sessions whose shell traps SIGHUP, torn down the way killSession() does it, fds stranded per session:

node-pty	kill()	destroy()
1.1.0	3	2
1.2.0-beta.18	1	0

So there are two independent bugs stacked here. #23 fixes the teardown side (kill() only signals; destroy() is what releases the fd), but on the currently pinned 1.1.0 that alone only gets 3 → 2. Zero requires this PR as well — the 1.2.0-beta line fixed something in node-pty's own close path that 1.1.0 gets wrong.

Repro is in #23 if anyone wants to check it independently.

Worth noting the two ranges are not equivalent for this: I measured on 1.2.0-beta.18, and ^1.2.0-beta.12 as proposed here will resolve to the newest beta anyway, so that is fine — just flagging that the leak numbers above are from .18 specifically, not from .12.