Codex keeps reporting an error that isn't actually an error despite Framework MCP and Agents instruction.

Resolved 💬 5 comments Opened Dec 30, 2025 by klipnot Closed Mar 29, 2026

What version of Codex is running?

0.77.0

What subscription do you have?

Business

Which model were you using?

gpt-5.2-codex, gpt-5.1-codex-max

What platform is your computer?

Darwin 25.1.0 arm64 arm

What issue are you seeing?

Codex keeps reporting this error

The new MyComponent is imported as a standalone component in MyModule and used directly in templates, but the component decorator does not declare standalone: true while still using the imports field.

Angular will fail compilation with “imports is only valid on a standalone component” / “component is not standalone” errors, preventing the app from building. Add standalone: true so it can be imported instead of being declared
in an NgModule.

When asking to codex to ask to the Angular MCP what is the default value the property it does

Called angular-cli.search_documentation({"query":"standalone default true Angular 20 decorator default standalone","includeTopContent":true})

└ No results found.

Called angular-cli.get_best_practices({})

└ .... - Must NOT set standalone: true inside Angular decorators. It's the default.

So Angular MCP is clear about this.

But when I start a new chat it completely forgot this rules and continue to report this as an issue.

I've event tried to add the Angular MCP instruction to my AGENTS.MD file Must NOT set standalone: ​​true inside Angular decorators. It's the default in Angular v20+. but it doesn't stop to report it.

Even more troubling, it focuses on this anomaly while ignoring other, genuinely problematic ones.

I'm experiencing this issue with the gpt-5.2-codex and gpt-5.1-codex-max models, regardless of whether the reasoning level is Very High or Medium

What steps can reproduce the bug?

Uploaded thread: 019b6eaa-599e-7c01-b292-2869c52f253e

What is the expected behavior?

Codex needs to stop focusing on problems that aren't really problems and take the time to concentrate on real issues.

Additional information

I'm currently testing the daily use of AI agents for our development teams, so I'm still figuring things out when it comes to setting them up.

It's possible I don't fully understand what I'm doing and that I might make a beginner's mistake (because yes, I definitely am one), so please don't hesitate to tell me if I'm doing something wrong; I won't take it personally!

I use Codex CLI in /review mode and in "What can you tell me about component XXX?" mode, and this problem occurs in both modes.

In /review mode, the error that isn't actually an error is sometimes the only feedback I get, whereas in "What can you tell me about component XXX?" mode, it will also report other anomalies.

This completely defeats the purpose of /review mode for my case.

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗