You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Surely there must be a step somewhere where I can provide my API key? The README.md just says to run the npm command and there's "zero configuration" from there. How could that be? Is OpenAI providing this service for free?
In the OP's description they mention OPENAI_API_KEY because it's only in the Non‑interactive / CI mode section. Should we have that in our environment anyway?
system
⚠️ OpenAI rejected the request (request ID: req_a057493e36bb3dda8a2fe4646b7d4cb0): 400 Your organization must be verified to generate reasoning summaries. Please go to:
https://platform.openai.com/settings/organization/general and click on Verify Organization.. Please verify your settings and try again.
So just a thought — the default model used by the CLI is o4-mini, which I think might not be fully rolled out to everyone yet. If your API key doesn’t have access to that model, that could explain the rejection error you’re seeing.
You might want to try running the /model command in the CLI and picking something like gpt-4.5 instead — basically any model you know you have access to — and see if that helps.
Not totally sure that’s the issue, but worth trying! Let me know if that works for you.
Activity
LuciferMornens commentedon Apr 16, 2025
Running into this too, and have access to all models.
shobhitic commentedon Apr 16, 2025
Ran into this exact issue
ndisalvio3 commentedon Apr 16, 2025
Can confirm
maheshrijal commentedon Apr 16, 2025
++ Same issue
adamjgrant commentedon Apr 16, 2025
Surely there must be a step somewhere where I can provide my API key? The README.md just says to run the
npmcommand and there's "zero configuration" from there. How could that be? Is OpenAI providing this service for free?In the OP's description they mention
OPENAI_API_KEYbecause it's only in the Non‑interactive / CI mode section. Should we have that in our environment anyway?I have that but still get this result.
justinechang39 commentedon Apr 16, 2025
same
rasdani commentedon Apr 16, 2025
same
MadcowD commentedon Apr 16, 2025
as well
johanbaath commentedon Apr 16, 2025
Happening here as well, maybe still rolling out? I'm on tier 5 and have access via the API and playground.
DhrubaPatra commentedon Apr 16, 2025
same pinch.
bradennapier commentedon Apr 16, 2025
samesies! <3 super pumepd though!
EverStarck commentedon Apr 16, 2025
wrong issue, but just run
codexon the workdir you want, ex:cd code/react/foo; codexMadcowD commentedon Apr 16, 2025
This is the issue actually:
https://platform.openai.com/settings/organization/general
I made a PR to fix this. #23
leandroz commentedon Apr 16, 2025
Same problem here!
cruffinoni commentedon Apr 16, 2025
Hey! 👋
So just a thought — the default model used by the CLI is o4-mini, which I think might not be fully rolled out to everyone yet. If your API key doesn’t have access to that model, that could explain the rejection error you’re seeing.
You might want to try running the /model command in the CLI and picking something like gpt-4.5 instead — basically any model you know you have access to — and see if that helps.
Not totally sure that’s the issue, but worth trying! Let me know if that works for you.
22 remaining items
adityamcodes commentedon Apr 16, 2025
anyone figure out how to get reasoning level to work?
tibo-openai commentedon Apr 16, 2025
Fix was fixed earlier today, please open new issues for other things and thanks for being patient!
kohl00 commentedon Apr 16, 2025
same only the o4-mini-[date-slug] works for me!
docs(changelog): note clipboard image paste support and auto-close #10
Strengthen linker runtime verification
feat(orchestrator): Phase 3 crate skeleton + types + trait stubs
fix(tui): keep thread ops non-fatal when the app-server request fails
fix(tui): keep thread ops non-fatal when the app-server request fails
fix(tui): keep thread ops non-fatal when the app-server request fails
fix(tui): keep thread ops non-fatal when the app-server request fails
fix(tui): keep thread ops non-fatal when the app-server request fails
Repo health ratchet gates, PathUri migration epic, offline changelog …
fix(rig-bridge): tool-call state machine + custom tool round-trip
Compaction V2: 時系列注記で最新の message を示し、開始手順を繰り返さないよう伝える