-
Notifications
You must be signed in to change notification settings - Fork 0
show connected codex version
Kazushi Kamegawa edited this page Jul 18, 2026
·
1 revision
Date: 2026-07-18 Tracking: Issue #61, sub-issues #62, #63, and #64
Display the version reported by the connected Codex app-server beside the
connection state in the Visual Studio tool-window header. The normal connected
header uses the form Ready · Codex 0.139.0, and the same version remains
visible while a turn is busy or waiting for approval.
- Extract a bounded, validated ASCII version from the first product token in the app-server initialize response user agent.
- Add the nullable Codex version to Worker contract version 9 and preserve it across ready, busy, and waiting-for-approval states.
- Clear stale version data before reconnecting and omit it while connecting, disconnected, or degraded.
- Expose sanitized, serializable Remote UI presentation properties and render the version beside the state without obscuring the state at narrow widths.
- Preserve Visual Studio theme resources and provide a concise UI Automation status announcement without duplicate version reading.
- Update the fake app-server, tests, and implementation records as required.
- Cover stable, prerelease, and build-metadata version strings.
- Reject missing, malformed, oversized, non-ASCII, and control-character input.
- Verify ready, busy, approval, reconnect, failure, and disconnect transitions.
- Verify Remote UI serialization, property notifications, XAML layout, truncation, and accessibility metadata.
- Complete the Release build and all Core and UI tests with zero warnings.
- Manually inspect narrow layouts and light, dark, and high-contrast themes.
- Do not start a separate version process; use the connected app-server handshake.
- Do not display the full user agent or Codex home path.
- Add no NuGet packages.
- Keep source, comments, tests, documentation, and commit messages in English.