fix: Windows terminal input not working

[toyuvalo]

Problem

On Windows, the ClawSCAD terminal renders correctly but typing has no effect. Works fine on Linux.

Root causes

1. Missing term.focus() in renderer.js (primary cause)

Electron on Windows does not automatically give keyboard focus to an xterm.js terminal element after term.open(). As a result, term.onData() never fires for keystrokes — every character typed is silently dropped. On Linux, focus is granted automatically.

Fix: Call term.focus() immediately after fitAddon.fit(), and add a click event listener that re-focuses the terminal when clicked.

2. Shell fallback defaults to /bin/bash on Windows (main.js)

process.env.SHELL is not set on Windows, so the fallback process.env.SHELL || '/bin/bash' tries to spawn /bin/bash — which doesn't exist. This means if Claude exits and the terminal attempts to restart, ptyProcess ends up broken and all further input is silently dropped.

Fix: Add a DEFAULT_SHELL constant that resolves to process.env.COMSPEC || 'cmd.exe' on Windows, and use it everywhere in place of the old fallback.

3. ConPTY input reliability on Windows (main.js)

node-pty defaults to the ConPTY backend on Windows, which can silently fail to forward input for some CLI applications. The legacy winpty backend is more reliable.

Fix: Pass useConpty: false in pty.spawn() options when running on Windows.

Changes

• renderer.js: term.focus() + click-to-focus for both terminal instances
• main.js: DEFAULT_SHELL constant, useConpty: false on win32, consistent restart logic in startTerminal and restartTerminal

🤖 Generated with Claude Code