Back to Signal Feed
CodeTracked since May 19, 2026

POSIX ACP CLI detection adds per-tool fallback after batch timeout

`AcpDetector.batchCheckCliAvailability` on POSIX was changed so a slow PATH scan no longer makes all built-in ACP CLIs appear missing. The batch `command -v` probe timeout was raised from 3s to 8s, and on batch timeout it now falls back to parallel per-CLI checks with a 3s limit each, isolating slow lookups from other tool detections.

AcpDetector.batchCheckCliAvailabilityPOSIX_BATCH_TIMEOUT_MSPOSIX_PER_CLI_TIMEOUT_MScommand -v

What Happened

  • `AcpDetector.batchCheckCliAvailability` on POSIX was changed so a slow PATH scan no longer makes all built-in ACP CLIs appear missing. The batch `command -v` probe timeout was raised from 3s to 8s, and on batch timeout it now falls back to parallel per-CLI checks with a 3s limit each, isolating slow lookups from other tool detections.
  • `AcpDetector.batchCheckCliAvailability` on POSIX was changed so a slow PATH scan no longer makes all built-in ACP CLIs appear missing. The batch `command -v` probe timeout was raised from 3s to 8s, and on batch timeout it now falls back to parallel per-CLI checks with a 3s limit each, isolating slow lookups from other tool detections.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Implemented a two-stage POSIX CLI detection flow: a larger batch timeout (8000 ms) for the fast path, and a bounded per-CLI fallback path (3000 ms each) only when the batch fails. This change keeps the public sync API unchanged while stopping one slow filesystem entry from causing false negatives across all detected tools, and includes unit coverage for empty input, normal batch parsing, fallback-on-rejection, and full graceful failure.

Why Track This

Why It Matters

Developers and operators using AionUi in WSL, Docker, or slow-mounted PATH environments should see far fewer startup cases where all assistants disappear from the picker, so installed CLIs remain usable without manual troubleshooting. Technically, the patch changes POSIX detection from an all-or-nothing batch failure model to batch-first with parallel per-CLI recovery, so a single delayed lookup cannot mask the availability of others; continue watching startup latency when many CLIs are absent and whether fallback logs still clearly separate true missing tools from slow-path delays.

Impact

Developers and operators using AionUi in WSL, Docker, or slow-mounted PATH environments should see far fewer startup cases where all assistants disappear from the picker, so installed CLIs remain usable without manual troubleshooting. Technically, the patch changes POSIX detection from an all-or-nothing batch failure model to batch-first with parallel per-CLI recovery, so a single delayed lookup cannot mask the availability of others; continue watching startup latency when many CLIs are absent and whether fallback logs still clearly separate true missing tools from slow-path delays.

What To Watch Next

  • Watch whether AcpDetector.batchCheckCliAvailability becomes a repeated pattern.
  • Track follow-up changes around AI Agents.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: monitor_per_cli_fallback_overhead_with_many_cli_entries, watch_incorrect_missing_cli_classification_when_permission_errors_occur.
Open Topic TimelineOpen Technical EventOpen Original Sourcemonitor_per_cli_fallback_overhead_with_many_cli_entries / watch_incorrect_missing_cli_classification_when_permission_errors_occur / watch_error_logging_clarity_for_batch_vs_tool_level_failures

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

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

Prevents false-negative CLI availability results in AionUi startup on WSL/Docker/Linux paths with slow mounted directories.