Route Guardian requests through /responses with identifying headers (#45736)

## What changed

- Replace dedicated Guardian endpoints with `/responses`, sending `x-codex-guardian: reviewer` or `x-codex-guardian: classifier` for eligible Codex backend requests over HTTP and WebSocket.
- Add model-scoped thread headers, recheck backend authentication on each request attempt, and reconnect WebSockets when the applicable headers change.
- Retain `features.guardianv2.free_guardian` for configuration compatibility while removing its routing gate; the backend now controls Guardian billing.

## Testing

Update tests for reviewer and classifier headers, model and authentication scoping, HTTP fallback, WebSocket reuse, and parent-response metadata across retries.

GitOrigin-RevId: 1c2b3c458ab77fb40aae4ee6784f6d827c60e76c
This commit is contained in:
jif authored and copyberry committed 2026-09-15 17:09:11 +00:00
1 parent d4e11a9b97
commit eeded5ba1a
22 files changed
+246 -286

No files matched your search

+1 -1
View File
@@ -1617,7 +1617,7 @@
"type": "boolean"
},
"free_guardian": {
"description": "Route Guardian review and classification through the unmetered Codex endpoints.",
"description": "Legacy setting retained for config compatibility; the backend now controls Guardian billing.",
"type": "boolean"
},
"max_action_tokens": {