Skip to content

v0.3.5 — Revert config model allowlist

Choose a tag to compare

View all tags
@AmirShayegh AmirShayegh released this 23 Apr 23:15
v0.3.5
3439091

Summary

Reverts the `.reviewbridge.json` `"model"` allowlist introduced in v0.3.4. The field is permissive again — any non-empty string is accepted and forwarded to Codex as-is.

Why

0.3.4 rejected any `model` value other than `gpt-5.5` or `gpt-5.4` at config parse time. That crossed the line from curating our recommendations into blocking user choice. Our position: don't advertise older Codex variants or mini models, but don't gate users who explicitly pick them either. Lesson L-006 captures the corrected policy.

What stays

  • `gpt-5.5` remains the default model
  • README still documents only `gpt-5.5` (current flagship) and `gpt-5.4` (fallback for ChatGPT-tier rollout gaps)
  • Error-message tips still point at `gpt-5.5` / `gpt-5.4`
  • The `RECOMMENDED_MODELS` constant (formerly `SUPPORTED_MODELS`) is retained as a documentation/tip-sourcing reference

What changes vs 0.3.4

  • `config.model` schema: back to `z.string().default('gpt-5.5')` — no superRefine, no rejection
  • README: clarifies that config, MCP param, and CLI flag all accept any string
  • 2 rejection tests removed; 1 permissive acceptance test added (488 total vs 489 in 0.3.4)

Upgrade

```bash
claude mcp remove codex-bridge
claude mcp add codex-bridge -- npx -y codex-claude-bridge@latest
```

Anyone who hit the 0.3.4 rejection error with a non-allowlisted `"model"` value will find that config now loads cleanly again.

Assets 2
Loading