Repository navigation
fix(provider): make readiness probe timeouts configurable - #33275
Merged
juliusmarminge merged 10 commits intoNov 12, 2026
Merged
juliusmarminge merged 10 commits into
juliusmarminge merged 10 commits into
Conversation
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Provider readiness checks have hardcoded deadlines. On a remote Linux cluster, Codex was authenticated and working, but T3 Code's check timed out. Raising the installed timeout to 60 seconds let a probe complete successfully in 22.2 seconds. Patching the executable has to be repeated after updates.
Add
T3CODE_<PROVIDER>_PROBE_TIMEOUT_MSoverrides for Codex, Claude, Cursor, Antigravity, Grok, Kiro, fx, Pi, Muse, OpenCode, and ACP Registry agents. Each override controls that provider's existing readiness deadlines, including nested discovery/startup limits that would otherwise cut the configured wait short. Without an override, each phase keeps its current default. Invalid, nonpositive, fractional, or overflowing values fall back to the phase default.Codex's discovery deadline follows its overall status-check budget. Other providers can have several sequential probe phases, so this is a per-phase limit rather than a total refresh deadline. The guide lists the variables and explains how to keep them in a remote server's launcher, systemd service, or provider-instance environment. Turn execution, installation-command, update-check, and shutdown deadlines are unchanged; optional usage/config enrichment keeps its shorter limits.
Closes #33266. Related: #27230 and #31023. This configures an existing capability without changing defaults or adding UI, following CONTRIBUTING.md's focused-configuration exception.
Verification:
corepack pnpm --filter t3 --filter '@t3tools/provider-*' run typecheck.vp run check:changed c73b38b379542cde87ec8bc855b70e7fae78fb5ccould not pass its broader workspace checks: Knip cannot load the uninstalled Expo/Astro configs, and the desktop typecheck cannot find Electron types. The filtered checkout contains server/provider dependencies. The separate typecheck above passed. The commit hook runs the same workspace Knip check, so it was bypassed after running these checks explicitly.The Linux cluster timings are the user's reported measurements; I did not rerun that live setup. The issue does not attribute the latency to a particular plugin.
Model: GPT-6.1-Sol. Harness: Codex CLI in T3 Code.