Symptom
Windows dogfooding repeatedly reports that fd is missing. The prompt recurs instead of resolving once or degrading cleanly, creating startup/runtime noise and making it unclear whether OpenAlice or an embedded agent actually requires the binary.
Expected behavior
- Identify which runtime/component performs the
fd check.
- If
fd is optional, use the available fallback and avoid repeated prompts.
- If it is required, ship it with the managed Windows toolchain or provide one clear install/repair action.
- Persist or cache the resolved readiness state so the same warning is not shown on every launch/probe.
Suspected location
- Windows agent runtime readiness/startup path
- managed desktop toolchain packaging
- upstream Pi/Codex resource discovery if the message does not originate in OpenAlice
A repository search currently finds no OpenAlice dependency on the fd executable; the only literal fd in desktop main is the Node IPC file descriptor. Capture the exact Windows log/prompt text when investigating.
Why deferred
The active fix is limited to Pi skill discovery and --approve compatibility. The Windows dependency prompt needs a separate reproduction on the dogfood machine.
Cross-references
Symptom
Windows dogfooding repeatedly reports that
fdis missing. The prompt recurs instead of resolving once or degrading cleanly, creating startup/runtime noise and making it unclear whether OpenAlice or an embedded agent actually requires the binary.Expected behavior
fdcheck.fdis optional, use the available fallback and avoid repeated prompts.Suspected location
A repository search currently finds no OpenAlice dependency on the
fdexecutable; the only literalfdin desktop main is the Node IPC file descriptor. Capture the exact Windows log/prompt text when investigating.Why deferred
The active fix is limited to Pi skill discovery and
--approvecompatibility. The Windows dependency prompt needs a separate reproduction on the dogfood machine.Cross-references