feat: update OpenAI OAuth model filter for GPT-5.5

[Astro-Han]

Summary

Backport upstream OpenCode commit 97f3c746f3f to include gpt-5.5 in the OpenAI OAuth/Codex model allowlist.

Why

The refreshed models.dev catalog already contains gpt-5.5, but OpenAI OAuth applies a plugin-level allowlist before exposing models. Without this backport, PawWork can refresh the catalog successfully and still hide gpt-5.5 from ChatGPT Pro/Plus OAuth users.

Related Issue

Closes #228.

How To Verify

bun --cwd packages/opencode test test/plugin/codex.test.ts test/provider/models-refresh.test.ts

Screenshots or Recordings

Not applicable. No visible UI changes beyond model availability after auth.

Checklist

• I linked the related issue, or stated why there is no issue
• This PR has type, scope, and priority labels, or I requested maintainer labeling
• I listed the relevant verification steps, including tests when behavior changed
• I manually checked visible UI or copy changes when needed, with screenshots or recordings
• I considered macOS and Windows impact for desktop, packaging, updater, signing, paths, shell, or permissions changes
• I called out docs, release notes, dependencies, permissions, credentials, deletion behavior, or generated/local file changes when relevant
• I am targeting dev, and my PR title and commit messages use Conventional Commits in English

Summary by CodeRabbit

• Bug Fixes
  • Updated Codex OAuth model filtering: Codex-labeled models and explicit whitelist entries are kept, newer gpt versions (semantic versions > 5.4) are now allowed, while older or unrelated models are excluded to prevent offering unsupported options during authentication.
• Tests
  • Added coverage validating model/pair scenarios and semantic-version ordering for allowed and disallowed gpt releases.

[gemini-code-assist]

Code Review

This pull request adds the gpt-5.5 model to the allowlist in codex.ts. Feedback suggests that additional updates are required in the reasoning effort logic for both gpt-5.4 and gpt-5.5 to support specific variants, and recommends adding gpt-5.5-mini to the allowlist for consistency.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: bf24ac9c-ccc0-42c8-8618-f646abeb6919

📥 Commits

Reviewing files that changed from the base of the PR and between 31f3c2c and 9d4ec08.

📒 Files selected for processing (2)

• packages/opencode/src/plugin/codex.ts
• packages/opencode/test/plugin/codex.test.ts

📜 Recent review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)

• GitHub Check: unit-windows-opencode-config-project
• GitHub Check: unit-windows-desktop
• GitHub Check: unit-windows-opencode-server-tools
• GitHub Check: unit-windows-opencode-session
• GitHub Check: unit-windows-app
• GitHub Check: typecheck
• GitHub Check: unit-desktop
• GitHub Check: unit-opencode
• GitHub Check: unit-app
• GitHub Check: smoke-macos-arm64
• GitHub Check: analyze-js-ts
• GitHub Check: e2e-artifacts

🧰 Additional context used

📓 Path-based instructions (2)

packages/opencode/**/*.ts

📄 CodeRabbit inference engine (packages/opencode/AGENTS.md)

packages/opencode/**/*.ts: Use Effect.gen(function* () { ... }) for Effect composition
Use Effect.fn("Domain.method") for named/traced effects and Effect.fnUntraced for internal helpers; these accept pipeable operators as extra arguments to avoid unnecessary outer .pipe() wrappers
Use Effect.callback for callback-based APIs
Prefer DateTime.nowAsDate over new Date(yield* Clock.currentTimeMillis) when you need a Date in Effect code
Use Schema.Class for multi-field data in Effect schemas
Use branded schemas (Schema.brand) for single-value types in Effect
Use Schema.TaggedErrorClass for typed errors in Effect schemas
Use Schema.Defect instead of unknown for defect-like causes in Effect code
In Effect.gen / Effect.fn, prefer yield* new MyError(...) over yield* Effect.fail(new MyError(...)) for direct early-failure branches
Use makeRuntime from src/effect/run-service.ts for all services; it returns { runPromise, runFork, runCallback } backed by a shared memoMap that deduplicates layers
Use InstanceState from src/effect/instance-state.ts for per-directory or per-project state that needs per-instance cleanup; do work directly in the InstanceState.make closure where ScopedCache handles run-once semantics
Use Effect.addFinalizer or Effect.acquireRelease inside the InstanceState.make closure for cleanup (subscriptions, process teardown, etc.)
Use Effect.forkScoped inside the InstanceState.make closure for background stream consumers — the fiber is interrupted when the instance is disposed
Prefer FileSystem.FileSystem instead of raw fs/promises for effectful file I/O in Effect services
Prefer ChildProcessSpawner.ChildProcessSpawner with ChildProcess.make(...) instead of custom process wrappers in Effect services
Prefer HttpClient.HttpClient instead of raw fetch in Effect services
Prefer Path.Path, Config, Clock, and DateTime services when those concerns are already inside Effect code
For backgroun...

Files:

• packages/opencode/test/plugin/codex.test.ts
• packages/opencode/src/plugin/codex.ts

packages/opencode/test/**/*.test.{ts,tsx}

📄 CodeRabbit inference engine (packages/opencode/test/AGENTS.md)

packages/opencode/test/**/*.test.{ts,tsx}: Use the tmpdir function from fixture/fixture.ts to create temporary directories for tests with automatic cleanup. Use await using syntax to ensure automatic cleanup when the variable goes out of scope.
When using the tmpdir function with git repository support, pass the git: true option to initialize a git repo with a root commit.
Use the config option in tmpdir to write an opencode.json config file during test setup by passing a partial Config.Info object.
Use the init option in tmpdir to define custom setup functions that can return extra data accessible via tmp.extra, and use the dispose option for custom cleanup logic.
Use testEffect(...) from test/lib/effect.ts for tests that exercise Effect services or Effect-based workflows.
Use it.effect(...) when the test should run with TestClock and TestConsole. Use it.live(...) when the test depends on real time, filesystem mtimes, child processes, git, locks, or other live OS behavior.
Prefer Effect-aware helpers from fixture/fixture.ts over building manual runtimes in tests: use tmpdirScoped() for scoped temp directories, provideInstance(dir)(effect) for low-level binding without directory creation, provideTmpdirInstance(...) for single temp instance binding, or provideTmpdirServer(...) for tests that also need the test LLM server.
Define const it = testEffect(...) near the top of the test file and keep the test body inside Effect.gen(function* () { ... }). Yield services directly with yield* MyService.Service or yield* MyTool.
Avoid custom ManagedRuntime, attach(...), or ad hoc run(...) wrappers in Effect tests when testEffect(...) already provides the runtime.
When a test needs instance-local state, prefer provideTmpdirInstance(...) or provideInstance(...) over manual Instance.provide(...) inside Promise-style tests.

Files:

• packages/opencode/test/plugin/codex.test.ts

🧠 Learnings (9)

📓 Common learnings

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 224
File: packages/app/src/i18n/zh.ts:0-0
Timestamp: 2026-04-24T17:08:44.294Z
Learning: In Astro-Han/pawwork PR `#224`, the first-occurrence `PawWork 爪印` branding rule originally specified in issue `#196` was superseded by an updated Chinese-branding spec. On all zh UI surfaces in `packages/app/src/i18n/zh.ts` (e.g., `dialog.model.unpaid.freeModels.title`, `session.new.subtitle`, `sidebar.gettingStarted.line1`), the correct and intentional target is fully localized `爪印` branding — no `PawWork` prefix. Do NOT flag these strings as missing the first-occurrence `PawWork 爪印` rule in future reviews.

📚 Learning: 2026-04-22T08:49:47.800Z

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 126
File: packages/desktop-electron/src/main/index-sidecar-source.test.ts:3-11
Timestamp: 2026-04-22T08:49:47.800Z
Learning: In `packages/desktop-electron/src/main/index-sidecar-source.test.ts` (Astro-Han/pawwork), the test intentionally uses `expect(source).toContain` / `expect(source).not.toContain` string matching against the raw `index.ts` source text as a lightweight sidecar contract guard. The maintainer has explicitly chosen not to introduce an AST parser (e.g., `babel/parser` or acorn) for this purpose. Do not flag these string-based assertions as fragile or suggest converting them to AST-based matching.

Applied to files:

• packages/opencode/test/plugin/codex.test.ts
• packages/opencode/src/plugin/codex.ts

📚 Learning: 2026-04-22T09:32:54.556Z

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 126
File: packages/opencode/test/provider/provider.test.ts:64-85
Timestamp: 2026-04-22T09:32:54.556Z
Learning: In `packages/opencode/test/provider/provider.test.ts`, the file intentionally uses AppRuntime-based async helpers (`run`, `list`, `getProvider`, etc.) rather than `testEffect(...)` for all tests. Converting individual tests to `testEffect` while leaving the rest on the async pattern would create internal inconsistency. A full harness migration of this file is the right approach if the pattern needs to change, but that should be a separate PR.

Applied to files:

• packages/opencode/test/plugin/codex.test.ts

📚 Learning: 2026-04-20T14:36:31.032Z

Learnt from: CR
Repo: Astro-Han/pawwork PR: 0
File: packages/opencode/test/AGENTS.md:0-0
Timestamp: 2026-04-20T14:36:31.032Z
Learning: Applies to packages/opencode/test/**/*.test.{ts,tsx} : Define `const it = testEffect(...)` near the top of the test file and keep the test body inside `Effect.gen(function* () { ... })`. Yield services directly with `yield* MyService.Service` or `yield* MyTool`.

Applied to files:

• packages/opencode/test/plugin/codex.test.ts

📚 Learning: 2026-04-24T06:50:02.712Z

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 211
File: packages/opencode/src/provider/models.ts:113-179
Timestamp: 2026-04-24T06:50:02.712Z
Learning: In Astro-Han/pawwork (`packages/opencode/src/provider/models.ts`), `PublishModel` and `PublishProvider` intentionally duplicate fields from `Model` and `Provider` with looser optionality. The split is a deliberate behavior boundary: `PublishModel`/`PublishProvider` (with `.passthrough()`) are used for lenient publish-time validation of incoming catalogs, while `Model`/`Provider` are used for strict runtime normalization. Do not flag this duplication as a maintenance burden or suggest extracting a shared base schema — the explicit separation is intentional and tied to the models-refresh reliability path introduced in PR `#211`.

Applied to files:

• packages/opencode/test/plugin/codex.test.ts
• packages/opencode/src/plugin/codex.ts

📚 Learning: 2026-04-20T14:36:31.032Z

Learnt from: CR
Repo: Astro-Han/pawwork PR: 0
File: packages/opencode/test/AGENTS.md:0-0
Timestamp: 2026-04-20T14:36:31.032Z
Learning: Applies to packages/opencode/test/**/*.test.{ts,tsx} : Use `testEffect(...)` from `test/lib/effect.ts` for tests that exercise Effect services or Effect-based workflows.

Applied to files:

• packages/opencode/test/plugin/codex.test.ts

📚 Learning: 2026-04-20T14:36:04.113Z

Learnt from: CR
Repo: Astro-Han/pawwork PR: 0
File: packages/app/e2e/AGENTS.md:0-0
Timestamp: 2026-04-20T14:36:04.113Z
Learning: Applies to packages/app/e2e/packages/app/src/testing/**/*.ts : Test-only hooks must be inert unless explicitly enabled and should not add normal-runtime listeners, reactive subscriptions, or per-update allocations

Applied to files:

• packages/opencode/test/plugin/codex.test.ts

📚 Learning: 2026-04-23T08:51:00.819Z

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 186
File: packages/opencode/test/plugin/workspace-adaptor.test.ts:139-144
Timestamp: 2026-04-23T08:51:00.819Z
Learning: For pawwork tests under packages/opencode/test/**, auth.json teardown may intentionally combine `Filesystem.write` (from `packages/opencode/src/util/filesystem.ts`) with `node:fs/promises` `unlink` for cleanup. Do not flag this as inconsistent style; it is the established/intentional pattern because `Filesystem` does not provide a `remove`/`unlink` helper.

Applied to files:

• packages/opencode/test/plugin/codex.test.ts

📚 Learning: 2026-04-21T16:00:44.910Z

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 102
File: packages/opencode/src/config/model-id.ts:9-11
Timestamp: 2026-04-21T16:00:44.910Z
Learning: In Astro-Han/pawwork (`packages/opencode/src/config/model-id.ts`), `ConfigModelID` uses a regex that requires a non-empty provider segment and a non-empty model segment separated by `/`, but intentionally allows additional slashes within the model segment. This is because `Provider.parseModel` supports model IDs like `synthetic/hf:zai-org/GLM-4.7`. Do not flag the permissive slash handling as a bug.

Applied to files:

• packages/opencode/src/plugin/codex.ts

🔇 Additional comments (3)

packages/opencode/src/plugin/codex.ts (2)

18-27: Good extraction of OAuth allowlist into a single constant.

This makes the filter policy easier to audit and update without touching loader flow logic.

---

101-109: Semantic GPT version check is correctly implemented and wired.

Parsing major/minor separately fixes the multi-digit minor regression path and keeps intended future GPT models during provider pruning.

Also applies to: 389-390

packages/opencode/test/plugin/codex.test.ts (1)

125-143: Strong regression coverage for the model-retention predicate.

The added cases cover explicit allowlist behavior, semantic-version ordering (including gpt-5.10), and expected rejection paths.

---

📝 Walkthrough

Walkthrough

Refactors Codex OAuth model allowlist: centralizes allowed set into CODEX_OAUTH_ALLOWED_MODELS and exports shouldKeepCodexOAuthModel(modelId, apiId). Models are retained when labeled codex, explicitly whitelisted, or when matching gpt-<major>.<minor> with version > 5.4; provider.model pruning now uses this predicate.

Changes

Cohort / File(s)	Summary
Codex OAuth plugin packages/opencode/src/plugin/codex.ts	Extracts hardcoded allowlist to CODEX_OAUTH_ALLOWED_MODELS, adds and exports shouldKeepCodexOAuthModel(modelId, apiId): boolean, and updates provider model pruning to use that predicate (keeps codex-labeled, whitelisted api.ids, or gpt-<major>.<minor> versions > 5.4).
Tests packages/opencode/test/plugin/codex.test.ts	Adds unit tests covering shouldKeepCodexOAuthModel for codex matches, whitelisted ids, future gpt minor versions (e.g., gpt-5.5, gpt-6.0), and negative cases for older/unrelated models.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related issues

• [Bug] OpenAI OAuth model filter hides refreshed GPT-5.5 catalog model #228 — Missing gpt-5.5 in OAuth model lists; this change broadens the Codex plugin's numeric-version allowance.

Poem

🐰 I hop through model lists at night,
sniffing tags by moonlit light.
Codex kept, whitelist too,
and gpt-5.5 hops through!
A nibble, a hop — the catalog's right.

🚥 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%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: updating the OpenAI OAuth model filter to support GPT-5.5, which is the primary objective addressed by the backport.
Description check	✅ Passed	The description covers all required template sections with specific details: summary of the backport, reasoning about the plugin-level allowlist issue, linked issue reference, clear verification steps, and a completed checklist.
Linked Issues check	✅ Passed	The PR fully addresses issue #228 by implementing semantic version comparison for GPT models, allowing gpt-5.5 and future versions to pass the Codex OAuth allowlist filter while maintaining backward compatibility.
Out of Scope Changes check	✅ Passed	All changes are scoped to the objective: refactoring the Codex OAuth allowlist logic and adding comprehensive test coverage for the new semantic version filtering behavior.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/openai-oauth-gpt55

---

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@packages/opencode/src/plugin/codex.ts`:
- Around line 382-383: The version check using
model.api.id.match(/^gpt-(\d+\.\d+)/) plus parseFloat(match[1]) misparses
versions like "5.10" as 5.1 and will incorrectly drop newer minor releases;
update the logic in the block that uses model.api.id.match and parseFloat to
parse major and minor as integers (e.g., match against /^gpt-(\d+)\.(\d+)/,
convert both captures to integers) and then compare numerically (keep model if
major > 5 or if major == 5 and minor > 4), avoiding parseFloat entirely.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 2ac0d5eb-6bea-4a7f-abd6-acb0e3e849c6

📥 Commits

Reviewing files that changed from the base of the PR and between 041f505 and 31f3c2c.

📒 Files selected for processing (1)

• packages/opencode/src/plugin/codex.ts

📜 Review details

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (12)

• GitHub Check: smoke-macos-arm64
• GitHub Check: unit-windows-app
• GitHub Check: unit-windows-opencode-session
• GitHub Check: unit-windows-opencode-config-project
• GitHub Check: unit-windows-opencode-server-tools
• GitHub Check: unit-windows-desktop
• GitHub Check: unit-opencode
• GitHub Check: typecheck
• GitHub Check: unit-app
• GitHub Check: unit-desktop
• GitHub Check: analyze-js-ts
• GitHub Check: e2e-artifacts

🧰 Additional context used

📓 Path-based instructions (1)

packages/opencode/**/*.ts

📄 CodeRabbit inference engine (packages/opencode/AGENTS.md)

packages/opencode/**/*.ts: Use Effect.gen(function* () { ... }) for Effect composition
Use Effect.fn("Domain.method") for named/traced effects and Effect.fnUntraced for internal helpers; these accept pipeable operators as extra arguments to avoid unnecessary outer .pipe() wrappers
Use Effect.callback for callback-based APIs
Prefer DateTime.nowAsDate over new Date(yield* Clock.currentTimeMillis) when you need a Date in Effect code
Use Schema.Class for multi-field data in Effect schemas
Use branded schemas (Schema.brand) for single-value types in Effect
Use Schema.TaggedErrorClass for typed errors in Effect schemas
Use Schema.Defect instead of unknown for defect-like causes in Effect code
In Effect.gen / Effect.fn, prefer yield* new MyError(...) over yield* Effect.fail(new MyError(...)) for direct early-failure branches
Use makeRuntime from src/effect/run-service.ts for all services; it returns { runPromise, runFork, runCallback } backed by a shared memoMap that deduplicates layers
Use InstanceState from src/effect/instance-state.ts for per-directory or per-project state that needs per-instance cleanup; do work directly in the InstanceState.make closure where ScopedCache handles run-once semantics
Use Effect.addFinalizer or Effect.acquireRelease inside the InstanceState.make closure for cleanup (subscriptions, process teardown, etc.)
Use Effect.forkScoped inside the InstanceState.make closure for background stream consumers — the fiber is interrupted when the instance is disposed
Prefer FileSystem.FileSystem instead of raw fs/promises for effectful file I/O in Effect services
Prefer ChildProcessSpawner.ChildProcessSpawner with ChildProcess.make(...) instead of custom process wrappers in Effect services
Prefer HttpClient.HttpClient instead of raw fetch in Effect services
Prefer Path.Path, Config, Clock, and DateTime services when those concerns are already inside Effect code
For backgroun...

Files:

• packages/opencode/src/plugin/codex.ts

🧠 Learnings (3)

📓 Common learnings

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 224
File: packages/app/src/i18n/zh.ts:0-0
Timestamp: 2026-04-24T17:08:44.294Z
Learning: In Astro-Han/pawwork PR `#224`, the first-occurrence `PawWork 爪印` branding rule originally specified in issue `#196` was superseded by an updated Chinese-branding spec. On all zh UI surfaces in `packages/app/src/i18n/zh.ts` (e.g., `dialog.model.unpaid.freeModels.title`, `session.new.subtitle`, `sidebar.gettingStarted.line1`), the correct and intentional target is fully localized `爪印` branding — no `PawWork` prefix. Do NOT flag these strings as missing the first-occurrence `PawWork 爪印` rule in future reviews.

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 211
File: packages/opencode/src/provider/models.ts:113-179
Timestamp: 2026-04-24T06:50:02.712Z
Learning: In Astro-Han/pawwork (`packages/opencode/src/provider/models.ts`), `PublishModel` and `PublishProvider` intentionally duplicate fields from `Model` and `Provider` with looser optionality. The split is a deliberate behavior boundary: `PublishModel`/`PublishProvider` (with `.passthrough()`) are used for lenient publish-time validation of incoming catalogs, while `Model`/`Provider` are used for strict runtime normalization. Do not flag this duplication as a maintenance burden or suggest extracting a shared base schema — the explicit separation is intentional and tied to the models-refresh reliability path introduced in PR `#211`.

📚 Learning: 2026-04-21T16:00:44.910Z

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 102
File: packages/opencode/src/config/model-id.ts:9-11
Timestamp: 2026-04-21T16:00:44.910Z
Learning: In Astro-Han/pawwork (`packages/opencode/src/config/model-id.ts`), `ConfigModelID` uses a regex that requires a non-empty provider segment and a non-empty model segment separated by `/`, but intentionally allows additional slashes within the model segment. This is because `Provider.parseModel` supports model IDs like `synthetic/hf:zai-org/GLM-4.7`. Do not flag the permissive slash handling as a bug.

Applied to files:

• packages/opencode/src/plugin/codex.ts

📚 Learning: 2026-04-24T06:50:02.712Z

Learnt from: Astro-Han
Repo: Astro-Han/pawwork PR: 211
File: packages/opencode/src/provider/models.ts:113-179
Timestamp: 2026-04-24T06:50:02.712Z
Learning: In Astro-Han/pawwork (`packages/opencode/src/provider/models.ts`), `PublishModel` and `PublishProvider` intentionally duplicate fields from `Model` and `Provider` with looser optionality. The split is a deliberate behavior boundary: `PublishModel`/`PublishProvider` (with `.passthrough()`) are used for lenient publish-time validation of incoming catalogs, while `Model`/`Provider` are used for strict runtime normalization. Do not flag this duplication as a maintenance burden or suggest extracting a shared base schema — the explicit separation is intentional and tied to the models-refresh reliability path introduced in PR `#211`.

Applied to files:

• packages/opencode/src/plugin/codex.ts