System Information
ralph-tui: 0.6.0
runtime: bun 1.3.6
os: win32 10.0.26200 (x64)
agent: gemini (unavailable)
tracker: json
global-config: yes
project-config: yes
templates: none
bundled-skills: 4
skills-installed: claude:0, opencode:0, droid:0, gemini:0, codex:0, kiro:0
Steps to reproduce
Hi,
I'm having an issue where ralph-tui fails to initialize the gemini agent on Windows. It times out waiting for gemini
--version.
Steps to Reproduce:
- Install gemini-cli via npm.
- Install ralph-tui via bun.
- Configure ralph-tui to use agent = "gemini".
- Run ralph-tui.
Error Message:
1 Initializing Ralph TUI...
2 ...
3 Failed to initialize engine: Agent 'gemini' not available: Timeout waiting for --version
System Information:
- OS: Windows
- ralph-tui installed via bun
- gemini-cli installed via npm
Diagnostics:
- gemini --version runs successfully from the command line and outputs 0.26.0.
- The gemini command is located at C:\Users\bacso\AppData\Roaming\npm\gemini.cmd.
- The ralph-tui command is located at C:\Users\bacso.bun\bin\ralph-tui.exe.
- The problem persists even when running with administrator privileges or setting a temporary HOME directory.
It seems to be an issue with how the bun-based ralph-tui executable spawns the npm-based gemini.cmd script on
Windows.
Relevant logs / terminal output
No iteration logs found.
Logs are saved to: C:\Users\bacso\.ralph-tui\iterations
Run ralph-tui to generate logs.
Configuration (if relevant)
Additional context
No response
System Information
Steps to reproduce
Hi,
I'm having an issue where ralph-tui fails to initialize the gemini agent on Windows. It times out waiting for gemini
--version.
Steps to Reproduce:
Error Message:
1 Initializing Ralph TUI...
2 ...
3 Failed to initialize engine: Agent 'gemini' not available: Timeout waiting for --version
System Information:
Diagnostics:
It seems to be an issue with how the bun-based ralph-tui executable spawns the npm-based gemini.cmd script on
Windows.
Relevant logs / terminal output
Configuration (if relevant)
Additional context
No response