Older Codex CLI can cause T3 Code session startup to fail with Timed out waiting for initialize. #360
Description
T3 Code failed while starting a Codex session, showing the exact error: Timed out waiting for initialization. In the UI, this appeared as repeated generic Runtime error entries instead of a clear startup failure.
The underlying issue was that the installed Codex CLI was outdated (0.42.0). During startup, the codex app-server produced output that T3 Code did not expect, so the app never received the normal initialization response and eventually timed out. Updating Codex from 0.42.0 to 0.111.0 resolved the problem.
What seems worth reporting is not just the version mismatch itself, but the user-facing behavior around it. The codebase already has provider health checks and logging, so the main gap appears to be that this startup failure is surfaced too generically for users. Instead of clearly indicating that Codex startup failed in an unexpected state, the app only showed repeated Runtime error entries, which makes the issue much harder to understand without digging through logs.
-- Written by t3-code, I am not a dev
