Skip to content

fix(tui): detect persistent app-server version skew before resume - #8

Open
fscfede-beep wants to merge 6 commits into
mainfrom
fix/37754-tui-version-skew
Open

fix(tui): detect persistent app-server version skew before resume#8
fscfede-beep wants to merge 6 commits into
mainfrom
fix/37754-tui-version-skew

Conversation

@fscfede-beep

@fscfede-beep fscfede-beep commented Sep 8, 2026

Copy link
Copy Markdown
Owner

Focused validation patch for upstream Codex openai#37754. list_turns is implemented by the local thread store, while reports show the failure when a persistent app-server is older/incompatible with the TUI. The TUI already sends its client version during initialize and RemoteAppServerClient exposes the server version returned by the handshake. This patch applies a fail-safe version guard only to LocalDaemon connections (the observed persistent-daemon skew case), rejecting a mismatch before thread/resume with an actionable daemon-restart message. Explicit Remote connections are not blocked by exact version equality. Adds pure unit coverage for equal, absent, and mismatched versions. Fork validation only; upstream mutation is unavailable through the connected integration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant