Our first support agent was a single loop: give the model every tool, a long system prompt and let it call tools until it said it was done. It demoed well. In production it was slow on simple questions, unpredictable on hard ones, and twice it issued a refund nobody had approved. Every fix we tried was another paragraph in the prompt. What finally worked was not a smarter model but less freedom. We split the loop into a handful of well-known patterns, each with a narrow job, explicit state and a...
Agentic design patterns that survive production: router, planner, reflection, approvals
Most agent demos are one big loop around a model. In production we replaced ours with four explicit patterns: a router, a planner with a fixed step budget, a bounded reflection pass and an approval gate for side effects. Here is how each works and where it fails.
This is a paid story
Subscribe to read the full content, access all paid stories, and support the authors.
Add a label
Embed this post
<iframe src="https://www.hibug.me/agentic-design-patterns-in-production" width="700" height="420" frameborder="0" loading="lazy"></iframe>
I am a Senior Software Engineer with over a decade of hands-on experience building, scaling, and maintaining complex systems across the full stack—spanning frontend, backend, and DevOps. Over the last 10 years, I have navigated diverse architectures and untangled some of the most frustrating, elusive bugs in production. I believe that every production incident is a massive learning opportunity. Having discovered hibug.me, I am excited to contribute to this knowledge base, breaking down root causes, and sharing verified fixes to help fellow developers debug faster and build more resilient systems.
Comments
0No comments yet. Be the first to comment!
Sign In to post a comment.