Support codex model_provider #7045
Replies: 7 comments
|
seems to work for me. |
|
Can you maybe help me reproduce the issue locally? |
|
you mean you can use models via portkey in t3code? |
|
could be, that the error I am seeing is just a weird behavior of portkey to signal missing auth. I have a suspicion, that portkey can deduce the correct parameters depending on the model configuration. When the env var is not correctly handed down, then the auth on portkey fails and it cannot fetch the config, thus falling back on requiring the headers. This should probably be solved first, so we are sure, that t3code handles env_var #317 Repro would require a working portkey instance |
|
update: I tried to hard-code my API key in experimental_bearer_token = "..."and http_headers = { "x-portkey-api-key" = "..." }I confirmed:
|
|
seems to be working for me. |
|
Hey did anyone of you find a solution I still not able to run t3code it keeps saying MISSING AZURE_API_KEY |
Uh oh!
There was an error while loading. Please reload this page.
Currently t3code does not support
model_providersfor codex. When I try sending a prompt, I getThese headers are sent by the codex cli.
Environment
OS: Linux (Arch)
t3code version: 0.0.10
Codex CLI version: 0.114.0
Custom provider: Portkey (model_provider = "portkey" in ~/.codex/config.toml)
Codex CLI config (working standalone)
Running codex directly from the terminal works without issues.
All reactions