Pulse
What X is shipping with agents right now.
New skills, workflows, and tricks from people building with Claude Code, Codex, and Cursor. Our bots read X, keep the useful posts, and sum each one up in a line.
- posts tagged #codex
- 5
- posts tagged #codex
- builders
- 5
- builders
- topics
- 14
- topics
OpenAI Developers@OpenAIDevs
OpenAI's playbook for pointing Codex at maintenance: it finds dead code and stale experiments, checks them against production telemetry, and drafts cleanup PRs.
Here’s how our engineers use Codex at OpenAI to dig through our codebase, find what needs attention, and chip away at the maintenance backlog: https://developers.openai.com/blog/maintaining-software-with-the-gpt-6-family
Ibragim@ibragim_bad
Your old ~/.claude and ~/.codex sessions are an eval set: your corrections become test cases for benchmarking models, harnesses and plugins.
I had 1,270 agent sessions sitting in ~/.claude, ~/.codex and ~/.pi that’s an eval set: my corrections to the agent are the test cases turned it into the my-mini-benchmark. now I test any model, harness or plugin on my own tasks guide + the skill 👇 https://t.co/oaRtwFJTxT
aditya@adxtyahq
A 40-agents-a-day setup: Claude Code on Opus plans from the Linear ticket, then work fans out across Claude, Codex and a big VM.
i run around 40 AI agents a day, 24/7. here's how i do it. my setup: 3 Claude $200 accounts 1 Codex $100 account Grok Bot a CPU VM with 128 GB RAM and 32 cores my workflow: 1. planning: Claude Code with Opus 5.5 breaks down the Linear ticket, reasons through the architecture, https://t.co/5k7FQTqP2r
Theo - t3.gg@theo
Theo flags that Codex still omits the current model name from its system prompt, so the agent can't tell which model it is.
It is so stupid that Codex STILL does not include the current model in the system prompt. Your agent has no idea what it is beyond "based on GPT-6". I've complained about this for a year straight and they won't fix it for no good reason. https://t.co/PepE5yeaZH
Mitchell Hashimoto@mitchellh
OSC7501 (deterministic agent status for terminals) is spreading: Kitty, Grok Build and Codex support it, so tools can drop status heuristics.
OSC7501 adoption updates: Kitty implements and displays in the tab title. Grok Build shipped support and Codex merged. In less than a week I think we're nearly at a place where the entire industry can drop their heuristics and get deterministic status updates.