Make SSH connections compatible with Codex Desktop's remote connections

[niklassheth]

Since Codex Desktop's remote connection uses a unix socket app-server while Litter's SSH uses a websocket one, they run separate app servers. This means that new messages and the "turn active" state desyncs between clients, if you're using both litter and Codex Desktop to connect to the same server.
My fork makes litter work just like Codex Desktop, using a shared codex app-server --listen unix:// and a codex app-server proxy instance per SSH connection. Now progress in a thread syncs correctly between the desktop app and litter. I find it useful to start a long running task on my laptop and steer it from my phone, or start one remotely and then work on it from the desktop app when I get home.
I looked into it, and it seems better to use the codex app-server --listen unix:// + codex app-server proxy method for SSH anyways, as it simplifies the codebase.

[dnakov]

Closing as fixed on current main. SSH-backed Codex connections now probe the remote Codex Desktop IPC socket ($TMPDIR/codex-ipc/ipc-<uid>.sock), attach over SSH direct-streamlocal when available, mark IPC as primary, and route thread/list/read/start/updates through the shared IPC path so Desktop and Litter observe the same remote app-server state. Reopen if the current main/TestFlight build still desyncs with Codex Desktop remote connections.

[dnakov]

for codex:
no. this isnt the IPC, theres a new thing in app-server to use a unix socket we should look into switching to that. review upstream to see how its implemented. also see what needs to change in alleycat