Release candidate
September 10, 2026 · View on GitHub
The candidate is v2.0.0-alpha.27 on codex/release-validation. Its code commit is 8da0900fff95ce28e4fe403b68157fd9da3c1bf0, based on aef6820276e67ff7e9b770834b7e0fb39b2ef173. Remote tags were checked on 9 September: v2.0.0-alpha.26 remains the latest tag in this series. The user approved publication on 9 September after confirming the OAuth name in the demo. The versioned changelog and migration notes include the account-name addition.
Account-name behavior
Browser OAuth and device-code sign-in/refresh read the optional name claim from the ID token. ChatGPTAccount.displayName trims surrounding whitespace and falls back to email for absent or blank names. The demo's signed-in header uses this property.
Existing saved sessions without name still decode. The original three-argument account initializer is preserved, including initializer-as-function references. Tests cover Unicode, missing/null/blank names, both authentication methods, token refresh, JSON round trips, and runtime Keychain persistence. The new initializer-reference regression was reproduced as a compiler failure before preserving the original overload.
Local verification
| Check | Result | Evidence |
|---|---|---|
| Release build, warnings as errors | Passed, all four library products | .build/account-name-release-build.log |
| Final package suite, warnings as errors | 532 executed: 526 passed, 6 opt-in skips, zero failures | .build/account-name-release-package-tests.log |
| Optimized regression/performance/concurrency checks | 29 passed, zero failures; 40 rounds per adapter | .build/account-name-optimized-tests.log |
| Signed demo build | Passed | .build/account-name-demo-final-build.log |
| Signed simulator runtime | Passed: SQLite, Realm, reopening, completion, cancellation | .build/account-name-simulator-verification/CodexKitVerification.json |
| Verification harness | 7 tests passed | PYTHONDONTWRITEBYTECODE=1 python3 -m unittest discover -s Tests/Verification |
| Production source-size guard | 211 files passed, each at most 600 lines | python3 scripts/check_source_size.py |
| Public API comparison against alpha.26 | Reviewed; no additional breaking diagnostics from account-name support | .build/account-name-api-review/ |
The simulator run used iOS 26.5 / iPhone 17 Pro, run ID b9b4cd38-ff6b-4417-9b47-89d7250f5d0a, finishing at 2026-09-09T04:09:57Z. It ran the final signed demo build in a disposable simulator and explicitly disabled live-account access. The temporary simulator was removed afterward. That run built the app at .build/simulator-verification/Build/Products/Debug-iphonesimulator/AssistantRuntimeDemoApp.app.
The optimized selection completed in 93.012 seconds. Its file, SQLite, and Realm concurrency checks each ran 40 rounds with six workers: 720 total lifecycle operations, 120 reader reopens, and 60 owning-runtime replacements. All passed independent transcript and attachment checks.
The full package suite completed in 137.085 seconds. Its six skips are the two live-provider tests and four opt-in performance workloads; the latter were enabled in the separate optimized run above.
The API comparison still reports the seven earlier default-parameter initializer changes and two optional configuration properties documented in the migration guide. It reports no removed/changed public UI declarations or new core protocol requirements. It does not establish binary ABI compatibility.
Local logs are retained under .build/ and are not committed.
Hosted verification
All four jobs in the candidate CI run passed for code commit 8da0900fff95ce28e4fe403b68157fd9da3c1bf0: current and minimum package/release verification, the Swift 6.1 iOS 17 build, and actual iOS 17 runtime verification. The current job also passed optimized regression/concurrency checks and signed simulator execution. Final job status is retained locally in .build/account-name-hosted-ci.json.
This final results update changes documentation only; it does not change the verified SDK, tests, demo sources, or workflows. Hosted CI retains its own package, optimized-test, and simulator evidence.
Manual demo checks
- Open
DemoApp/CodexKitDemo.xcodeprojin Xcode, selectCodexKitIOSDemo, and run on your device or simulator. The shared scheme starts the normal UI without--verify-runtime. - Complete a fresh sign-in and inspect Signed in as on the Assistant tab. Expect the account name when supplied by authentication, otherwise the email. A restored older session can remain on the email fallback until sign-in or token refresh supplies a name.
- Close and relaunch the app. Confirm the saved session and displayed name/email are restored.
- Send a short message and confirm normal replies still work. If you use both browser and device-code sign-in, check each flow.
- Report whether a real account name appeared and whether sign-in, restoration, and messaging worked. Do not share raw tokens.
Fresh browser OAuth sign-in was confirmed on an iOS 26.5 simulator on 9 September: the user reported seeing the name in the demo. A temporary diagnostic recorded a nonempty top-level ID-token name, distinct from the email, and a populated account.name. The name was also present in the access token's namespaced profile and the provider's advertised user-info response (HTTP 200). The diagnostic only read those additional sources; the displayed name came from the existing ID-token implementation. It recorded field names/presence rather than token or profile values and was removed afterward. No additional profile request was added to the SDK. The local diagnostic summary is .build/account-name-oauth-diagnostic-result.json.
After removing the diagnostics, the normal demo build was rebuilt, installed over the diagnostic build without clearing app data, and relaunched. The demo restored the saved OAuth session and still displayed the name.
This confirms real-token name availability and session restoration for the tested browser OAuth flow. It does not yet confirm the original physical-device session, device-code sign-in, or live messaging checks. The existing live plain/structured and image-compaction/reopen tests also remain unverified for this candidate; the Mac tests need a Mac SDK/demo session, separate from an iOS device's session.
Publication handoff
- User publication approval received on 9 September; manual OAuth name and restoration results are recorded above.
- README release links and changelog comparisons target alpha.27.
- Fast-forward the reviewed candidate onto
mainand create an annotatedv2.0.0-alpha.27tag. - The tag triggers the release workflow, which repeats required checks before publishing the GitHub prerelease.