New session with OmO or Gajae Code cannot start on a Windows PC #234

What happens

New session with OmO or Gajae Code on a Windows PC cannot work. These agents are started by typing a command into the new pane's shell (server/shell-agent.ts), and that code assumes a POSIX shell and POSIX paths:

• The command is typed as '<absolute path>' '<arg>' with POSIX single-quote escaping. In PowerShell a quoted string alone is an expression, not a call (it needs & '<path>'), and cmd does not treat single quotes as quotes at all.
• The start counts as done once the agent is the pane's foreground process, judged by isOmoProcess / isGjcProcess. Both match /-separated paths and names without .exe / .cmd, so a Windows process is never recognized and the start times out after 60 s.
• /api/agents offers the agent when Bun.which finds it, which on Windows resolves the npm .cmd shims, so the dialog does offer what then cannot start.

The same matchers decide the OmO mark in the sidebar (labelOmoPanes) and the chat lens's transcript lookup, so an OmO or gjc pane started by hand on Windows is likely not recognized either.

Status

Found by reading the code after Windows PCs became connectable (#227). Not reproduced: it needs OmO or gjc installed on a Windows PC, and a fix needs the same to be verified, including which shell the pane runs (PowerShell or cmd).

Ideas

• Pick the quoting from the pane's foreground shell (pane.process_info): & '...' for PowerShell, "..." for cmd.
• Make the process matchers accept \\ separators and .exe / .cmd / .ps1 names.
• Until then, do not offer shell-started agents on a Windows bridge.