#网友语录 Eric Wang
## 5 Codex features I'm not turning off.

The default instinct is to enable everything you find.

That's how you end up with context soup: random MCP noise, tools you didn't ask for, a model drowning in its own config.

I run 5 flags. Everything else is off.

Here's the full config for the lazy:

[features]
chronicle = true
goals = true
mentions_v2 = true
prevent_idle_sleep = true
runtime_metrics = true

apps = false
enable_mcp_apps = false
remote_plugin = false
multi_agent_v2 = false
child_agents_md = false

Copy-paste. Adjust after a week. You'll know what to change.

The following is his reasoning:

chronicle = true

Passive memory that builds up across sessions. Codex starts remembering your project shape, your file patterns, your recent decisions.

I stopped re-explaining my repo structure after turning this on. Second session in, it already knew which tests mattered.

Still under development. Already the most interesting thing in the config.

goals = true

This changes how Codex handles multi-step work.

Without it, every session is stateless. You keep repeating the objective.

With goals: "refactor auth flow, update tests, clean imports, ship." The run has a spine. You steer once, it holds.

One flag. Way less babysitting.

mentions_v2 = true

Sounds like UX polish. It's not.

The faster you can point Codex at the right file, skill, or context, the less you explain.

Good agent UX is just reducing explanation tax. This flag cuts mine in half.

If you've ever typed "look at src/auth/..." for the third time in a session, you want this on.

prevent_idle_sleep = true
runtime_metrics = true

One keeps your machine awake during long runs.
The other tells you where Codex gets slow.

Not flashy. Just the flags you notice when they're off. Like when a 40-minute repo audit dies at minute 22 because your Mac took a nap.

runtime_metrics is optional, but if you treat your setup like a workstation, keep it.