feat(codex): regenerate protocol bindings for Codex 0.159

[juliusmarminge]

Our Codex app-server bindings were generated from 0.156.0, so they lacked the protocol additions shipped since.

• Point the generator at the rust-v0.159.0 tag (687a119f0f) and regenerate. The new surface is account/gatewayOAuth/{read,login,cancel} and the account/gatewayOAuth/changed notification, plus upstream schema changes.
• Upstream names these responses GatewayOAuth*Response, not the AccountGatewayOAuth*Response the generator derives from the method path, so they join the existing response-name overrides.
• The model manifest recommends Codex >=0.159.0 for T3 Code 0.0.44 and later. 0.156 stays supported, and 0.0.42–0.0.43 keep their current policy.

Verified with typechecks of effect-codex-app-server and apps/server, plus the bindings tests, Codex adapter/runtime/wire tests, and the manifest and compatibility tests.

Live check against Codex 0.159.0

Drove a real codex app-server 0.159.0 through the regenerated client, with real inference:

initialize.userAgent t3-live-0159/0.159.0 (Ubuntu 26.4.0; x86_64) ...
account/read ok, type: chatgpt
model/list ok: gpt-6.1-sol, gpt-6-astra, gpt-6-sol, ... (17 models)
account/rateLimits/read: Success
account/gatewayOAuth/read: {"error":null,"providerId":"openai","providerName":"OpenAI","required":false,"status":null}
thread/start ok: model gpt-5.6-sol
turn/completed status: completed
agent text: "pong 0.159"
notifications decoded: thread/started, thread/status/changed ×2, turn/started, item/started ×2, item/completed ×2, thread/tokenUsage/updated

A dev server with the Codex provider pointed at 0.159.0 also completed its provider probe (CodexInstallation.compatibility, requestAllCodexModels, probeCodexAppServerProvider, checkCodexProviderStatus all succeeded).

🤖 Generated with Claude Code (Claude Opus 5.5)

---

Summary by CodeRabbit

• Compatibility
  • Codex versions 0.0.44 and later now recommend client version 0.159.0 or later. Versions from 0.0.42 up to, but not including, 0.0.44 retain the recommendation for client version 0.156.0 or later.
  • Supported, unsupported, and broken client-version ranges remain unchanged.

[github-actions]

Thread transfer impact

✅ Thread transfer remains within every enforced ceiling.

ℹ️ The exact PR base did not have a successful artifact. Baseline uses the latest successful main measurement shown below.

Provider	Metric	Main baseline	This PR	Impact	PR ceiling
Codex	Total thread wire	13.5 KiB	13.6 KiB	+50 B (+0.4%)	15.1 KiB	✅
Codex	Thread snapshot wire	7.0 KiB	7.1 KiB	+17 B (+0.2%)	7.3 KiB	✅
Codex	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+33 B (+0.5%)	7.8 KiB	✅
Codex	Live turn WebSocket decoded	56.3 KiB	56.3 KiB	0 B (0.0%)	66.4 KiB	✅
Codex	Live turn messages	10	10	0 (0.0%)	21	✅
Claude	Total thread wire	13.5 KiB	13.6 KiB	+35 B (+0.3%)	15.1 KiB	✅
Claude	Thread snapshot wire	7.1 KiB	7.1 KiB	+8 B (+0.1%)	7.3 KiB	✅
Claude	Live turn WebSocket wire	6.5 KiB	6.5 KiB	+27 B (+0.4%)	7.8 KiB	✅
Claude	Live turn WebSocket decoded	57.0 KiB	57.1 KiB	+44 B (+0.1%)	66.4 KiB	✅
Claude	Live turn messages	9	10	+1 (+11.1%)	21	✅

Baseline: 408ff8a · PR result: 3448dd0 · Source CI: success

Scenario and decoded snapshot size

10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.

• Codex decoded thread snapshot: 114.0 KiB
• Claude decoded thread snapshot: 114.7 KiB

Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed.

[macroscopeapp]

Approvability

Verdict: Not approved

Macroscope's review found this PR not approvable — The PR regenerates Codex bindings with new gateway OAuth requests, authorization-status notifications, and initialization controls, making authentication behavior part of the changed runtime contract. Existing defaults remain unchanged, but the authentication-sensitive API expansion requires human review.

^{You can add or adjust custom eligibility rules. Learn more.}

[coderabbitai]

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: pingdotgg/t3code/.coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 98f8d5fe-ea66-4d7a-b982-1904f8d5e664

📥 Commits

Reviewing files that changed from the base of the PR and between 451afcb and 3448dd0.

⛔ Files ignored due to path filters (3)

• packages/effect-codex-app-server/src/_generated/meta.gen.ts is excluded by !**/_generated/**
• packages/effect-codex-app-server/src/_generated/namespaces.gen.ts is excluded by !**/_generated/**
• packages/effect-codex-app-server/src/_generated/schema.gen.ts is excluded by !**/_generated/**

📒 Files selected for processing (2)

• apps/server/src/provider/model-manifest.json
• packages/effect-codex-app-server/scripts/generate.ts

Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 9 remain after this review.

---

📝 Walkthrough

Walkthrough

The Codex generator now uses a different upstream revision and explicitly resolves response schemas for three gateway OAuth methods. The model manifest separates Codex compatibility recommendations by t3Code version and updates its timestamp.

Changes

Codex updates

Layer / File(s)	Summary
Codex protocol generation packages/effect-codex-app-server/scripts/generate.ts	The generator uses a new upstream commit and adds response-schema mappings for the gateway OAuth cancel, login, and read methods.
Codex compatibility ranges apps/server/src/provider/model-manifest.json	The manifest recommends client version >=0.159.0 for t3Code >=0.0.44. It retains the previous recommendation and compatibility ranges for >=0.0.42 and <0.0.44, and updates the manifest timestamp.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Feature

Suggested reviewers: t3dotgg

Merge Risk: ⚪ Minimal · up to 3448d

The generated OAuth bindings match the pinned schemas, and the Codex recommendation changes at the intended T3 Code version. No actionable merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (1 skipped: 1 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly and concisely describes the main change: regenerating Codex protocol bindings for Codex 0.159.
Description check	✅ Passed	The description clearly explains what changed, why it changed, compatibility policy updates, validation performed, and live verification results. It does not include the checklist section, but the req…

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (1 skipped: 1 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches 💡 1

📝 Generate docstrings 💡

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}