Skip to content

fix(codex): preserve supported none reasoning effort #116

Description

@drewstone

Reproduction

With CLI Bridge serving Codex CLI 0.146.0, send a chat completion using model: codex/default and effort: none.

The bridge maps none to minimal in codexReasoningEffort. The active Codex model rejects it with HTTP 400: minimal is unsupported; accepted values are none, low, medium, high, xhigh, max.

Expected

The backend should pass a reasoning value accepted by the installed Codex CLI/model, and the model catalog/capabilities should agree with that mapping. In particular, a caller's explicit none must not be rewritten to an unsupported value.

Impact

A real Braid first-run validation of the advertised codex/default route fails before dispatch even though the backend and local subscription are healthy.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions