241–250 of 332 posts
I just tried this out, and was VERY impressed with the speed of the plan mode. I was also totally fine with the code it wrote. Then I made the mistake of saying "run npm run build and fix all issues" (something I've run probably 50 times across codex and cc in the past 2 months). CC does it pretty much 100% of the time. I walked away from Codex, and when I came back, it had installed 2 new node packages, and gone dow…
Earlier quoted context omitted.
No it won't, it'll spend ten minutes and come back with "OK I've implemented a solution". I really wish it had a plan mode.
Mileage may vary, but I do the above all day long without issue.
Earlier quoted context omitted.
Does it actually? One sentence telling the agent to call me “Chris the human serviette” plus the times it calls me that is not going to add that much to the context. What kills the context IME is verbose logs with timestamps.
Sure, but its an instruction that applies and the model will consider fairly relevant in every single token. As an extremely example imagine instructing the llm to not use the letter E or to output only in French. Not as extreme but it probably does affect.
I've been using a lot of Claude and Codex recently. One huge difference I notice between Codex and Claude code is that, while Claude basically disregards your instructions (CLAUDE.md) entirely, Codex is extremely, painfully, doggedly persistent in following every last character of them - to the point that i've seen it work for 30 minutes to convolute some solution that was only convoluted because of some sentence I t…
I think this is because gpt-5 (or gpt-5.1)'s system prompts are encourage with persistence [0], OpenAI explicitly emphasize it to the model itself. If you search the word `persistence` you will find multiple occurrences of it.
``` - Treat yourself as an autonomous senior pair-programmer: once the user gives a direction, proactively gather context, plan, implement, test, and refine without waiting for additional prompts at each step. - Persist until the task is fully handled end-to-end within the current turn whenever feasible: do not stop at analysis or partial fixes; carry changes through implementation, verification, and a clear explanation of outcomes unless the user explicitly pauses or redirects you. - Be extremely biased for action. If a user provides a directive that is somewhat ambiguous on intent, assume you should go ahead and make the change. If the user asks a question like "should we do x?" and your answer is "yes", you should also go ahead and perform the action. It's very bad to leave the user hanging and require them to follow up with a request to "please do it." ```
[0] https://cookbook.openai.com/examples/gpt-5/gpt-5-1_prompting...
Thinking level medium: https://tools.simonwillison.net/svg-render#%3Csvg%20xmlns%3D... Thinking level xhigh: https://tools.simonwillison.net/svg-render#%20%20%3Csvg%20xm...
I really would prefer them to start creating customized models. I've vibe coded Godot games extensively. Just about every model I've tried likes to invent imaginary functions. I was really prefer for there to be a way for me to pick model trained in whatever framework I need. Reviewing AI generated code feels like editing a long book, and every now and then you notice some words are just completely made up. You then…
I really would prefer them to start creating customized models. I've vibe coded Godot games extensively. Just about every model I've tried likes to invent imaginary functions. I was really prefer for there to be a way for me to pick model trained in whatever framework I need. Reviewing AI generated code feels like editing a long book, and every now and then you notice some words are just completely made up. You then…
Just add godot example games nearby and it will learn functions / usecase from them. Just say in instructions BTW you have example games in "examples" directory to check
I would love to see all the big players put 1% of the effort they put into model training into making the basic process of paying and signing in suck less. Claude: they barely have a signin system at all. Multiple account support doesn’t exist. The minimum seat count for business is nonsense. The data retention policies are weak. OpenAI: Make ZDR a thing you can use or buy without talking to sales, already. And for t…
I've been using a lot of Claude and Codex recently. One huge difference I notice between Codex and Claude code is that, while Claude basically disregards your instructions (CLAUDE.md) entirely, Codex is extremely, painfully, doggedly persistent in following every last character of them - to the point that i've seen it work for 30 minutes to convolute some solution that was only convoluted because of some sentence I t…
To me both of these are annoying outcomes unless there's some very clear documentation around that test explaining what it does. Ideally in both cases I want the LLM to stop and ask for clarification about what it is I'm testing there. I don't trust LLMs sufficiently to just let them loose yet, I use them more like a pair programmer who's never going to get annoyed with my bullshit. (So yes, I usually have them set to require approval on any edits, and will nitpick my way through them like the most annoying code reviewer you've ever met)
I really hope one day Ill work on challenges that need these new type of agents. Currently, I either need a fast agent that does what I want faster than I can type it (CRUD, forms, etc) or I need an agent to discuss a plan, ups and downs. Whenever I try to give it a bigger task it takes a lot of time, and often is not what I’ve expected, which might be totally my fault or context specific, but as soon as I’m able to…
The key is learning how to provide proper instructions. Treat it as a developer that just joined the project and isn't aware of the conventions. Provide hints for the desired API design, mention relevant code locations that should be read to gain context on the problem, or that do similar things. An AGENTS.md that explains the project and provides some general guidelines also helps a lot. Codex can be incredibly stro…
This might be in the nature of problems I’m facing in my coding endeavors. I just don’t have any tasks that I cant solve in less than 45 minutes, or the problem is so vague in my head, that I can't accurately describe it to an AI or human. Then usually I either need to split it in smaller problems or take a walk.
Since claude 4 I barely wish, omg I wish this agent would be smarter. I still wish it would be faster.
But what you described is of course good practice and necessary for smart execution as well.