fix: when using codex sub, send the custom agent prompts as a separate developer message (previously sent as user message but api allows for instructions AND developer messages)#11667
Conversation
…e developer message (previously sent as user message but api allows for instructions AND developer messages)
|
Thanks for the credit for finding the issue, but I think with this new solution OAuth Codex behavior is still different from non-OAuth Codex: OAuth Codex path
Non-OAuth Codex (Zen/opencode)
Resulting behavior:
So behavior still differs (append vs replace). Assumning parity is desired, we likely need to either:
Also |
|
yeah this is expected from what openai told me. If you are using a codex sub the instructions field should always be that codex prompt and then anything custom should be sent as a developer message (system message) separately If you arent using a codex sub the all that instructions stuff is moot |
|
does that make sense? Am i missing something? |
|
I might be missing something. If OpenAI recommends PROMPT_CODEX for the Codex model, why only enforce it for OAuth Codex? Why not apply the same rule to all Codex instances (including Zen/non‑OAuth)? Right now behavior differs:
Is this intentional? |
|
sorry it is a requirement for oauth flow thats what im saying |
|
yes this is intentional (it’s a requirement from them they asked me to do) and its only for the codex subscription |
|
Oh that's interesting, thanks for clarifying. I guess that makes it more difficult to use oauth codex for custom agents, since there is a baked in default that we can't remove. |
…e developer message (previously sent as user message but api allows for instructions AND developer messages) (anomalyco#11667) Co-authored-by: Carlos <carloscanas942@gmail.com>
…e developer message (previously sent as user message but api allows for instructions AND developer messages) (anomalyco#11667) Co-authored-by: Carlos <carloscanas942@gmail.com>
…e developer message (previously sent as user message but api allows for instructions AND developer messages) (anomalyco#11667) Co-authored-by: Carlos <carloscanas942@gmail.com>
fixes: #11163
credit to @CarlosCommits for finding