#网友语录 Eric Wang
My rule for any agent config:
Turn on what improves continuity.
Turn off what sprays noise into the session.
The best setup is not the biggest one.
It's the one that stays quiet until it matters.
I'd rather have 5 clean flags than 15 with three conflicting plugins fighting for the model's attention.
My rule for any agent config:
Turn on what improves continuity.
Turn off what sprays noise into the session.
The best setup is not the biggest one.
It's the one that stays quiet until it matters.
I'd rather have 5 clean flags than 15 with three conflicting plugins fighting for the model's attention.
#网友语录 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.
## 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.
#网友语录 mywaiting 人生其实只有三件事：选择路线，踏上征程，承担后果。很多人因为害怕承担后果而不愿做出选择，又或者因为懒惰、迟疑而踯躅不前。
你可以不选择，也可以不行动，但唯独承担后果是躲不掉的。不选择路线，不踏上征程，就必然要承担一直在原地的后果。这个后果是躲不掉的。（其实大家都是转发来转发去。但万一有个人被某一次转发触动了，他可能就会从那天开始变成了另一个人。
你可以不选择，也可以不行动，但唯独承担后果是躲不掉的。不选择路线，不踏上征程，就必然要承担一直在原地的后果。这个后果是躲不掉的。（其实大家都是转发来转发去。但万一有个人被某一次转发触动了，他可能就会从那天开始变成了另一个人。
#网摘 Claude sounds like a person wrote it. ChatGPT sounds like a very capable machine wrote it. Even with tweaking and detailed style instructions, it’s harder to get ChatGPT there. The prose comes out robotic. If you’re producing client-facing content or board materials, you’ll feel this gap right away.
<https://www.smithstephen.com/p/chatgpt-54-is-good-thats-not-the>
<https://www.smithstephen.com/p/chatgpt-54-is-good-thats-not-the>
Smithstephen
ChatGPT 5.4 Is Good. That's Not the Point.
Strong analysis, flat writing, and a model that sometimes lies about finishing its homework.
#网摘 人生可能有的两次觉醒
第一次是弗洛伊德
你明白了，痛苦、自卑、讨好与不安，往往来自童年的匮乏与创伤。你从此不再责备自己。
第二次是阿德勒
你明白了，纵然过去塑造了现在的你，但真正决定自己将来的，是当下的选择。你不再抱怨命运与现实的不公，不再随波逐流，而开始有意识地审视自己的每一个决定。
第一次是弗洛伊德
你明白了，痛苦、自卑、讨好与不安，往往来自童年的匮乏与创伤。你从此不再责备自己。
第二次是阿德勒
你明白了，纵然过去塑造了现在的你，但真正决定自己将来的，是当下的选择。你不再抱怨命运与现实的不公，不再随波逐流，而开始有意识地审视自己的每一个决定。
Ctrl+Alt+KP 1 这里KP是哪个键？
## Claude responded: KP 是 Keypad，就是键盘右边的数字小键盘（NumPad）上的数字键。
KP 是 Keypad，就是键盘右边的数字小键盘（NumPad）上的数字键。
所以
如果你的键盘没有小键盘（比如笔记本），建议直接设成
## Claude responded: KP 是 Keypad，就是键盘右边的数字小键盘（NumPad）上的数字键。
KP 是 Keypad，就是键盘右边的数字小键盘（NumPad）上的数字键。
所以
Ctrl+Alt+KP_1 就是 Ctrl + Alt + 小键盘的1，不是主键盘行上方的数字1。如果你的键盘没有小键盘（比如笔记本），建议直接设成
Ctrl+Alt+1（主键盘数字）就好。#网摘#网摘
One could say in the first quarter-century of my life, that while I was always fascinated by programming, I could never overcome the guilt of not really knowing whether the tool I am building right now isn’t already superceded by some much better implementation someone else has already written 30 or 40 years ago; I could write a TSV-aware search and replace, or I could find out about
You need to reinvent a couple of wheels to get to the edge of what we know about wheel-making, not a thousand wheels, and not zero; probably four or five is sufficient in most domains, maybe closer to twenty or thirty in the most epistemically rigorous and developed fields like mathematics or computer science. Each wheel you reinvent, and every directed question you ask along the way, will propel you faster to the true frontier than that same amount of time spend in idle study, or even five times that amount.
— Andrew Quinn, footnote on Replacing a 3 GB SQLite database with a 10 MB FST (finite state transducer) binary
One could say in the first quarter-century of my life, that while I was always fascinated by programming, I could never overcome the guilt of not really knowing whether the tool I am building right now isn’t already superceded by some much better implementation someone else has already written 30 or 40 years ago; I could write a TSV-aware search and replace, or I could find out about
awk and solve that entire class of problems in one fell swoop, for example. My central conceit is that this is a trap.You need to reinvent a couple of wheels to get to the edge of what we know about wheel-making, not a thousand wheels, and not zero; probably four or five is sufficient in most domains, maybe closer to twenty or thirty in the most epistemically rigorous and developed fields like mathematics or computer science. Each wheel you reinvent, and every directed question you ask along the way, will propel you faster to the true frontier than that same amount of time spend in idle study, or even five times that amount.
— Andrew Quinn, footnote on Replacing a 3 GB SQLite database with a 10 MB FST (finite state transducer) binary
