Repository navigation
V0.8.0: native Codex runtime and responsive workspace - #2
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
V0.7.1 restarted its Python/Codex reader for individual requests and layered polling and duplicate UI state onto interactive work. V0.8.0 keeps one installed Codex App Server under the Rust Agent, delivers authorized traffic over an outbound persistent connection, and shows cached history immediately while reconciling in the background.
Validation:
make check,make test(95 Rust and 19 Console tests),make privacy, Console build and 59 browser checks passed; nine redundant browser matrix cases are intentionally skipped. Native protocol checks cover Codex 0.153.4 and 0.147.0. Release installation/rollback tests and a real isolated Hub → Linux Agent → browser loop cover reading, sending, queuing, interruption, notifications and reconnection. A V0.7.1 → V0.8.0 → V0.7.1 → V0.8.0 database roundtrip retains completed receipts and does not replay uncertain work.Controlled browser benchmarks load all 100 pages of a 2000-turn history: 11 turns remain mounted, cached switching p95 is 92 ms, and 20 sends use 40 HTTP requests (previously about 80). Each simulated network segment has 80 ms RTT; these figures exclude model time. Private machine-specific evidence is intentionally kept outside Git.
The final real-host test found and fixed duplicate history reads when terminal events and command receipts arrived separately. Refreshes now deduplicate by operation/turn identity, with a regression covering both arrival orders. Under two added 80 ms RTT segments, 30 real native reads of the latest 20 turns reached 243 ms p95, 30 save acknowledgements reached 208 ms p95, and 20 sends used 42 total HTTP requests. An active turn also survived Hub reconnection before interruption, and its queued follow-up completed.