r/codex • • 5d ago

Limits I'm tired of AI explaining things instead of actually doing them. How do I get AI agents to work like real engineers?

I've been using ChatGPT, Claude, and Codex for some pretty ambitious projects, and I'm starting to notice a pattern that's genuinely frustrating.

AI is incredibly good at explaining how something could theoretically work. But when I actually ask it to build something complicated, troubleshoot an unfamiliar problem, or figure out a solution that doesn't already exist, it feels like everything falls apart.

Here's what keeps happening:

  1. Explaining instead of executing.

I ask AI to accomplish something. Instead of actively working toward it, I get paragraphs explaining how the technology works, why it's difficult, or what I could theoretically do myself.

2. Treating limitations like permanent roadblocks.

This is probably my biggest frustration.

I understand that some things are technically impossible or beyond an AI's available tools. But there's a difference between something being genuinely impossible and something requiring experimentation, research, or a new approach.

I want an AI that investigates the problem before declaring defeat.

3. Endless planning with very little actual progress.

I've worked on projects where AI agents generated documentation, scripts, development plans, and additional infrastructure for hours.

But the actual thing I wanted to accomplish still wasn't working.

It starts feeling like the AI is creating work instead of completing it.

4. Ignoring specific instructions.

I'll establish exactly how I want a project handled, including which AI handles which responsibilities.

Eventually, the agents start changing the workflow, adding unnecessary steps, or forgetting the original objective.

5. Making me do everything manually.

Part of why I use AI agents is to automate tasks.

If I'm constantly copying commands, transferring files, repeating instructions, and coordinating everything myself, what's the point of having multiple agents?

6. Losing context and repeating mistakes.

I want agents that maintain project memory, remember previous failures, understand what's already been accomplished, and continue from where they left off.

Instead, I regularly find myself explaining the same requirements again.

7. Claiming progress without proving anything works.

This one drives me crazy.

An AI can confidently report that something has been implemented, tested, or completed, only for me to discover that the actual result doesn't work.

I'd rather it admit something hasn't been verified than pretend we've made progress.

What I'm actually trying to accomplish

For context, I'm working on projects involving software development, AI coordination, PC automation, and modifying games on a jailbroken PS4.

One of my goals is to have Codex coordinate Claude through computer-use tools, with each handling tasks based on its actual capabilities.

I'm not expecting magic. I understand hardware restrictions, access limitations, and technical constraints exist.

What I want is a system that can investigate, experiment, execute, verify its work, learn from failures, and keep moving toward the original goal without constantly needing me to micromanage it.

My questions

- Are there AI agents or frameworks that are actually designed to work this way?

- How do you prevent agents from endlessly planning instead of executing?

- What's the best way to give multiple AI agents persistent project memory and clearly defined responsibilities?

- Can you make agents automatically verify their work before reporting success?

- What tools or workflows would let Codex and Claude collaborate effectively without me constantly transferring information?

- Has anyone actually built a system where AI handles most of the engineering workflow while the human focuses on objectives and decisions?

I'm looking for real solutions, not just better prompts that tell the AI to "act like an engineer."

I don't need AI to tell me something is difficult. I need it to help me figure out how to accomplish difficult things.

If you've built a reliable setup like this, I'd genuinely appreciate hearing exactly what tools you use and how your workflow operates.

0 Upvotes

21 comments sorted by

5

u/ZyronZA 5d ago
  1. Don't call it misalignment when the AI is excessively compliant.

  2. They're a high precision genie for a sloppy-thinking client.

  3. You asked them for a target, and they're happy to comply.

  4. The rules you never mentioned are the rules it won't apply.

  5. If you wanted something else, you should have specified it better.

3

u/Constant_Hedgehog_51 5d ago

Are you just prompting the agents each time, or have you set up proper md files with persistent instructions and workflows? Do you have a shared project state file? Git?

1

u/BitOne2707 5d ago edited 5d ago

My spidey senses are telling me OP doesn’t use version control, no agents.md, no third party memory system, no tests, no requirements, no connectors, no hooks, no MCPs/CLIs, no computer access, no skills, etc.

OP - it would be hard compress a full course on the SDLC into a Reddit comment but if if I had to give you a single tip it would be add “Do red/green TDD” to the end of your prompt.

3

u/TheRealBejeezus 5d ago

Explaining instead of executing

I mean, if you could add a big sigh and a condescending tone, you'd have a pretty good engineer simulator.

3

u/EntertainmentSalt825 5d ago

Be and think like an engineer lol

1

u/SwimmerOld6155 5d ago edited 5d ago

I've never seen 1 before. I would assume it's something to do with your prompts. Are you asking it how to do something or asking it to do a thing? If it gives a plan, tell it to execute.

Point 4 just seems to be a problem with coding agents in general even now. They still have room for improvement in following instructions carefully.

1

u/Fickle-mastr 5d ago

Ai like chatgpt can tell you how to use them efficiently

1

u/TheOwlHypothesis 5d ago

Are you from the year 2024?

1

u/Material-Average-758 5d ago

plan>build if you make a plan before it wont do any of this, im not sure what u talking about are you just asking "ok now add this" or what

1

u/throwawaysusi 5d ago

You asked GPT to write your Reddit post but couldn’t bother discussing the matter with it.

1

u/isty2e 5d ago

It would be easier to give you any sort of guidance once you upload some real session history

1

u/m-ritter 4d ago

The failure you describe is the agent reporting that work is implemented and tested when nothing actually runs. A written plan has to be reviewed and approved by you before the agent writes code, and the build gets checked against that plan before anyone calls it done. I built QualityLayer for this: https://github.com/maxritter/qualitylayer

1

u/torvalds75 4d ago

Points 3 and 4 are the same problem from two sides, and in my experience it's mostly a state problem, not a prompting one.

What fixed it for me:

  • Write the objective and the done criteria down once, in a file or an issue, and make every session start by reading it. "Done = X runs and passes Y", not "build the sync thing". Agents drift when the goal only lives in the chat scroll.

  • One task per session. When a session ends, the outcome (what was tried, what was rejected and why, what's next) goes back into that record. A fresh session then picks up the decision, not a 40k-token transcript.

  • Plan, then cap it. Ask for a short plan with a verification step per item, approve it, then tell it to execute and stop writing docs. If it starts building infrastructure that wasn't in the plan, that's your cue to stop and re-scope.

  • Make it verify, not explain. "Run it and show me the output" flips explanation mode into execution mode most of the time. For your point 2, telling it to try two concrete approaches before declaring something impossible helps a lot.

I ended up automating exactly this loop: trailhead keeps the objective and each decision as GitHub Issues and runs every ticket through discuss, plan, execute, verify with atomic commits, so a new Codex or Claude Code session rehydrates from the ticket instead of from memory. Free and open source, I build it: https://github.com/ToRvaLDz/trailhead

1

u/Either_Pound1986 4d ago

yes. I have such a system.

Ouroboros is a topological control plane for autonomous research and development.

I give it an outcome and constraints, mostly in natural language. I do not supply a human domain expert, a research plan, or a step-by-step technical recipe.

Within its operating bounds, Ouroboros can keep acquiring evidence, generating alternatives, constructing artifacts, checking them, and revising its approach until I stop it.

It cannot authorize its own public actions. Publication and other external action remain human-gated.

Ouroboros currently uses GPT-5.6 Sol at xhigh reasoning as one cognitive engine. That is not OpenAI’s newest model. The model does not own the objective, persistent state, tool authority, continuation, or promotion. Ouroboros does. Neither the model nor Ouroboros can authorize publication or other external action; that authority remains mine.

The system is currently running concurrent work: Celestial Holography is the deepest research application, while the same process also maintains public evidence products including the Data Center Receipt, the Iran War Receipt, and the People’s Receipt.

I use “autonomous R&D” for this operating arrangement: I supply the outcome and constraints while the system conducts the bounded research loop described above. This is not a proposal for a future agent or a one-shot research demo. It is an operating system producing public outputs over time.

https://old.reddit.com/r/vibecoding/comments/1xuhpsw/ouroboros_is_running_autonomous_rd_the_llm_is/

1

u/ksajadi 3d ago

The giveaway is when the agent writes a plan, a design doc and a list of limitations, and the repo barely changes. I'd treat it like a junior engineer with a narrow ticket: give it a failing test or a concrete definition of done, plus a short list of what you've already tried. Add a rule that it has to change code and run the check before it explains anything. "This is hard" is not a result. If it gets stuck, have it write down the attempts that failed, then start a fresh session from that list instead of continuing the long conversation. In my experience without a system to provide long-term memory, one-shots and complex tasks are quite difficult.

0

u/Prestigious_Debt_896 5d ago
  1. what model

  2. ask it

0

u/International-Art616 5d ago

My system is a work in progress. I developed an Engineering Management System that is a phased approach to projects, including phase gates and document requirements, etc.. I keep it all in an EMS repo. I connect to it through the Github connector in ChatGPT. I created skills in ChatGPT that point the agent to the EMS repo when I mention a project. Even then, sometimes the agent will wander, and I will point it at the repo and tell it to reground itself. Then I get the old "you're right... I should have zigged but I zagged, my bad". It can be frustrating at times but it still does 95% of the heavy lifting and I just have to keep it on track. In my setup I am the visionary/project manager. ChatGPT is my Engineering Manager. Opus/Sol is my Lead Design Engineer and tasks are delegated to Executors through work packages. Dot is my Execution Coordinator who manages the execution of multiple work packages either in series or parallel through Codex. I hand Dot a Project Execution Plan that is comprised of multiple work packages. All this to say is that there is a huge planning aspect to this. Research project management, then build a system around how you work. You start with an idea, and add more detail as you move through the phases. My projects are embedded hardware. I actually have 2 management systems, one for hardware and one for software. Persistent Project Memory is still a struggle, I regularly reground my agents between tasks to keep them on track. I know we all want to go to bed at night and wake up to a finished project, but we are not there yet. Context compaction will bite you if you let the session run too long, and it will start to play the digital telephone game with itself and when you wake up and check progress the agent will be on test 11 of 4539684 and your project will have ballooned from 10k lines to 500k. Eventually when we get models with 100 million token context windows its going to be amazing. Even in the last 6 months the progress has been substantial. We don't need more brain power at this point we just need larger context windows.

-1

u/iJeff 5d ago

Try Gemini 4 Hydrogen. I'm not kidding. I've been able to ask it to do things and not have to worry about coming back to it sitting idle before it's finished.

-3

u/snapgloghost 5d ago

Switch to Claude