jcode connect fails with "Broken pipe (os error 32)" on Ubuntu while jcode run works

Describe the bug

On Ubuntu Linux, jcode connect successfully connects to the running J-Code server, but as soon as I send a normal message, it fails with:

Error: Broken pipe (os error 32)

The server still appears to be alive, and jcode run works for the same kind of prompt.

To Reproduce

1. Start the server:

   jcode serve
   

2. In another terminal, run:

   jcode connect
   

3. Type any normal message, for example:

   quiero que veas el estado actual del proyecto y me muestres el mapa
   

4. Press Enter.
5. The client exits with:

   Error: Broken pipe (os error 32)
   

Expected behavior

jcode connect should keep the interactive session alive and process the message normally.

Actual behavior

jcode connect accepts the connection, but breaks immediately after sending the first prompt.

Works as expected

This works:

jcode run "quiero que veas el estado actual del proyecto y me muestres el mapa"

Environment

• OS: Ubuntu Linux
• jcode version: jcode v0.44.0 (ee9476ae)
• Shell: bash
• Project directory: ~/proyectos/will-cel

Additional context

I had previously cleaned an older modified local build and reinstalled jcode 0.44.0 successfully. After reinstall, jcode run works, but jcode connect consistently fails with the broken pipe error.

Reproduce the failure with jcode serve and jcode connect on Ubuntu, then compare it with the working jcode run command. Trace the first prompt sent by the interactive client and identify why the session closes with Broken pipe (os error 32). Done means jcode connect processes a normal message and keeps the interactive session alive.