I'm interested in hearing from engineers who have moved in the opposite direction.
At what point in your product lifecycle did you decide that agentic approach was wrong tool for the job?
What was the specific failure mode (reliability, cost, latency, maintainability) pushed you to replace agentic loop with more deterministic system/pipeline?
If all LLM tools disappeared tomorrow, all of my scripts and processes developed with an LLM will continue to work without hiccup. If anthropic went out of business tomorrow, I'd lose nothing switching to another provider because I don't have to "trust" agentic operations in automated processes. They are always overseen by me and they are rarely creating things I couldn't have created myself. It's just much faster to iterate on it with these tools.
This is a really pragmatic philosophy and I think it's underappreciated. Using the LLM as a development accelerator rather than a runtime dependency gives the best of both worlds.
I am approaching AI as not an automation technology, but as a cognitive assistance technology. My AI Agents are all "method actor prompted" and placed inside other open source software, where they are created to believe they are one of the developers of that open source application. That creates "intelligent" versions of those applications.
For example, a word processor I have integrated agents into that are able to support editing and layout of the contents of the editor, but more important the user can create solo and groups of agents that have knowledge of the subject document, and understand how to communicate better than the user - BUT they do not write for the user, they coach the user to write and communicate better.
Are you familiar with Chain-of-Thought / Reasoning models? I've made a fully transparent system that is similar I call "Chain of Method Actors" that operates very much like Chain-of-Thought models, but the user is included in the loops, in a conversational exchange between their experts and the user. Net result? Massive efficiency and expense savings. Where CoT models may spin in their agentic loops hundreds of times before they emit their best guess what they user wants, my Socratic Chain of Method Acting Agents will begin with clarifying questions, rather than guessing, and the eventual answer the user seeks is often delivered in 3 to 6 loops. Not hundreds.
But my goal here is not the same as most: my system I have designed is for people doing critical work they must understand and stand behind. This is a knowledge IDE that I have created. It's an office suite with conversationally programmable AI Agents that method act the expertise that one needs. It is not automation, it's human enhancement, intellectual cognitive support for people that cannot trust automation or delegation, the task is too critical.
I look at the traces of agent execution, and use that as a feedback to extract common patterns. The comment patterns are extracted out as Scripts, or Skills.
So Agent doesnt have to figure out how to do things from scratch, saving considerable amount of tokens and latency.
I also came across this paper recently: https://arxiv.org/abs/2603.25158
Which does exactly the same. Extracts traces and converts them into skills for agents to use.
AI can give suggestions, not decisions. IF you want decisions and responsibility to be taken, use real people.