Pi provider reports "timed out" on pi --version because the version probe timeout is only 4 s #28393

What happened

T3 Code shows the Pi provider as unavailable: "Pi CLI is installed but timed out while running pi --version."

Diagnosis

The Pi health check runs pi --version with a 4 s limit (VERSION_PROBE_TIMEOUT_MS = 4_000, packages/provider-pi/src/server/status.ts:59 at v0.1.6). pi --version takes about 5 s on this machine and exceeds it. Grok has its own 4_000 constant (packages/provider-grok/src/server/status.ts:61); CLAUDE_VERSION_CHECK_TIMEOUT_MS is already 20_000 (apps/server/src/provider/ClaudeProvider.ts:190). Suggestion: raise the Pi version-probe timeout (e.g. 20 s like Claude) or make provider probe timeouts configurable instead of per-provider constants.

Steps to reproduce

1. Install Pi CLI 1.4.0 via npm on Windows 11 (pi.cmd).
2. Confirm in PowerShell: Measure-Command { pi --version } takes about 5 s (cold 4.97 s, warm 4.94 s).
3. Open T3 Code and check provider status: Pi is unavailable with the timeout message.

Version

Stable 0.1.6 and Nightly 0.1.7-nightly.20261031.3991 (triage CLI 0.1.6)

Environment

Windows 11 Pro x64, Pi CLI 1.4.0 (npm, pi.cmd), Node v26.12.1

Evidence

Measure-Command { pi --version }: 4.97 s cold, 4.94 s warm. Source constants confirmed at tag v0.1.6.

Related issues

Same pattern in #27230 / #27262 (Codex app-server probe, 20 s; fix to 60 s proposed). Different code path. #24122 touches the same pi --version probe for output limits, not timeout.

Fix applied or workaround

Patched the constant to 2e4 (20 s) in the bundled server.asar. Pi then shows Available and works normally, including tool calling.

Filed by

Claude Sonnet 5.5 (claude-sonnet-5-5) in the Claude Code agent via t3 triage