#9954 don't work

Resolved 💬 9 comments Opened Jan 27, 2026 by cvjxendra Closed Jan 28, 2026

💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

codex-cli 0.92.0

What subscription do you have?

plus

Which model were you using?

gpt-5.2-high

What platform is your computer?

WSL on Windows x64

What terminal emulator and version are you using (if applicable)?

_No response_

What issue are you seeing?

Wrong message, because I already changed my config.toml:

⚠ Under-development features enabled: collab, collaboration_modes. Under-development features are incomplete and may
behave unpredictably. To suppress this warning, set suppress_unstable_features_warning = true in /home/cvj/.codex/config.toml

What steps can reproduce the bug?

Uploaded thread: 019c00ea-fedb-7061-8590-6912fcf8fae7

What is the expected behavior?

Don't display the warning.

Additional information

_No response_

View original on GitHub ↗

9 Comments

etraut-openai contributor · 5 months ago

Can you say more about what's not working?

The suppress_unstable_features_warning config key suppresses the warning that you cited above. Add suppress_unstable_features_warning = true if you don't want to see this.

I just confirmed that it's working for me.

rustanacexd · 5 months ago

same its not working for me.

etraut-openai contributor · 5 months ago

@rustanacexd, can you say more? Perhaps you can share your config.toml file?

bawanyadam · 5 months ago

@etraut-openai hey there, likewise, and hopefully this adds more context: I've added the suppress flag (at true) to my config.toml and it still shows the warning message.

here's the block of my config that is relevant:

[notice]  
hide_full_access_warning = true
hide_gpt5_1_migration_prompt = true
"hide_gpt-5.1-codex-max_migration_prompt" = true
suppress_unstable_features_warning = true

[notice.model_migrations]  
"gpt-5.2" = "gpt-5.2-codex"
"gpt-5.1-codex-mini" = "gpt-5.2-codex"

[features]
collaboration_modes = true
shell_snapshot = true
web_search_request = true
steer = true
unified_exec = true
collab = true

save/reload codex and the message still shows. I imagine this is what the other folks above replying are referring to as well.

etraut-openai contributor · 5 months ago

suppress_unstable_features_warning is a top-level key. It looks like you've placed it under the [notice] section. It won't have any effect there. Move it to the top of the file so it's not under any heading, and it should work.

bawanyadam · 5 months ago

suppress_unstable_features_warning is a top-level key. It looks like you've placed it under the [notice] section. It won't have any effect there. Move it to the top of the file so it's not under any heading, and it should work.

appreciate the quick reply. works as intended.

cvjxendra · 5 months ago

Top level? I will try. This should have been better documented.

Em qua., 28 de jan. de 2026, 03:58, Eric Traut @.***>
escreveu:

etraut-openai left a comment (openai/codex#10013) <https://github.com/openai/codex/issues/10013#issuecomment-3809346361> suppress_unstable_features_warning is a top-level key. It looks like you've placed it under the [notice] section. It won't have any effect there. Move it to the top of the file so it's not under any heading, and it should work. — Reply to this email directly, view it on GitHub <https://github.com/openai/codex/issues/10013#issuecomment-3809346361>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXGBWKTF57ZEEJE3ESNKLAT4JBMXXAVCNFSM6AAAAACTCSBDEOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTQMBZGM2DMMZWGE> . You are receiving this because you authored the thread.Message ID: @.***>

etraut-openai contributor · 5 months ago

Documentation for Codex config keys can be found here. Config keys that are scoped include their namespace in the name. For example, otel.log_user_prompt is scoped to the [otel] section of the toml document.

rustanacexd · 5 months ago

ok top level key and it works, but I think this should be obvious from the warning message inside the CLI. just saying. but thank you for the response!