Back to Signal Feed
CodeTracked since May 19, 2026

Fix POSIX ACP CLI detection to avoid false-missing results after timeout

The PR replaces a brittle POSIX batch-only CLI availability check with a two-step strategy: it raises the batch `command -v` timeout to 8000ms, and on batch timeout it runs parallel per-CLI probes (each with 3000ms). This prevents a single slow PATH entry from forcing all built-in ACP CLIs to be reported as missing.

AcpDetectorPOSIX batch CLI detectioncommand -vsafeExec

What Happened

  • The PR replaces a brittle POSIX batch-only CLI availability check with a two-step strategy: it raises the batch `command -v` timeout to 8000ms, and on batch timeout it runs parallel per-CLI probes (each with 3000ms). This prevents a single slow PATH entry from forcing all built-in ACP CLIs to be reported as missing.
  • The PR replaces a brittle POSIX batch-only CLI availability check with a two-step strategy: it raises the batch `command -v` timeout to 8000ms, and on batch timeout it runs parallel per-CLI probes (each with 3000ms). This prevents a single slow PATH entry from forcing all built-in ACP CLIs to be reported as missing.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Updated `AcpDetector.batchCheckCliAvailability` in `src/process/agent/acp/AcpDetector.ts` by introducing `POSIX_BATCH_TIMEOUT_MS = 8000`, adding `POSIX_PER_CLI_TIMEOUT_MS = 3000`, and adding fallback logic that runs isolated per-CLI `command -v` checks when the batch probe times out.

Why Track This

Why It Matters

Users and operators running AionUi in WSL, Docker, or Linux hosts with slow mounted PATHs will no longer see all ACP CLIs disappear as unavailable at startup, so installed tools remain selectable and usable instead of silently falling back to a degraded workflow. Technical mechanism: the detector still prefers a fast batch probe for normal environments, but now recovers from timeout cases by probing each CLI independently with bounded 3s checks; continue watching whether fallback frequency increases on very slow filesystems and whether per-CLI fallback meaningfully extends startup latency when many CLIs repeatedly timeout.

Impact

Users and operators running AionUi in WSL, Docker, or Linux hosts with slow mounted PATHs will no longer see all ACP CLIs disappear as unavailable at startup, so installed tools remain selectable and usable instead of silently falling back to a degraded workflow. Technical mechanism: the detector still prefers a fast batch probe for normal environments, but now recovers from timeout cases by probing each CLI independently with bounded 3s checks; continue watching whether fallback frequency increases on very slow filesystems and whether per-CLI fallback meaningfully extends startup latency when many CLIs repeatedly timeout.

What To Watch Next

  • Watch whether AcpDetector becomes a repeated pattern.
  • Track follow-up changes around Tool Calling.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: watch_batch_vs_per_cli_timeout_tuning, watch_increased_startup_delay_on_heavy_fallback.
Open Topic TimelineOpen Technical EventOpen Original Sourcewatch_batch_vs_per_cli_timeout_tuning / watch_increased_startup_delay_on_heavy_fallback / watch_residual_false_negatives_on_slow_filesystems

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

iOfficeAI/AionUi PR #2938: fix(acp): per-CLI fallback when batch CLI detection times out

Batch check timeout increased from 3000ms to 8000ms, with automatic per-CLI fallback using `safeExec` and `Promise.allSettled` when the batch path times out.