Layered approach for configs

What feature would you like to see?

I am trying to define some project specific MCP servers which I don't want to include in my global ~/.codex/config.toml.

I was assuming that you could define a .codex/config.toml and include it there, so it would be combined with your global config. Similar to how an AGENT.md or skills work.

This is however not the case.

Also (more like a bug report), I can't point to it using the --config argument:

❯ codex --config ~/.codex/config.toml
Error: Invalid override (missing '='): /Users/xxxxx/.codex/config.toml

Additional information

❯ codex --version
codex-cli 0.77.0