Skip to content

v0.3.4 — Config allowlist: gpt-5.5 or gpt-5.4 only

Choose a tag to compare

View all tags
@AmirShayegh AmirShayegh released this 23 Apr 23:03
v0.3.4
d48947d

Summary

`.reviewbridge.json` now rejects any `"model"` value other than `gpt-5.5` or `gpt-5.4`. Unknown values produce a clear validation error at load time:

```
CONFIG_ERROR: Unsupported model "gpt-5.1-codex-mini". Supported values: gpt-5.5, gpt-5.4.
```

MCP tool schemas and the CLI `--model` flag remain permissive so Claude Code can experiment per call — the allowlist applies only to persisted config.

Why

The previous permissive `z.string()` on config.model meant anything could silently run in the background (`gpt-5.3-codex`, `gpt-5.2-codex`, `gpt-5.1-codex-mini`, etc.). Only the current flagship (`gpt-5.5`) and one fallback (`gpt-5.4`) are supported. Older Codex variants and mini models are out of scope and will be rejected at config load. See lessons L-006 and L-007 for the rationale.

Changes

  • `src/config/types.ts`: new `SUPPORTED_MODELS` constant; `model` field gains a `superRefine` against the allowlist
  • 2 new tests — unsupported rejection with descriptive message, both supported models accepted
  • README documents the allowlist on `.reviewbridge.json`
  • 489 tests passing (was 487)

Breaking changes (minor)

If you were running with a non-supported `"model"` in `.reviewbridge.json`, the bridge will now fail config load with a clear error. Fix: set `"model": "gpt-5.5"` or `"gpt-5.4"`, or omit the field to use the default (`gpt-5.5`).

Upgrade

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

Assets 2
Loading