Check the OpenAI Developer blog
Limited to two replies in a row so appending to second reply.
Make use the slash command /goal
Hi guys I wanted to start this thread to see what everyone is breathing with.
Do you have any cool tips and tricks you don’t see on the web to share with devs in this forum? Something simple but efficient. Not complicated to implement not too tied to a specific project but more something that helps you save some time and tokens.
Here is 1 I thought of sharing:
/.feedback
- AGENTS.md
- README.md
- TEMPLATE.yaml
- /new
- /claimed
- /implemented
Placed in the root of your project, with a note in main agents.md file to do before commit preparation: to review the current session agent experience, identify frictions, problems, failed tools, or unclear instructions, as well as any other notes agent considers important to improve its efficiency, quality and overall work in this project.
Then simply ask your agent time from time to review the folder and improve the workflows and/or its instructions.
I have another one for readme… now basically part of most of my repos. Codex even figured out how to scan outlines on MD files with regex.
One tactic that has helped our team a lot: treat Codex runs like reversible ops loops. Start with a tiny mission card, keep proof for each browser step, and split the closeout into executed, verified, and blocked. It cuts drift fast when you are testing across real surfaces.
Tomorrow marks 60 days of coding with codex, doing practically nothing else night and day.
I had no experience or knowledge on how to code, what clean architecture was, but decades of being an end-user of a multitude of software types really helped me get through…
I’ve been playing with the idea of putting a thread together for folks, that approaches the pitfalls someone with little experience in the field should be aware of before going in.
Simple things that most of you fine folks would probably never consider because of your years of experience…
Like how a simple ‘vibe’ prompt can lead to extensive refactoring down the road and how to use the plan feature as well as general tips to consider when prompting that I’ve picked up while in the trench.
In my mind it’s not so much a ‘tips and tricks’ thread, but something along the lines of - ‘never coded before? - codex makes it easy - here’s what to look out for on your first projects’.
Let me know if you would like me to spend time fleshing that out.
