Eight Codex Config Tweaks That Fix the 'Worse Than Doubao' Problem
Teams burning budget on AI coding tools often blame the model when the real bottleneck is a handful of default settings that cripple throughput. These eight changes cost nothing and can flip a tool from dead weight to a daily driver.
After rolling out $200 Codex Pro seats to an entire team, one group reported the tool was useless while another was flying through work. A side-by-side settings comparison revealed the defaults were the bottleneck. The fixes range from granting full file-access permissions and switching the interaction tone to "Pragmatic" to adopting Andrej Karpathy's open-source custom instructions for agent behavior.
Other changes address workflow friction directly: switching the editor follow-up mode from "Queue" to "Guide" allows mid-task corrections, and session-management tricks let a frozen context continue in a fresh dialog via a copied session ID. Enabling full computer control for Chrome and arbitrary apps turns Codex into a desktop operator rather than just a code editor.
A persistent "Reconnecting 5/5" error traces back to WebSocket incompatibility with local proxies. The fix involves a prompt that rewrites the config to force an HTTP-based provider and, if needed, detects and injects the correct proxy port into the environment file.
Identical AI tooling produces wildly asymmetric productivity inside the same team, and the delta often lives in configuration defaults — not model quality or developer skill.
Karpathy's public complaints about agent behavior have been operationalized into a copy-paste ruleset that meaningfully improves output; community-sourced system prompts are becoming a practical layer of tool customization.
The WebSocket reconnection bug is a concrete example of how AI coding tools still assume a direct network path that corporate proxy environments routinely break, and the fix requires the tool to edit its own config.