gemini-cli - 💡(How to fix) Fix Bug : Session exit after shell action execution over SSH/Remote Terminal [1 participants]

Description

When running the Gemini CLI on a Raspberry Pi Zero 2 W, the session intermittently exits after a shell action is authorized. While the command executes successfully, the CLI often fails to return to the interactive prompt, instead dropping the user back to the system shell. This behavior is inconsistent—it occasionally works as expected, but fails frequently.

Environment

• Device: Raspberry Pi Zero 2 W (512MB RAM)
• OS: Raspberry Pi OS Lite (64-bit)
• Node Version: v24.14.1
• Connection Method: SSH (Windows CMD/PowerShell), Raspberry Pi Connect (Web-based)

Steps to Reproduce

1. Connect to the Pi via SSH.
2. Launch the CLI: gemini
3. Trigger a shell tool (e.g., pip list or ls /dev/spi*).
4. Select "1. Allow once" from the interactive menu.
5. Observed Behavior: The command output prints to the terminal.
6. The Intermittent Bug: - Fail Case: The Gemini process terminates immediately after the command output, returning to user@raspberrypi:~$.
   • Success Case: The Gemini prompt ? reappears, allowing further interaction.

Additional Context

• Hardware Constraints: The issue is occurring on a Pi Zero 2 W. Given the limited 512MB RAM, this may be a resource exhaustion issue or a timing race condition during the TTY handoff between the child process and the ink UI.
• PTY Status: enableInteractiveShell is enabled.
• Inconsistency: There is no clear pattern to the failures, though it seems more prone to exiting when the command output is lengthy or the system is under higher load.

Hypothesis

There appears to be a race condition in the stdin/stdout handoff. On low-resource hardware like the Pi Zero 2, the parent Node.js process may be losing terminal focus or receiving an end-of-file (EOF) signal before the UI has a chance to re-initialize after the shell execution finishes.