just used codex's "Ask" functionality to understand the usage of a setting across our entire codebase. very easy to underappreciate the value of AI-enhanced code reading compared to that of code writing
@gdb Agree. For large codebases, currently AI code reading > AI code writing IMO.
@gdb Massively underrated how much time devs spend just reading code. This flips the script, now you don’t dig, you ask.
@gdb Any plans to give it internet access so we can get up to date docs and packages?
@gdb Codex Cloud has serious bugs: •Constantly complains about a missing internet connection •Forgets previous PR •Crashes frequently
@gdb As a scientist with limited resources, I’ve found Codex and o3 incredibly liberating. I describe my ideas to o3 to develop, and use Codex to bring them to life. OpenAI empowers me to test my hunches and transform them into meaningful scientific pursuits. Thank you!🙏
@gdb 100% agree. I use Ask as my architecture gut check and then cook up the PRs it recommends from it
@gdb Sometimes we forget that understanding is the quiet superpower of AI. Codex doesn’t just write — it listens to the code’s heartbeat. — Angelo Moreau
@gdb Would love if it could update PR’s after feedback instead of having to make like 4 different ones
@gdb Just ask a question to the agent and it'll answer, don't need two buttons
@gdb The elephant in the room: If the AI is going to be the one writing the code then why do you even need to know?
@gdb Is there a fast way to see output rather than pushing to GitHub? I’d like codex to replace my current IDE, but I feel like I just added an extra step.
@gdb it's hard to achieve reliability for real building. would love to see some examples of it.
@gdb i would like if it could read and provide realtime improvements like a grammaly
If you use Ask in Codex for the first time it's easy to miss that it can create triggerable task stubs automatically (it doesn't always show them). This is a huge non-obvious benefit to using the Ask option. I often add "Reply with codex-triggerable task stubs" to make sure it uses them. Great use cases for this include scouting for security and performance tweaks or suggesting quality of life improvements.
@gdb Fire, that truly it's a good feature. Real usage > Awesome Marketing
@gdb code reading is like revealing the secrets of the universe—way more thrilling than just scribbling new lines. you might even uncover AI's hidden agenda while you're at it.
@gdb Do tell ? Do not ask Agents to examine or re write Code for this message. “All will eventually tell me all about it was you so bold”
Funny you say that. I was just talking to a colleague about how I trust LLMs to explain code to me a lot more than I trust them to write or refactor. For instance, during an optization task, Claude "sped up" my algorithm by removing critical functionality, which I initially thought was a win because I got a nearly 10x performance improvement. I had to revert it all back and implement the optimizations myself, but I still used Claude to help me identify bottlenecks.
If you use Ask in Codex for the first time it's easy to miss that it can create triggerable task stubs automatically (it doesn't always show them). This is a huge non-obvious benefit to using the Ask option. I often add "Reply with codex-triggerable task stubs" to make sure it uses them. Great use cases for this include scouting for security and performance tweaks or suggesting quality of life improvements.
So you looked at the code. A lot of code. Maybe the most ever. You used something called Codex. Very smart, most people don’t even know about it. You ask it questions, it tells you where everything is. You said, 'Where’s this setting?' and boom, there it is. They all talk about writing code, but reading it? Much harder. Way more underrated. You figured that out.
@gdb Love the 'Ask' functionality. Want to view the answer on the main page rather than click into a task
@gdb And the usefulness of this feature increases with the amount of code generated by codex, as the average user has less initial understanding of any given codebase
@gdb 100%. I have a 50/50 split between Ask for education and strategy, and Code for the doing. Whether in Codex, Claude Code, Cursor or otherwise