Files
hermes-webui/api
nesquena-hermes ec403fa3cf fix(routes): persist openai-codex provider unconditionally on stale-session repair (Opus stage-303 follow-up)
Opus advisor on stage-303 (#1738 verification Q4) flagged that the
catalog-coverage branch produces a redundant repair-write per chat-start
when the active Codex default is itself slash-prefixed: the repair sets
`provider_context = None`, the next chat-start hits the same branch
because `requested_provider is None` again, and the repair fires repeatedly.

In practice Codex `default_model` is always a bare `gpt-...` ID from the
Codex catalog, so this is theoretical. But once we've decided this session
belongs to Codex, we should persist that decision. Drop the conditional
catalog-coverage check and unconditionally attach `raw_active_provider`
("openai-codex") on this repair path. The shape is now stable across
resolutions.

Absorb-in-release per Opus stage-303 verdict — small, defensive, ≤10 LOC.
2026-05-06 15:18:34 +00:00
..
2026-04-29 19:54:07 -07:00