Repository navigation
fix(runtime): keep Codex account and tape sticky - #735
Merged
Merged
Conversation
Codex OAuth accounts are session options under one provider. Runtime rebuilds reuse the bound tape_id so a completed session's next prompt does not rebind. Verified: ruff; 250 pytest; 308 vitest.
Finalizer copies ctx tape on first bind and keeps a sticky session tape_id. create_agent must not treat an empty Tape as missing, or restored named tapes get a new uuid.
Sticky tape_id is enforced at daemon prepare. complete only assigns on first bind so later turns cannot overwrite it.
delete-cloud
marked this pull request as ready for review
September 3, 2026 08:08
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.
Summary
Phase F serving follow-up after live Codex verification.
provider_nameascodex:<label>.tape_idacross runtime rebuilds (retain_session_tapein daemon prepare and ensure) so a completed session's next prompt does not raisesession tape target cannot be rebound.Test plan
uv run ruff checkon touched Python filesuv run pytestfocused runtime/CLI/config (250 passed)pnpm testinwebui/app-next(308 passed)TURN1_OKthenTURN2_OK, one tape_idOut of scope: settings
replace_runtime_configtape rebind; Next.js cross-origin 403 to daemon; production new-runtime activation flag; Phase G.