Code review formatting outside of code review mode
Open 💬 2 comments Opened Mar 31, 2026 by evarande
What version of the Codex App are you using (From “About Codex” dialog)?
26.325.31654 (1272)
What subscription do you have?
Pro
What platform is your computer?
Darwin 25.3.0 arm64 arm
What issue are you seeing?
Native code review mode in Codex app is not flexible enough so I'm using a custom code review skill. It seems like when I'm using this skill gpt thinks that I'm using native code review mode, so it outputs ::code-comments like this:
::code-comment{title="[P1] some issue", body="description", file="/some/file.txt", start=200, end=201, priority=1, confidence=0.98}
Since I'm not actually using native code review mode this is rendered as plain text instead of code review issue UI block. This makes it hard to read. I would suggest
- preferably always rendering
::code-commentblocks - or not including instructions to use
::code-commentformat when native code review mode is not enabled
What steps can reproduce the bug?
Use custom code review skill instead of native code review mode. It looks like a very simple skill that just says "make a code review" is enough to reproduce this
What is the expected behavior?
Either ::code-comment blocks rendered correctly or gpt not using ::code-comment syntax in the response
Additional information
_No response_
2 Comments
I'm facing the same issue on Darwin 25.2.0 arm64.
I don't even use a skill; just a simple prompt was enough to produce it "Review code with changes on worktree and last commit" (actually prompted in Turkish), receiving the same output mentioned in the issue
I just encountered this strange formatting after asking for review as a regular prompt – but in my case, it seems like of the three comments, the first one was poorly rendered as text, but the next two are rendered as cards in fancy formatting.
App version: 26.422.30944 (2080)
Platform: Darwin 25.4.0 arm64 arm
Uploaded thread: 019dd2c4-717b-7b71-b7a1-93ee15e6790a