AI Foundry Desk 0.3.1 - A workstation that stays dependable after updates

AI Foundry Desk 0.3.1 — A workstation that stays dependable after updates

AFD 0.3.1 focuses on a simple outcome: your tools should keep working consistently in a normal console, inside Codex tasks, and when you start a fresh session.

Updates no longer leave agent tasks stranded

You can continue updating tools normally with WinGet. AFD now recognizes when an update replaced a tool and unintentionally removed the access an isolated Codex task needs. It explains the exact problem and gives you a reviewable recovery path instead of asking you to reinstall tools, freeze versions, or route everyday commands through AFD.

One clear health check

afd doctor now gives you one place to confirm that the workstation is genuinely usable—not merely configured. It checks the effective identity, runtime versions, executable paths, and whether the core toolchain can actually run in the current context.

That makes it easier to distinguish three different situations:

• the normal user environment is healthy;
• an isolated agent task lacks access to a specific tool;
• optional services such as local observability are simply not active.

Safer recovery with less hidden behavior

AFD does not take over WinGet, replace your tools, or silently change permissions during startup or diagnosis. If recovery is needed, you first see the exact proposed paths and read/execute grants. Applying the repair is a separate, explicit decision and keeps a rollback snapshot.

More predictable project work

Normal-user sessions and isolated agent tasks now share the same project dependency baseline. This removes a class of confusing failures where the repository worked in one context but tried to rebuild or discard dependencies in another.

Private observability when you want it

This release also establishes the optional local observability experience for understanding agent runs and usage. It remains private, local-first, and explicitly activated. Installing or upgrading AFD does not start telemetry, background services, or workstation layers.

When observability is not active, AFD now reports that state clearly instead of returning a low-level connection error.

What remains under your control

• You choose when third-party tools are updated.
• You review permission repairs before applying them.
• You choose whether local observability and autostart are enabled.
• Installing AFD does not automatically apply Layer 1 or Layer 2 changes.

Windows x64 is the fully validated environment for this release. The checksum-verified portable CLI bootstrap remains available for the documented POSIX path; macOS support is still experimental.

Use the checksum-verified install or upgrade command in the README, then run afd doctor.