Repository navigation
Fix invalid input[].id values containing colons during /review #9360
Description
What version of Codex is running?
codex-cli 0.86.0
What subscription do you have?
Running gpt-5.2-codex 2026-01-14 on Microsoft Foundry
Which model were you using?
gpt-5.2-codex
What platform is your computer?
Darwin 24.5.0 arm64 arm
What terminal emulator and version are you using (if applicable)?
zsh
What issue are you seeing?
Running /review in Codex CLI after reviewing a PR against main fails with an API validation error.
Full error message (PII redacted):
{
"error": {
"message": "Invalid 'input[3].id': 'review:rollout:user'. Expected an ID that contains letters, numbers, underscores, or dashes, but this value contained additional characters.",
"type": "invalid_request_error",
"param": "input[3].id",
"code": "invalid_value"
}
}
The error indicates that Codex CLI is sending an input[].id containing colons (:), which are rejected by the OpenAI API validator.
What steps can reproduce the bug?
- Open a repository with an open pull request targeting main
- Run Codex CLI
- Execute /review to review the PR
- The initial review seems to work
- Try to ask follow up questions.
- Codex CLI constructs a multi-input request to the OpenAI API
- The request fails with an invalid_request_error due to an invalid input[].idObserved invalid ID value:
review:rollout:user
No custom configuration or non-default options are required to reproduce this.
Session ID, token usage, and context window usage were not exposed by the CLI at the time of failure.
What is the expected behavior?
What is the expected behavior?
Codex CLI should generate API-compatible input[].id values.
Internally generated IDs should only contain characters allowed by the OpenAI API:
[a-zA-Z0-9_-]
The /review command should complete successfully without failing API validation.
Additional information
- This appears to be a client-side ID formatting issue rather than a user configuration problem.
- The failure occurs with standard /review usage.
- A simple normalization step (e.g. replacing non-allowed characters with _ or -) would likely resolve the issue.
- Happy to test a fix or provide additional logs if needed.
Activity
Fix invalid input error on Azure endpoint
etraut-openai commentedon Jan 16, 2026
Thanks for the bug report. I'm guessing that this problem is specific to the Azure endpoint. We haven't heard of any similar reports for OpenAI-hosted models.
We should be able to work around the Azure limitation. I have a PR that's up for review.
Fix invalid input error on Azure endpoint (#9387)
etraut-openai commentedon Jan 19, 2026
This should be fixed in the next release.
Fix invalid input error on Azure endpoint (openai#9387)
doggy8088 commentedon Jan 25, 2026
@etraut-openai which version?
etraut-openai commentedon Jan 25, 2026
@doggy8088, this should have been in 0.89. Are you still seeing it?
mohamad1014 commentedon Jan 27, 2026
@etraut-openai Yes I just had this error message
■ { "error": { "message": "Invalid 'input[326].id': 'review_rollout_user'. Expected an ID that begins with 'msg'.", "type": "invalid_request_error", "param": "input[326].id", "code": "invalid_value" } }etraut-openai commentedon Jan 27, 2026
@mohamad1014, are you using an Azure endpoint? If you see this again, please use the
/feedbackcommand to upload your logs and post the thread ID here.codeofdusk commentedon Mar 11, 2026
@etraut-openai I'm getting a similar error to @mohamad1014.
Thread ID:
019cdf30-b38f-7551-8bf2-d6d4e420f2b7.etraut-openai commentedon Mar 11, 2026
@codeofdusk, are you using an Azure-hosted model? If so, please report this to the Azure folks as well. If you don't, they won't be aware of the problem.
eshgovil commentedon Mar 13, 2026
I'm still getting this issue, using GPT 5.4 via Azure and
codex-cli 0.114.0. Who are the Azure folks to report to?tcx4c70 commentedon Mar 17, 2026
Hi, I add a fix commit in my own fork (just add a 'msg_' prefix) and it works in my machine. But I don't have permission to open a PR for the repo. @etraut-openai , could you please help to add the fix commit to the repo?
etraut-openai commentedon Mar 17, 2026
@tcx4c70, I don't think this is a bug in the Codex harness. We wouldn't want to make changes to work around a temporary bug in Azure's endpoint. Please report the issue to Azure if you haven't already done so.
dews commentedon Apr 7, 2026
I'm still seeing the same issue in v0.118.0 with Azure GPT-5.4. I don't understand the root cause, but I never encounter this bug when using GitHub Copilot.
myn commentedon Apr 9, 2026
Can confirm I am also experiencing the same behavior with v.118.0 and Azure Hosted GPT-5.4
behrendtio commentedon May 11, 2026
Same here with GPT 5.5 on Azure Foundry
cammoore54 commentedon May 20, 2026
I am getting this on v0.132.0 with GPT5.5 on Azure Foundry also
Fix invalid input error on Azure endpoint (openai#9387)