![Revisit consent button](../images/body-df29beacd7496220cc94.svg) We value your privacy We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies. Customise Reject All Accept All Customise Consent Preferences ![](../images/body-2159bb67f3de8ad870eb.svg) We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below. The cookies that are categorised as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... Show more NecessaryAlways Active Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data. * Cookie BCTempID * Duration 10 minutes * Description No description available. * Cookie __cf_bm * Duration 1 hour * Description This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. * Cookie AWSALBCORS * Duration 7 days * Description Amazon Web Services set this cookie for load balancing. * Cookie _cfuvid * Duration session * Description Cloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services * Cookie li_gc * Duration 6 months * Description Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. * Cookie __hssrc * Duration session * Description This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. * Cookie __hssc * Duration 1 hour * Description HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. * Cookie wpEmojiSettingsSupports * Duration session * Description WordPress sets this cookie when a user interacts with emojis on a WordPress site. It helps determine if the user's browser can display emojis properly. * Cookie BCSessionID * Duration 1 year 1 month 4 days * Description Blueconic sets this cookie as a unique identifier for the BlueConic profile. * Cookie _octo * Duration 1 year * Description No description available. * Cookie logged_in * Duration 1 year * Description No description available. * Cookie __Secure-YEC * Duration past * Description YouTube sets this cookie to stores the user's video player preferences using embedded YouTube video * Cookie __eoi * Duration 6 months * Description Description is currently not available. * Cookie AWSALBTGCORS * Duration 7 days * Description No description available. * Cookie login-status-p * Duration past * Description Description is currently not available. * Cookie AWSALBTG * Duration 7 days * Description No description available. * Cookie csrf_token * Duration session * Description No description available. * Cookie token_v2 * Duration 1 day * Description Description is currently not available. * Cookie D * Duration 1 year * Description Description is currently not available. * Cookie PHPSESSID * Duration session * Description This cookie is native to PHP applications. The cookie stores and identifies a user's unique session ID to manage user sessions on the website. The cookie is a session cookie and will be deleted when all the browser windows are closed. * Cookie VISITOR_PRIVACY_METADATA * Duration 6 months * Description YouTube sets this cookie to store the user's cookie consent state for the current domain. * Cookie cookietest * Duration session * Description The cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience. * Cookie __Host-airtable-session * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie __Host-airtable-session.sig * Duration 1 year * Description This cookie is used to enable us to integrate the services of Airtable. * Cookie m * Duration 1 year 1 month 4 days * Description Stripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly. * Cookie BIGipServer* * Duration session * Description Marketo sets this cookie to collect information about the user's online activity and build a profile about their interests to provide advertisements relevant to the user. * Cookie __cfruid * Duration session * Description Cloudflare sets this cookie to identify trusted web traffic. * Cookie _GRECAPTCHA * Duration 6 months * Description Google Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks. * Cookie __Secure-YNID * Duration 6 months * Description Google cookie used to protect user security and prevent fraud, especially during the login process. * Cookie cookieyes-consent * Duration 1 year * Description CookieYes sets this cookie to remember users' consent preferences so that their preferences are respected on subsequent visits to this site. It does not collect or store any personal information about the site visitors. Functional Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features. * Cookie lidc * Duration 1 day * Description LinkedIn sets the lidc cookie to facilitate data center selection. * Cookie brw * Duration 1 year * Description No description available. * Cookie brwConsent * Duration 5 minutes * Description Description is currently not available. * Cookie WMF-Uniq * Duration 1 year * Description Description is currently not available. * Cookie loom_anon_comment * Duration 1 year * Description No description available. * Cookie loom_referral_video * Duration session * Description Description is currently not available. * Cookie VISITOR_INFO1_LIVE * Duration 6 months * Description A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. * Cookie yt-remote-connected-devices * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie ytidb::LAST_RESULT_ENTRY_KEY * Duration Never Expires * Description The cookie ytidb::LAST_RESULT_ENTRY_KEY is used by YouTube to store the last search result entry that was clicked by the user. This information is used to improve the user experience by providing more relevant search results in the future. * Cookie yt-remote-device-id * Duration Never Expires * Description YouTube sets this cookie to store the user's video preferences using embedded YouTube videos. * Cookie yt-remote-session-name * Duration session * Description The yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video. * Cookie yt-remote-fast-check-period * Duration session * Description The yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos. * Cookie yt-remote-session-app * Duration session * Description The yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player. * Cookie yt-remote-cast-available * Duration session * Description The yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player. * Cookie yt-remote-cast-installed * Duration session * Description The yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video. * Cookie cp_session * Duration 3 months * Description Codepen sets this cookie for Help systems found in the website. * Cookie loid * Duration 1 year 1 month 4 days * Description This cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform. Analytics Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc. * Cookie __hstc * Duration 6 months * Description Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). * Cookie hubspotutk * Duration 6 months * Description HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. * Cookie _ga * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. * Cookie _ga_* * Duration 1 year 1 month 4 days * Description Google Analytics sets this cookie to store and count page views. * Cookie __Host-psifi.analyticsTrace * Duration 6 hours * Description Description is currently not available. * Cookie __Host-psifi.analyticsTraceV2 * Duration 6 hours * Description Description is currently not available. * Cookie _gh_sess * Duration session * Description GitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form. * Cookie YSC * Duration session * Description YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. * Cookie ajs_anonymous_id * Duration 1 year * Description This cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before. * Cookie vuid * Duration 1 year 1 month 4 days * Description Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. Performance Performance cookies are used to understand and analyse the key performance indexes of the website which helps in delivering a better user experience for the visitors. * Cookie AWSALB * Duration 7 days * Description AWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target. * Cookie acq * Duration past * Description Description is currently not available. * Cookie acq.sig * Duration past * Description Description is currently not available. * Cookie ptc * Duration 2 years * Description No description available. Advertisement Advertisement cookies are used to provide visitors with customised advertisements based on the pages you visited previously and to analyse the effectiveness of the ad campaigns. * Cookie muc_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to collect user behaviour and interaction data to optimize the website. * Cookie guest_id_marketing * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie guest_id_ads * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. * Cookie personalization_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to integrate and share features for social media and also store information about how the user uses the website, for tracking and targeting. * Cookie guest_id * Duration 1 year 1 month 4 days * Description Twitter sets this cookie to identify and track the website visitor. It registers if a user is signed in to the Twitter platform and collects information about ad preferences. * Cookie bcookie * Duration 1 year * Description LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs. * Cookie __Secure-ROLLOUT_TOKEN * Duration 6 months * Description YouTube sets this cookie to manage feature rollout and experimentation. It helps Google control which new features or interface changes are shown to users as part of testing and staged rollouts, ensuring consistent experience for a given user during an experiment. * Cookie yt.innertube::nextId * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie yt.innertube::requests * Duration Never Expires * Description YouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen. * Cookie session_tracker * Duration session * Description This cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website. * Cookie edgebucket * Duration session * Description Reddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content. * Cookie did * Duration 1 year * Description Arbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year. Uncategorised Other uncategorised cookies are those that are being analysed and have not been classified into a category as yet. No cookies to display. Reject All Save My Preferences Accept All Toggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation [](https://towardsdatascience.com/) Publish AI, ML & data-science insights to a global community of data professionals. Sign in[Submit an Article](https://write.insightmediagroup.io) [Latest](https://towardsdatascience.com/latest/)[Editor's Picks](https://towardsdatascience.com/tag/editors-pick/)[Newsletter](https://towardsdatascience.com/tag/the-variable/)[ShipAI](https://towardsdatascience.com/shipai/) * * * [Write For TDS](https://towardsdatascience.com/submissions/) [LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search [Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/) # Why AI Engineers Are Moving Beyond LangChain to Native Agent Architectures Frameworks accelerated the first wave of LLM apps, but production demands a different architecture. [Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/) April 30, 20267 min read ![](../images/000.jpg) Image by author (Generated with ChatGPT) Recently, I've been sitting closely with this topic, and it brought back some experiences from working on a couple of projects. Take this scenario: you ship an LLM-powered feature, the demo is clean, and all stakeholders are happy. Then three weeks into production, something breaks in a way nobody can explain. You spend an afternoon staring at logs that tell you _what_ happened but not _why_. Then it turns out that the framework swallowed the context somewhere between step three and step four, and now you're reading source code you didn't write. That is not a bug report; it is a wakeup call about the architecture. Frameworks like LangChain let engineers build LLM-powered systems without first understanding how those systems work under pressure. At first, that sounds like the cavalry has arrived. But trust me, the cost doesn't show up until you're deep in a production incident, and now you're stuck wondering why your agent skipped the verification step it was supposed to run. This post is about that cost and why more engineers, after discovering it, are now building the orchestration layer by themselves. Learn this step by step with the interactive [AI Agents](https://roadmap.sh/ai-agents) roadmap. ## Give LangChain Its Credit I remember watching a colleague build a working RAG pipeline in about forty minutes sometime in early 2023. He went from the vector store through the retrieval chain, prompt templates, and the LLM call, all connected by lunchtime. Six months prior, that would have been at least a two-week project. Come to think of it, that's actually how and why LangChain spread so fast. Most engineers hadn't built LLM applications before. Nobody had strong opinions about the right way to structure a retrieval chain or manage conversation memory and other stuff like that. LangChain showed up with answers that were modular, composable, and documented, and of course, teams grabbed them immediately, including mine. So when I say it creates problems in production, I'm not being dismissive. It was optimized for the phase most teams were in when they adopted it. The problems came later, when the phase changed. ## Where the Abstraction Breaks When I was learning object-oriented programming in my sophomore year, one of the first concepts that clicked was abstraction: hiding the internal details of how something works and only exposing what the user needs. LangChain applies that same idea to LLM orchestration. It hides a lot of what's happening inside your system so you can move faster. But production AI systems demand something that cuts against that: **clarity**. You need to know exactly what your system did, in what order, with what inputs, and why. Not roughly. Exactly. Abstractions trade that visibility for speed. That’s a fair trade at first, until the hidden complexity becomes the very thing you need to understand. And it shows up in more ways than one. **Debugging is worse than it sounds:** When a multi-step chain gives the wrong output, you’re not just debugging your own code. You're also trying to understand the framework's execution flow and what the callback layer was doing behind the scenes. I once spent three hours tracking down a failure that turned out to be a memory module silently cutting out context. The fix itself took four minutes. Finding what caused it took half a day because the abstraction made the actual behavior invisible. **Observability hits a ceiling:** You can integrate [LangSmith](https://docs.smith.langchain.com/) and get useful traces, but you're still seeing things through the framework's lens, limited to the spans it chooses to expose. When you need visibility into something specific to your business logic, you end up working around the framework's data model instead of just measuring what actually matters. **Multi-agent state is where things really fall apart:** The moment you have [agents coordinating](https://lilianweng.github.io/posts/2023-06-23-agent/), one planning, others executing, and another verifying, shared state becomes the real problem. Who created this information, when, and is it still valid? One agent updates memory, another reads a stale version, and the coordinator makes a decision based on context that no longer matches reality. Framework-managed state tends to work just fine for the happy path and quietly breaks down at the edge cases. Production systems live in those edge cases. **Latency accumulates:** Every abstraction layer adds overhead through serialization, validation, callback firing, and internal routing that runs whether you need it or not. In a prototype that overhead is invisible. Under real traffic, it shows up in [percentile latency](https://www.brendangregg.com/blog/2017-08-08/latency-percentiles.html), specifically in the p95 and p99 ranges where users actually feel it. The cost per call might be small, but in an agentic system making four, five, or even six model calls per user request, those small costs compound quickly. At some point, you have to ask whether that overhead is still worth what it buys you. None of this is impossible to solve inside a framework. But the fixes start to look like working around the framework instead of working with it. And once you get there, it becomes harder to tell what the framework is still giving you. ## So What Does "Building It Yourself" Actually Look Like? "Native agent architecture" sounds more complex than it really is. It just means writing the orchestration logic yourself as code you own, instead of relying on a framework's abstraction of it. State is something you define and update explicitly. Tools are clear functions you can test on their own. Memory is code you wrote, so it’s easier to debug, control, and understand what gets stored and how it gets retrieved. The model call is your code, which means you can instrument it directly and trace what matters. Sure, there will be more code upfront. But when something breaks, the failure is in your code and not somewhere inside an execution model written by somebody else. Let's not forget, complex workflows map more naturally here. Things like parallel execution, conditional branching, and long-running async tasks work much better in [event-driven patterns](https://martinfowler.com/articles/201701-event-driven.html) in ways that synchronous chain execution doesn't handle cleanly. More design work upfront means less firefighting later. ··· I've seen teams rebuild a perfectly good LangChain prototype into a custom orchestration layer just because native architectures felt more “serious.” They spent three extra weeks on it and shipped the same system with more code to maintain. To me, that’s not progress. If you're checking whether a feature is worth building, then a framework gets you there faster. If three people use the system internally and nobody's pager is attached to it, the abstraction overhead is fine. The question isn’t “framework or native?” It’s what you need to optimize for right now. Fast iteration on uncertain requirements means the framework makes sense. Real users, real SLAs, agent coordination, and operational monitoring mean the native architecture earns its upfront cost. Most teams hit that turning point sooner than they expect, usually at the first serious debugging session or the first time someone asks for detailed metrics, and the honest answer is "not without a lot of extra work." That's the moment to rethink the architecture, not after six months of piling on workarounds. Frameworks are how knowledge transfers in a new field. LangChain made LLM application development accessible for a generation of engineers. That contribution is real. But maturity in a domain looks like moving from "I configure the framework to do the thing" to "I understand what the framework was doing, and I make those decisions myself." Not because frameworks are bad, but because owning your architecture means you know what’s happening under the hood. The engineers building the most reliable production AI systems aren't the ones with the most sophisticated tooling. They're the ones who can explain exactly what their system does at any point. What prompt is constructed, from what context, under what conditions, and with what fallback. That clarity is hard to maintain through thick layers of abstraction. ··· ## Final thoughts Abstraction debt is quiet until it's loud. You won't notice it during the build. You'll notice it when something fails in a way the framework's error message can't explain. That moment comes earlier than you expect, usually triggered by a debugging session or a monitoring ask rather than a planning meeting. State and observability are not optional. If you can’t trace what your agent did and why, you’re not really improving the system. You’re just hoping for the best every time you redeploy. Treat orchestration as a real architectural decision. Pick it on purpose, with the tradeoffs visible. The engineers building durable AI systems aren't the ones who avoided frameworks. They're the ones who knew when to stop letting the framework decide for them. ··· ## Before you go! I write more about the real engineering decisions behind AI systems, where abstractions help, where they hurt, and what it takes to build reliably. You can [**subscribe to my newsletter**](https://thatcsguy.substack.com/?r=79lldp&utm_campaign=pub-share-checklist) if you'd like more of that. **Connect With Me** * [LinkedIn](http://www.linkedin.com/in/nwekebenjamin) * [Substack](https://thatcsguy.substack.com/) ## Register Now to Continue Reading ### Unlock Towards Data Science with a Free Account All articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more. Register for freeSign in to your account * * * ![](../images/body-4ad89a2fc5e69dde007d.jpeg) Written By ## [Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/) Benjamin Nweke is a Computer Science graduate and technical writer exploring AI, machine learning, and data science. He writes about building reliable AI systems, model evaluation, agentic architectures, and the practical challenges that appear when machine learning moves beyond experiments. His work focuses on making technically complex ideas clear, useful, and grounded in real implementation. [See all from Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/) [AI Agents](https://towardsdatascience.com/tag/ai-agents-2/)[Artificial Intelligence](https://towardsdatascience.com/tag/artificial-intelligence/)[Langchain](https://towardsdatascience.com/tag/langchain/)[Machine Learning](https://towardsdatascience.com/tag/machine-learning/)[Software Architecture](https://towardsdatascience.com/tag/software-architecture/) Share This Article * [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Ftowardsdatascience.com%2Fwhy-ai-engineers-are-moving-beyond-langchain-to-native-agent-architectures%2F&title=Why%20AI%20Engineers%20Are%20Moving%20Beyond%20LangChain%20to%20Native%20Agent%20Architectures) * [](https://www.linkedin.com/shareArticle?mini=true&url=https%3A%2F%2Ftowardsdatascience.com%2Fwhy-ai-engineers-are-moving-beyond-langchain-to-native-agent-architectures%2F&title=Why%20AI%20Engineers%20Are%20Moving%20Beyond%20LangChain%20to%20Native%20Agent%20Architectures) * [](https://x.com/share?url=https%3A%2F%2Ftowardsdatascience.com%2Fwhy-ai-engineers-are-moving-beyond-langchain-to-native-agent-architectures%2F&text=Why%20AI%20Engineers%20Are%20Moving%20Beyond%20LangChain%20to%20Native%20Agent%20Architectures) Towards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program. [Write for TDS](https://towardsdatascience.com/submissions/) ## Related Articles * [![](../images/001.jpg)](https://towardsdatascience.com/recreating-an-ml-masters-degree-with-online-courses-8f90a7088cf8/) ## [Recreating an ML Master's degree with Online Courses](https://towardsdatascience.com/recreating-an-ml-masters-degree-with-online-courses-8f90a7088cf8/) [Deep Learning](https://towardsdatascience.com/category/artificial-intelligence/deep-learning/) Use online courses to create your curriculum [Pascal Janetzky](https://towardsdatascience.com/author/pascaljanetzky/) June 14, 20217 min read * [![](../images/002.jpeg)](https://towardsdatascience.com/recognizing-cats-and-dogs-with-tensorflow-105eb56da35f/) ## [Recognizing Cats and Dogs With TensorFlow](https://towardsdatascience.com/recognizing-cats-and-dogs-with-tensorflow-105eb56da35f/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) Create a neural network using TensorFlow to recognize cats and dogs [Patrick Kalkman](https://towardsdatascience.com/author/pkalkman/) January 11, 202110 min read * [![](../images/003.jpeg)](https://towardsdatascience.com/sort-pandas-df-5748eaadcd4f/) ## [How To Sort Pandas DataFrames](https://towardsdatascience.com/sort-pandas-df-5748eaadcd4f/) [Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/) Sorting pandas DataFrames using one or more columns [Giorgos Myrianthous](https://towardsdatascience.com/author/gmyrianthous/) July 5, 20225 min read * [![](../images/004.png)](https://towardsdatascience.com/why-hire-an-ai-consultant-50e155e17b39/) ## [How to Hire an AI Consultant](https://towardsdatascience.com/why-hire-an-ai-consultant-50e155e17b39/) [Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/) So, you know you need some machine learning/AI development. Why not just do it yourself? Well, the short answer is that specialists have... [Daniel Shapiro, PhD](https://towardsdatascience.com/author/lemaysolutions/) June 27, 201711 min read * [![](../images/005.jpeg)](https://towardsdatascience.com/deep-dive-into-context-engineering-for-ai-agents/) ## [Context Engineering for AI Agents: A Deep Dive](https://towardsdatascience.com/deep-dive-into-context-engineering-for-ai-agents/) [Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/) How to optimize context, a precious finite resource for AI agents [Clara Chong](https://towardsdatascience.com/author/clarachong13/) April 7, 20267 min read * [![](../images/006.jpg)](https://towardsdatascience.com/how-to-design-architectural-guardrails-around-ai-agents/) ## [How to Design Architectural Guardrails Around AI Agents](https://towardsdatascience.com/how-to-design-architectural-guardrails-around-ai-agents/) [Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/) Agent design patterns every data engineer must know [Thuwarakesh Murallie](https://towardsdatascience.com/author/thuwarakesh/) September 29, 202612 min read * [![](../images/007.jpg)](https://towardsdatascience.com/stop-ranking-agent-configs-by-average-score/) ## [Stop Ranking Agent Configs by Average Score](https://towardsdatascience.com/stop-ranking-agent-configs-by-average-score/) [Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/) Best-worst comparisons, MaxDiff-style judging, and Plackett-Luce utility scores give agent teams a cleaner way to decide which configs to ship, prune, and route toward next. [Doster Esh](https://towardsdatascience.com/author/doster.esh/) July 6, 202613 min read * [![](../images/008.jpeg)](https://towardsdatascience.com/production-ready-llms-made-simple-with-nemo-agent-toolkit/) ## [Production-Ready LLMs Made Simple with the NeMo Agent Toolkit](https://towardsdatascience.com/production-ready-llms-made-simple-with-nemo-agent-toolkit/) [Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/) From simple chat to multi-agent reasoning and real-time REST APIs [Mariya Mansurova](https://towardsdatascience.com/author/miptgirl/) December 31, 202522 min read * [![](../images/009.jpg)](https://towardsdatascience.com/coding-agents-dont-need-bigger-context-windows-they-need-a-context-compiler/) ## [Coding Agents Don’t Need Bigger Context Windows — They Need a Context Compiler](https://towardsdatascience.com/coding-agents-dont-need-bigger-context-windows-they-need-a-context-compiler/) [Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/) Most coding agents waste 70% of their context window on irrelevant code. A compiler would never do that. It resolves dependencies, discards unreachable code, and keeps only the interfaces where implementation isn’t needed. Coding agents do the opposite—and it’s costing them the exact thing a shrinking context budget can’t afford to lose. [Emmimal P Alexander](https://towardsdatascience.com/author/emmimalp.alexander/) August 1, 202613 min read * [YouTube](https://www.youtube.com/c/TowardsDataScience) * [X](https://x.com/TDataScience) * [LinkedIn](https://www.linkedin.com/company/towards-data-science/) * [Threads](https://www.threads.net/@towardsdatascience) * [Bluesky](https://bsky.app/profile/towardsdatascience.com) [](https://towardsdatascience.com/) Your home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals. Subscribe to Our Newsletter[Write For TDS](https://towardsdatascience.com/submissions/)•[About](https://towardsdatascience.com/about-towards-data-science-d691af11cc2f/)•[Advertise](https://contact.towardsdatascience.com/advertise-with-towards-data-science)•[Privacy Policy](https://towardsdatascience.com/privacy-policy/)•[Terms of Use](https://towardsdatascience.com/website-terms-of-use/) © Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network) #### Recommended Articles Close * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500) How Relevance Models Foreshadowed Transformers for NLP ](https://towardsdatascience.com/how-relevance-models-foreshadowed-transformers-for-nlp/ "How Relevance Models Foreshadowed Transformers for NLP") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500) Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1 ](https://towardsdatascience.com/javascript-fatigue-you-dont-need-js-to-build-chatgpt/ "Javascript Fatigue: HTMX Is All You Need to Build ChatGPT — Part 1") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500) The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs ](https://towardsdatascience.com/subset-sum-problem-solved-in-linear-time-for-dense-enough-inputs/ "The Subset Sum Problem Solved in Linear Time for Dense Enough Inputs") * [ ![](https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500) Does Your Company Have a Data Strategy? ](https://towardsdatascience.com/does-your-company-have-a-data-strategy-e8944dbec4ae/ "Does Your Company Have a Data Strategy?")