fix: reduce sidebar polling and replay relay history#543
Open
Chenzr888 wants to merge 1 commit into
Open
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.
Hi! Thanks for building Codex++. I ran into two user-visible issues while using v1.1.9 locally and wanted to contribute a small patch instead of only reporting the problem.
What this changes
previous_response_id, the proxy now replays the prior chat messages before sending the next Chat Completions request, which helps relay mode preserve multi-turn context.previous_response_idreplay.Why
On my machine, Codex itself stays responsive, while Codex++ v1.1.9 can become very slow in the left conversation sidebar. The injected
projectMovesorting path was doing recurring full visible-chat checks even while idle, so this PR keeps the feature but removes the recurring self-schedule.For relay mode, Responses API requests can rely on
previous_response_id, while Chat Completions upstreams are stateless. Replaying the local converted history makes that bridge closer to Codex's expected multi-turn behavior.Verification
node --check assets/inject/renderer-inject.jsgit diff --checkI could not run Rust tests locally because this machine does not currently have
cargoinstalled. The PR includes Rust tests for the protocol proxy and should be covered by the existingcargo test --workspaceCI.