⌘K
Jacob Paris There doesn't appear to be a systemic issue with the keys (low 401 rate and I can successfully follow your steps) Evidence points to your API key being rejected. The thing to focus on here is the cURL request, since that eliminates anything weird Codex could be doing You will get a 401 if that $V0_API_KEY variable is undefined, in case your export V0_API_KEY command executed in a different environment and the variable didn't carry over to when you ran your curl command, so make sure you test them back to back I'll check with the v0 team to see if we have any better resources for debugging this
loai Hi Jacob, Thanks again for following up — I finally managed to get the Vercel key itself working, but I’ve run into a second, CLI-specific problem that’s preventing me from switching my default provider back to OpenAI. Where things stand now Step Result 1. curl with V0_API_KEY ✅ returns 200 (v0-1.5-md) — so the key & billing are good. 2. codex --provider vercel … after codex auth login vercel ✅ works (no more 401). 3. codex config set provider openai from the shell ❌ CLI prints its banner, drops into the interactive REPL, then ignores the config command. 4. `codex config show head` ❌ same bann
William I couldn't get it to work too. I followed the v0 docs and have the provider vercel added in config.json , and then I have V0_API_KEY in env along side OPENAI_API_KEY (which seems to be the cause of the issue) curl with V0_API_KEY returns 200 as well I think it is an upstream issue reported in the codex repo: github.com/openai/codex/issues/987 and the issue seems to be related to being logged in with openai keys and then trying to switch to other providers.
Okeul855 1337 I'm truly desperate. I tried again, but it's still not working. V0 said there's a high chance the issue is caused by me doing 3D development, but I don't know how to do 3D development at all — I don't even know how to create anything in 3D.
Pauline P. Narvas Hi, Okeul! Welcome to the Vercel Community. I'm sorry to hear that you've been having issues with a runtime error in v0. I recommend checking out the following resources which may help you debug: community.vercel.com/t/become-a-v0-expert/5981 We also have other members who managed to get a solution to similar errors which may be helpful: community.vercel.com/search?q=runtime%20error%20status:solved%20%23v0
Pauline P. Narvas Hi, Nadia! Welcome to the Vercel Community. Hopefully this post helps: community.vercel.com/t/bidirectional-git-sync-for-v0-premium-users-is-now-in-beta/11176
Nadia Hi Pauline, thanks for the reply and sharing this. I think this actually might mean there's an issue (or I'm still not understanding how it works) as in the announcement it says "You can connect your chat to GitHub to either main or another branch and every new generation will be synced as a new commit" - but this hasn't been my experience with the feature as described in my message! It's what I thought it should do but the number of commits generated definitely don't match if this is actually working in this manner.
Jacob Paris Hey, thanks for digging into this Are you saying you have a postcss.config.js file in v0 that's not being included when you deploy? Or that after sending prompts, sometimes v0 deletes the postcss.config.js file, and in that state it still works in the preview but breaks when deployed?
Aryan384 so when you give a prompt to the V0 about chainging UI in the project sometimes it deletes the postcss config file and then if this file doesnt include in the project VERCEL will deploy it without it and it will only show the RAW HTML The thing about preview is V0 uses DEVELOPMENT SERVER like (vite dev, next dev, npm run dev) that automatically compiles PostCSS, Tailwind, or other assets and that is why you dont have any problem with preview. and then in the other side VERCEL doesnt know how to compile without postcss config file and it runs wihtout it because its not an error and then ignores
