{
  "source_file": "0930",
  "source_platform": "Medium",
  "author": "Benjamin Nweke",
  "title_listed": "Why AI Engineers Are Moving Beyond LangChain to Native Agent Architectures",
  "keywords": "",
  "domain": "大模型算法",
  "content_type": "深度技术解析",
  "is_paid_flag": "否",
  "url": "https://towardsdatascience.com/why-ai-engineers-are-moving-beyond-langchain-to-native-agent-architectures/",
  "publish_date": "2026-04-30",
  "corpus_stage": "",
  "notes": "",
  "id": "00a265af0151",
  "collected_at": "2026-10-02T07:41:16",
  "title": "Why AI Engineers Are Moving Beyond LangChain to Native Agent Architectures | Towards Data Science",
  "body_markdown": "![Revisit consent button](../images/body-df29beacd7496220cc94.svg)\nWe value your privacy\nWe 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.\nCustomise Reject All Accept All\nCustomise Consent Preferences ![](../images/body-2159bb67f3de8ad870eb.svg)\nWe use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.\nThe 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\nNecessaryAlways Active\nNecessary 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.\n  * Cookie\nBCTempID\n  * Duration\n10 minutes\n  * Description\nNo description available.\n\n\n  * Cookie\n__cf_bm\n  * Duration\n1 hour\n  * Description\nThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management. \n\n\n  * Cookie\nAWSALBCORS\n  * Duration\n7 days\n  * Description\nAmazon Web Services set this cookie for load balancing.\n\n\n  * Cookie\n_cfuvid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services\n\n\n  * Cookie\nli_gc\n  * Duration\n6 months\n  * Description\nLinkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.\n\n\n  * Cookie\n__hssrc\n  * Duration\nsession\n  * Description\nThis 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.\n\n\n  * Cookie\n__hssc\n  * Duration\n1 hour\n  * Description\nHubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.\n\n\n  * Cookie\nwpEmojiSettingsSupports\n  * Duration\nsession\n  * Description\nWordPress 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.\n\n\n  * Cookie\nBCSessionID\n  * Duration\n1 year 1 month 4 days\n  * Description\nBlueconic sets this cookie as a unique identifier for the BlueConic profile.\n\n\n  * Cookie\n_octo\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nlogged_in\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\n__Secure-YEC\n  * Duration\npast\n  * Description\nYouTube sets this cookie to stores the user's video player preferences using embedded YouTube video\n\n\n  * Cookie\n__eoi\n  * Duration\n6 months\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTGCORS\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\nlogin-status-p\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTG\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\ncsrf_token\n  * Duration\nsession\n  * Description\nNo description available.\n\n\n  * Cookie\ntoken_v2\n  * Duration\n1 day\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nD\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nPHPSESSID\n  * Duration\nsession\n  * Description\nThis 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.\n\n\n  * Cookie\nVISITOR_PRIVACY_METADATA\n  * Duration\n6 months\n  * Description\nYouTube sets this cookie to store the user's cookie consent state for the current domain. \n\n\n  * Cookie\ncookietest\n  * Duration\nsession\n  * Description\nThe cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience.\n\n\n  * Cookie\n__Host-airtable-session\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\n__Host-airtable-session.sig\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\nm\n  * Duration\n1 year 1 month 4 days\n  * Description\nStripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly.\n\n\n  * Cookie\nBIGipServer*\n  * Duration\nsession\n  * Description\nMarketo 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. \n\n\n  * Cookie\n__cfruid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to identify trusted web traffic.\n\n\n  * Cookie\n_GRECAPTCHA\n  * Duration\n6 months\n  * Description\nGoogle Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks.\n\n\n  * Cookie\n__Secure-YNID\n  * Duration\n6 months\n  * Description\nGoogle cookie used to protect user security and prevent fraud, especially during the login process.\n\n\n  * Cookie\ncookieyes-consent\n  * Duration\n1 year\n  * Description\nCookieYes 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.\n\n\nFunctional\nFunctional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.\n  * Cookie\nlidc\n  * Duration\n1 day\n  * Description\nLinkedIn sets the lidc cookie to facilitate data center selection.\n\n\n  * Cookie\nbrw\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nbrwConsent\n  * Duration\n5 minutes\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nWMF-Uniq\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nloom_anon_comment\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nloom_referral_video\n  * Duration\nsession\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nVISITOR_INFO1_LIVE\n  * Duration\n6 months\n  * Description\nA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.\n\n\n  * Cookie\nyt-remote-connected-devices\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nytidb::LAST_RESULT_ENTRY_KEY\n  * Duration\nNever Expires\n  * Description\nThe 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.\n\n\n  * Cookie\nyt-remote-device-id\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-name\n  * Duration\nsession\n  * Description\nThe yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\nyt-remote-fast-check-period\n  * Duration\nsession\n  * Description\nThe yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-app\n  * Duration\nsession\n  * Description\nThe yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-available\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-installed\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\ncp_session\n  * Duration\n3 months\n  * Description\nCodepen sets this cookie for Help systems found in the website.\n\n\n  * Cookie\nloid\n  * Duration\n1 year 1 month 4 days\n  * Description\nThis cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform.\n\n\nAnalytics\nAnalytical 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.\n  * Cookie\n__hstc\n  * Duration\n6 months\n  * Description\nHubspot 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).\n\n\n  * Cookie\nhubspotutk\n  * Duration\n6 months\n  * Description\nHubSpot 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.\n\n\n  * Cookie\n_ga\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle 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.\n\n\n  * Cookie\n_ga_*\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle Analytics sets this cookie to store and count page views.\n\n\n  * Cookie\n__Host-psifi.analyticsTrace\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n__Host-psifi.analyticsTraceV2\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n_gh_sess\n  * Duration\nsession\n  * Description\nGitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form.\n\n\n  * Cookie\nYSC\n  * Duration\nsession\n  * Description\nYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.\n\n\n  * Cookie\najs_anonymous_id\n  * Duration\n1 year\n  * Description\nThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.\n\n\n  * Cookie\nvuid\n  * Duration\n1 year 1 month 4 days\n  * Description\nVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. \n\n\nPerformance\nPerformance 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.\n  * Cookie\nAWSALB\n  * Duration\n7 days\n  * Description\nAWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target.\n\n\n  * Cookie\nacq\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nacq.sig\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nptc\n  * Duration\n2 years\n  * Description\nNo description available.\n\n\nAdvertisement\nAdvertisement 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.\n  * Cookie\nmuc_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to collect user behaviour and interaction data to optimize the website.\n\n\n  * Cookie\nguest_id_marketing\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\nguest_id_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\npersonalization_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter 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.\n\n\n  * Cookie\nguest_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter 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.\n\n\n  * Cookie\nbcookie\n  * Duration\n1 year\n  * Description\nLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.\n\n\n  * Cookie\n__Secure-ROLLOUT_TOKEN\n  * Duration\n6 months\n  * Description\nYouTube 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.\n\n\n  * Cookie\nyt.innertube::nextId\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nyt.innertube::requests\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nsession_tracker\n  * Duration\nsession\n  * Description\nThis cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website.\n\n\n  * Cookie\nedgebucket\n  * Duration\nsession\n  * Description\nReddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content.\n\n\n  * Cookie\ndid\n  * Duration\n1 year\n  * Description\nArbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year.\n\n\nUncategorised\nOther uncategorised cookies are those that are being analysed and have not been classified into a category as yet.\nNo cookies to display.\nReject All Save My Preferences Accept All\nToggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation\n[](https://towardsdatascience.com/)\nPublish AI, ML & data-science insights to a global community of data professionals.\nSign in[Submit an Article](https://write.insightmediagroup.io)\n[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/)\n* * *\n[Write For TDS](https://towardsdatascience.com/submissions/)\n[LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\n# Why AI Engineers Are Moving Beyond LangChain to Native Agent Architectures\nFrameworks accelerated the first wave of LLM apps, but production demands a different architecture.\n[Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/)\nApril 30, 20267 min read\n![](../images/000.jpg)\nImage by author (Generated with ChatGPT)\nRecently, I've been sitting closely with this topic, and it brought back some experiences from working on a couple of projects.\nTake 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.\nYou spend an afternoon staring at logs that tell you _what_ happened but not _why_.\nThen 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.\nThat is not a bug report; it is a wakeup call about the architecture.\nFrameworks 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.\nBut 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.\nThis post is about that cost and why more engineers, after discovering it, are now building the orchestration layer by themselves.\nLearn this step by step with the interactive [AI Agents](https://roadmap.sh/ai-agents) roadmap.\n## Give LangChain Its Credit\nI remember watching a colleague build a working RAG pipeline in about forty minutes sometime in early 2023.\nHe went from the vector store through the retrieval chain, prompt templates, and the LLM call, all connected by lunchtime.\nSix months prior, that would have been at least a two-week project.\nCome to think of it, that's actually how and why LangChain spread so fast. \nMost 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. \nLangChain showed up with answers that were modular, composable, and documented, and of course, teams grabbed them immediately, including mine.\nSo 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.\n## Where the Abstraction Breaks\nWhen 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.\nLangChain applies that same idea to LLM orchestration. It hides a lot of what's happening inside your system so you can move faster.\nBut production AI systems demand something that cuts against that: **clarity**. \nYou need to know exactly what your system did, in what order, with what inputs, and why. Not roughly. Exactly.\nAbstractions trade that visibility for speed. That’s a fair trade at first, until the hidden complexity becomes the very thing you need to understand.\nAnd it shows up in more ways than one.\n**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.\nI 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.\n**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.\n**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.\nWho created this information, when, and is it still valid?\nOne agent updates memory, another reads a stale version, and the coordinator makes a decision based on context that no longer matches reality.\nFramework-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.\n**Latency accumulates:** Every abstraction layer adds overhead through serialization, validation, callback firing, and internal routing that runs whether you need it or not.\nIn 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.\nThe 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.\nAt some point, you have to ask whether that overhead is still worth what it buys you.\nNone 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.\n## So What Does \"Building It Yourself\" Actually Look Like?\n\"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.\nState 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.\nThe model call is your code, which means you can instrument it directly and trace what matters.\nSure, 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.\nLet'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.\nMore design work upfront means less firefighting later.\n···\nI'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.\nTo me, that’s not progress.\nIf 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.\nThe 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.\nMost 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.\"\nThat's the moment to rethink the architecture, not after six months of piling on workarounds.\nFrameworks are how knowledge transfers in a new field. LangChain made LLM application development accessible for a generation of engineers. That contribution is real.\nBut 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.\" \nNot because frameworks are bad, but because owning your architecture means you know what’s happening under the hood.\nThe engineers building the most reliable production AI systems aren't the ones with the most sophisticated tooling.\nThey'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.\nThat clarity is hard to maintain through thick layers of abstraction.\n···\n## Final thoughts\nAbstraction 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.\nThat moment comes earlier than you expect, usually triggered by a debugging session or a monitoring ask rather than a planning meeting.\nState 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.\nTreat orchestration as a real architectural decision. Pick it on purpose, with the tradeoffs visible.\nThe 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.\n···\n## Before you go!\nI write more about the real engineering decisions behind AI systems, where abstractions help, where they hurt, and what it takes to build reliably. \nYou can [**subscribe to my newsletter**](https://thatcsguy.substack.com/?r=79lldp&utm_campaign=pub-share-checklist) if you'd like more of that.\n**Connect With Me**\n  * [LinkedIn](http://www.linkedin.com/in/nwekebenjamin)\n  * [Substack](https://thatcsguy.substack.com/)\n\n\n## Register Now to Continue Reading\n### Unlock Towards Data Science with a Free Account\nAll articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more.\nRegister for freeSign in to your account\n* * *\n![](../images/body-4ad89a2fc5e69dde007d.jpeg)\nWritten By\n## [Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/)\nBenjamin 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.\n[See all from Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/)\n[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/)\nShare This Article\n  * [](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)\n  * [](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)\n  * [](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)\n\n\nTowards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program.\n[Write for TDS](https://towardsdatascience.com/submissions/)\n## Related Articles\n  * [![](../images/001.jpg)](https://towardsdatascience.com/recreating-an-ml-masters-degree-with-online-courses-8f90a7088cf8/)\n## [Recreating an ML Master's degree with Online Courses](https://towardsdatascience.com/recreating-an-ml-masters-degree-with-online-courses-8f90a7088cf8/)\n[Deep Learning](https://towardsdatascience.com/category/artificial-intelligence/deep-learning/)\nUse online courses to create your curriculum\n[Pascal Janetzky](https://towardsdatascience.com/author/pascaljanetzky/)\nJune 14, 20217 min read\n  * [![](../images/002.jpeg)](https://towardsdatascience.com/recognizing-cats-and-dogs-with-tensorflow-105eb56da35f/)\n## [Recognizing Cats and Dogs With TensorFlow](https://towardsdatascience.com/recognizing-cats-and-dogs-with-tensorflow-105eb56da35f/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nCreate a neural network using TensorFlow to recognize cats and dogs\n[Patrick Kalkman](https://towardsdatascience.com/author/pkalkman/)\nJanuary 11, 202110 min read\n  * [![](../images/003.jpeg)](https://towardsdatascience.com/sort-pandas-df-5748eaadcd4f/)\n## [How To Sort Pandas DataFrames](https://towardsdatascience.com/sort-pandas-df-5748eaadcd4f/)\n[Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/)\nSorting pandas DataFrames using one or more columns\n[Giorgos Myrianthous](https://towardsdatascience.com/author/gmyrianthous/)\nJuly 5, 20225 min read\n  * [![](../images/004.png)](https://towardsdatascience.com/why-hire-an-ai-consultant-50e155e17b39/)\n## [How to Hire an AI Consultant](https://towardsdatascience.com/why-hire-an-ai-consultant-50e155e17b39/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nSo, you know you need some machine learning/AI development. Why not just do it yourself? Well, the short answer is that specialists have...\n[Daniel Shapiro, PhD](https://towardsdatascience.com/author/lemaysolutions/)\nJune 27, 201711 min read\n  * [![](../images/005.jpeg)](https://towardsdatascience.com/deep-dive-into-context-engineering-for-ai-agents/)\n## [Context Engineering for AI Agents: A Deep Dive](https://towardsdatascience.com/deep-dive-into-context-engineering-for-ai-agents/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nHow to optimize context, a precious finite resource for AI agents\n[Clara Chong](https://towardsdatascience.com/author/clarachong13/)\nApril 7, 20267 min read\n  * [![](../images/006.jpg)](https://towardsdatascience.com/how-to-design-architectural-guardrails-around-ai-agents/)\n## [How to Design Architectural Guardrails Around AI Agents](https://towardsdatascience.com/how-to-design-architectural-guardrails-around-ai-agents/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nAgent design patterns every data engineer must know\n[Thuwarakesh Murallie](https://towardsdatascience.com/author/thuwarakesh/)\nSeptember 29, 202612 min read\n  * [![](../images/007.jpg)](https://towardsdatascience.com/stop-ranking-agent-configs-by-average-score/)\n## [Stop Ranking Agent Configs by Average Score](https://towardsdatascience.com/stop-ranking-agent-configs-by-average-score/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nBest-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.\n[Doster Esh](https://towardsdatascience.com/author/doster.esh/)\nJuly 6, 202613 min read\n  * [![](../images/008.jpeg)](https://towardsdatascience.com/production-ready-llms-made-simple-with-nemo-agent-toolkit/)\n## [Production-Ready LLMs Made Simple with the NeMo Agent Toolkit](https://towardsdatascience.com/production-ready-llms-made-simple-with-nemo-agent-toolkit/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nFrom simple chat to multi-agent reasoning and real-time REST APIs\n[Mariya Mansurova](https://towardsdatascience.com/author/miptgirl/)\nDecember 31, 202522 min read\n  * [![](../images/009.jpg)](https://towardsdatascience.com/coding-agents-dont-need-bigger-context-windows-they-need-a-context-compiler/)\n## [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/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nMost 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.\n[Emmimal P Alexander](https://towardsdatascience.com/author/emmimalp.alexander/)\nAugust 1, 202613 min read\n\n\n  * [YouTube](https://www.youtube.com/c/TowardsDataScience)\n  * [X](https://x.com/TDataScience)\n  * [LinkedIn](https://www.linkedin.com/company/towards-data-science/)\n  * [Threads](https://www.threads.net/@towardsdatascience)\n  * [Bluesky](https://bsky.app/profile/towardsdatascience.com)\n\n\n[](https://towardsdatascience.com/)\nYour home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals.\nSubscribe 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/)\n© Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network)\n####  Recommended Articles \nClose\n  * [ ![](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\")\n  * [ ![](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\")\n  * [ ![](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\")\n  * [ ![](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?\")\n\n\n",
  "metadata": {
    "title": "Why AI Engineers Are Moving Beyond LangChain to Native Agent Architectures | Towards Data Science",
    "description": "Frameworks accelerated the first wave of LLM apps, but production demands a different architecture.",
    "keywords": null,
    "author": "Benjamin Nweke",
    "og:locale": "en_US",
    "og:type": "article",
    "og:title": "Why AI Engineers Are Moving Beyond LangChain to Native Agent Architectures",
    "og:description": "Frameworks accelerated the first wave of LLM apps, but production demands a different architecture.",
    "og:url": "https://towardsdatascience.com/why-ai-engineers-are-moving-beyond-langchain-to-native-agent-architectures/",
    "og:site_name": "Towards Data Science",
    "og:image": "https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/ChatGPT-Image-Apr-26-2026-12_48_58-AM.jpg",
    "og:image:width": "1536",
    "og:image:height": "1024",
    "og:image:type": "image/jpeg",
    "twitter:card": "summary_large_image",
    "twitter:site": "@TDataScience",
    "twitter:creator": "@TDataScience",
    "twitter:label1": "Written by",
    "twitter:data1": "Benjamin Nweke",
    "twitter:label2": "Est. reading time",
    "twitter:data2": "7 min read",
    "article:published_time": "2026-04-30T06:00:06.000Z",
    "article:modified_time": "2026-04-30T06:00:06.000Z",
    "article:author": "https://towardsdatascience.com/author/benjaminnweke/"
  },
  "paywall": {
    "listed_paid": false,
    "detected": false,
    "marker": "",
    "public_only": false,
    "policy": "付费/会员内容只保留页面公开可见部分，不绕过付费墙"
  },
  "crawl": {
    "success": true,
    "status_code": 202,
    "error": ""
  },
  "code_blocks": [],
  "images": [
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607686/image?etag=1782161464448&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T17:59:01Z"
    },
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607639/image?etag=1781250125848&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T17:59:01Z"
    },
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/607930/image?etag=1782124566054&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T17:59:01Z"
    },
    {
      "status": "http_404",
      "url": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500",
      "src": "https://h030.towardsdatascience.com/rest/v2/contentStores/d7d3a4ab-7caf-4383-bbd2-fbf7fb4f1787/items/3660/image?etag=1780176246070&width=500&height=500",
      "alt": "",
      "downloaded": false,
      "discovery": "saved_markdown",
      "retried_at": "2026-10-20T17:59:01Z"
    }
  ],
  "audio": [],
  "videos": [
    {
      "url": "https://www.youtube.com/c/TowardsDataScience",
      "kind": "channel_reference",
      "status": "reference_only"
    }
  ],
  "links": [
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/latest/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/editors-pick/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/the-variable/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/shipai/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/submissions/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/author/benjaminnweke/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/ai-agents-2/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/artificial-intelligence/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/langchain/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/machine-learning/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/tag/software-architecture/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/recreating-an-ml-masters-degree-with-online-courses-8f90a7088cf8/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/category/artificial-intelligence/deep-learning/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/author/pascaljanetzky/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/recognizing-cats-and-dogs-with-tensorflow-105eb56da35f/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/category/artificial-intelligence/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/author/pkalkman/"
    },
    {
      "type": "internal",
      "href": "https://towardsdatascience.com/sort-pandas-df-5748eaadcd4f/"
    },
    {
      "type": "external",
      "href": "https://write.insightmediagroup.io"
    },
    {
      "type": "external",
      "href": "https://www.linkedin.com/company/towards-data-science/"
    },
    {
      "type": "external",
      "href": "https://x.com/TDataScience"
    },
    {
      "type": "external",
      "href": "https://roadmap.sh/ai-agents"
    },
    {
      "type": "external",
      "href": "https://docs.smith.langchain.com/"
    },
    {
      "type": "external",
      "href": "https://lilianweng.github.io/posts/2023-06-23-agent/"
    },
    {
      "type": "external",
      "href": "https://www.brendangregg.com/blog/2017-08-08/latency-percentiles.html"
    },
    {
      "type": "external",
      "href": "https://martinfowler.com/articles/201701-event-driven.html"
    },
    {
      "type": "external",
      "href": "https://thatcsguy.substack.com/?r=79lldp"
    },
    {
      "type": "external",
      "href": "http://www.linkedin.com/in/nwekebenjamin"
    },
    {
      "type": "external",
      "href": "https://thatcsguy.substack.com/"
    },
    {
      "type": "external",
      "href": "https://www.facebook.com/sharer/sharer.php?title=Why+AI+Engineers+Are+Moving+Beyond+LangChain+to+Native+Agent+Architectures&u=https%3A%2F%2Ftowardsdatascience.com%2Fwhy-ai-engineers-are-moving-beyond-langchain-to-native-agent-architectures%2F"
    },
    {
      "type": "external",
      "href": "https://www.linkedin.com/shareArticle?mini=true&title=Why+AI+Engineers+Are+Moving+Beyond+LangChain+to+Native+Agent+Architectures&url=https%3A%2F%2Ftowardsdatascience.com%2Fwhy-ai-engineers-are-moving-beyond-langchain-to-native-agent-architectures%2F"
    },
    {
      "type": "external",
      "href": "https://x.com/share?text=Why+AI+Engineers+Are+Moving+Beyond+LangChain+to+Native+Agent+Architectures&url=https%3A%2F%2Ftowardsdatascience.com%2Fwhy-ai-engineers-are-moving-beyond-langchain-to-native-agent-architectures%2F"
    },
    {
      "type": "external",
      "href": "https://www.youtube.com/c/TowardsDataScience"
    },
    {
      "type": "external",
      "href": "https://www.threads.net/@towardsdatascience"
    },
    {
      "type": "external",
      "href": "https://bsky.app/profile/towardsdatascience.com"
    },
    {
      "type": "external",
      "href": "https://thenewstack.io"
    },
    {
      "type": "external",
      "href": "https://roadmap.sh"
    },
    {
      "type": "external",
      "href": "https://insightmediagroup.io/creator-network"
    }
  ],
  "repair_version": 2,
  "repaired_at": "2026-10-20T17:30:10Z",
  "source_url": "https://towardsdatascience.com/why-ai-engineers-are-moving-beyond-langchain-to-native-agent-architectures/",
  "delivery_status": "unverified",
  "discovery_status": "http_403",
  "missing_reason": "源页面未重新核验:http_403；已按保留正文补采图片",
  "repair_error": "",
  "actual_video_files": [],
  "expected_saved_body_images": 4,
  "image_discovery": "saved_markdown",
  "source_body_markdown": "![Revisit consent button](https://cdn-cookieyes.com/assets/images/revisit.svg)\nWe value your privacy\nWe 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.\nCustomise Reject All Accept All\nCustomise Consent Preferences ![](https://cdn-cookieyes.com/assets/images/close.svg)\nWe use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.\nThe 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\nNecessaryAlways Active\nNecessary 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.\n  * Cookie\nBCTempID\n  * Duration\n10 minutes\n  * Description\nNo description available.\n\n\n  * Cookie\n__cf_bm\n  * Duration\n1 hour\n  * Description\nThis cookie, set by Cloudflare, is used to support Cloudflare Bot Management. \n\n\n  * Cookie\nAWSALBCORS\n  * Duration\n7 days\n  * Description\nAmazon Web Services set this cookie for load balancing.\n\n\n  * Cookie\n_cfuvid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to track users across sessions to optimize user experience by maintaining session consistency and providing personalized services\n\n\n  * Cookie\nli_gc\n  * Duration\n6 months\n  * Description\nLinkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes.\n\n\n  * Cookie\n__hssrc\n  * Duration\nsession\n  * Description\nThis 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.\n\n\n  * Cookie\n__hssc\n  * Duration\n1 hour\n  * Description\nHubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie.\n\n\n  * Cookie\nwpEmojiSettingsSupports\n  * Duration\nsession\n  * Description\nWordPress 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.\n\n\n  * Cookie\nBCSessionID\n  * Duration\n1 year 1 month 4 days\n  * Description\nBlueconic sets this cookie as a unique identifier for the BlueConic profile.\n\n\n  * Cookie\n_octo\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nlogged_in\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\n__Secure-YEC\n  * Duration\npast\n  * Description\nYouTube sets this cookie to stores the user's video player preferences using embedded YouTube video\n\n\n  * Cookie\n__eoi\n  * Duration\n6 months\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTGCORS\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\nlogin-status-p\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nAWSALBTG\n  * Duration\n7 days\n  * Description\nNo description available.\n\n\n  * Cookie\ncsrf_token\n  * Duration\nsession\n  * Description\nNo description available.\n\n\n  * Cookie\ntoken_v2\n  * Duration\n1 day\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nD\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nPHPSESSID\n  * Duration\nsession\n  * Description\nThis 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.\n\n\n  * Cookie\nVISITOR_PRIVACY_METADATA\n  * Duration\n6 months\n  * Description\nYouTube sets this cookie to store the user's cookie consent state for the current domain. \n\n\n  * Cookie\ncookietest\n  * Duration\nsession\n  * Description\nThe cookietest cookie is typically used to determine whether the user's browser accepts cookies, essential for website functionality and user experience.\n\n\n  * Cookie\n__Host-airtable-session\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\n__Host-airtable-session.sig\n  * Duration\n1 year\n  * Description\nThis cookie is used to enable us to integrate the services of Airtable.\n\n\n  * Cookie\nm\n  * Duration\n1 year 1 month 4 days\n  * Description\nStripe sets this cookie for fraud prevention purposes. It identifies the device used to access the website, allowing the website to be formatted accordingly.\n\n\n  * Cookie\nBIGipServer*\n  * Duration\nsession\n  * Description\nMarketo 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. \n\n\n  * Cookie\n__cfruid\n  * Duration\nsession\n  * Description\nCloudflare sets this cookie to identify trusted web traffic.\n\n\n  * Cookie\n_GRECAPTCHA\n  * Duration\n6 months\n  * Description\nGoogle Recaptcha service sets this cookie to identify bots to protect the website against malicious spam attacks.\n\n\n  * Cookie\n__Secure-YNID\n  * Duration\n6 months\n  * Description\nGoogle cookie used to protect user security and prevent fraud, especially during the login process.\n\n\n  * Cookie\ncookieyes-consent\n  * Duration\n1 year\n  * Description\nCookieYes 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.\n\n\nFunctional\nFunctional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.\n  * Cookie\nlidc\n  * Duration\n1 day\n  * Description\nLinkedIn sets the lidc cookie to facilitate data center selection.\n\n\n  * Cookie\nbrw\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nbrwConsent\n  * Duration\n5 minutes\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nWMF-Uniq\n  * Duration\n1 year\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nloom_anon_comment\n  * Duration\n1 year\n  * Description\nNo description available.\n\n\n  * Cookie\nloom_referral_video\n  * Duration\nsession\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nVISITOR_INFO1_LIVE\n  * Duration\n6 months\n  * Description\nA cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface.\n\n\n  * Cookie\nyt-remote-connected-devices\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nytidb::LAST_RESULT_ENTRY_KEY\n  * Duration\nNever Expires\n  * Description\nThe 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.\n\n\n  * Cookie\nyt-remote-device-id\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to store the user's video preferences using embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-name\n  * Duration\nsession\n  * Description\nThe yt-remote-session-name cookie is used by YouTube to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\nyt-remote-fast-check-period\n  * Duration\nsession\n  * Description\nThe yt-remote-fast-check-period cookie is used by YouTube to store the user's video player preferences for embedded YouTube videos.\n\n\n  * Cookie\nyt-remote-session-app\n  * Duration\nsession\n  * Description\nThe yt-remote-session-app cookie is used by YouTube to store user preferences and information about the interface of the embedded YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-available\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-available cookie is used to store the user's preferences regarding whether casting is available on their YouTube video player.\n\n\n  * Cookie\nyt-remote-cast-installed\n  * Duration\nsession\n  * Description\nThe yt-remote-cast-installed cookie is used to store the user's video player preferences using embedded YouTube video.\n\n\n  * Cookie\ncp_session\n  * Duration\n3 months\n  * Description\nCodepen sets this cookie for Help systems found in the website.\n\n\n  * Cookie\nloid\n  * Duration\n1 year 1 month 4 days\n  * Description\nThis cookie is set by the Reddit. The cookie enables the sharing of content from the website onto the social media platform.\n\n\nAnalytics\nAnalytical 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.\n  * Cookie\n__hstc\n  * Duration\n6 months\n  * Description\nHubspot 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).\n\n\n  * Cookie\nhubspotutk\n  * Duration\n6 months\n  * Description\nHubSpot 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.\n\n\n  * Cookie\n_ga\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle 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.\n\n\n  * Cookie\n_ga_*\n  * Duration\n1 year 1 month 4 days\n  * Description\nGoogle Analytics sets this cookie to store and count page views.\n\n\n  * Cookie\n__Host-psifi.analyticsTrace\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n__Host-psifi.analyticsTraceV2\n  * Duration\n6 hours\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\n_gh_sess\n  * Duration\nsession\n  * Description\nGitHub sets this cookie for temporary application and framework state between pages like what step the user is on in a multiple step form.\n\n\n  * Cookie\nYSC\n  * Duration\nsession\n  * Description\nYSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages.\n\n\n  * Cookie\najs_anonymous_id\n  * Duration\n1 year\n  * Description\nThis cookie is set by Segment to count the number of people who visit a certain site by tracking if they have visited before.\n\n\n  * Cookie\nvuid\n  * Duration\n1 year 1 month 4 days\n  * Description\nVimeo installs this cookie to collect tracking information by setting a unique ID to embed videos on the website. \n\n\nPerformance\nPerformance 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.\n  * Cookie\nAWSALB\n  * Duration\n7 days\n  * Description\nAWSALB is an application load balancer cookie set by Amazon Web Services to map the session to the target.\n\n\n  * Cookie\nacq\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nacq.sig\n  * Duration\npast\n  * Description\nDescription is currently not available.\n\n\n  * Cookie\nptc\n  * Duration\n2 years\n  * Description\nNo description available.\n\n\nAdvertisement\nAdvertisement 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.\n  * Cookie\nmuc_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to collect user behaviour and interaction data to optimize the website.\n\n\n  * Cookie\nguest_id_marketing\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\nguest_id_ads\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter sets this cookie to identify and track the website visitor.\n\n\n  * Cookie\npersonalization_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter 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.\n\n\n  * Cookie\nguest_id\n  * Duration\n1 year 1 month 4 days\n  * Description\nTwitter 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.\n\n\n  * Cookie\nbcookie\n  * Duration\n1 year\n  * Description\nLinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser IDs.\n\n\n  * Cookie\n__Secure-ROLLOUT_TOKEN\n  * Duration\n6 months\n  * Description\nYouTube 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.\n\n\n  * Cookie\nyt.innertube::nextId\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nyt.innertube::requests\n  * Duration\nNever Expires\n  * Description\nYouTube sets this cookie to register a unique ID to store data on what videos from YouTube the user has seen.\n\n\n  * Cookie\nsession_tracker\n  * Duration\nsession\n  * Description\nThis cookie is set by the Reddit. This cookie is used to identify trusted web traffic. It also helps in adverstising on the website.\n\n\n  * Cookie\nedgebucket\n  * Duration\nsession\n  * Description\nReddit sets this cookie to save the information about a log-on Reddit user, for the purpose of advertisement recommendations and updating the content.\n\n\n  * Cookie\ndid\n  * Duration\n1 year\n  * Description\nArbor sets this cookie to show targeted ads to site visitors.This cookie expires after 2 months or 1 year.\n\n\nUncategorised\nOther uncategorised cookies are those that are being analysed and have not been classified into a category as yet.\nNo cookies to display.\nReject All Save My Preferences Accept All\nToggle Search[](https://towardsdatascience.com/)Toggle Mobile Navigation\n[](https://towardsdatascience.com/)\nPublish AI, ML & data-science insights to a global community of data professionals.\nSign in[Submit an Article](https://write.insightmediagroup.io)\n[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/)\n* * *\n[Write For TDS](https://towardsdatascience.com/submissions/)\n[LinkedIn](https://www.linkedin.com/company/towards-data-science/)[X](https://x.com/TDataScience)Toggle Search\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\n# Why AI Engineers Are Moving Beyond LangChain to Native Agent Architectures\nFrameworks accelerated the first wave of LLM apps, but production demands a different architecture.\n[Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/)\nApril 30, 20267 min read\n![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/ChatGPT-Image-Apr-26-2026-12_48_58-AM.jpg)\nImage by author (Generated with ChatGPT)\nRecently, I've been sitting closely with this topic, and it brought back some experiences from working on a couple of projects.\nTake 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.\nYou spend an afternoon staring at logs that tell you _what_ happened but not _why_.\nThen 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.\nThat is not a bug report; it is a wakeup call about the architecture.\nFrameworks 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.\nBut 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.\nThis post is about that cost and why more engineers, after discovering it, are now building the orchestration layer by themselves.\nLearn this step by step with the interactive [AI Agents](https://roadmap.sh/ai-agents) roadmap.\n## Give LangChain Its Credit\nI remember watching a colleague build a working RAG pipeline in about forty minutes sometime in early 2023.\nHe went from the vector store through the retrieval chain, prompt templates, and the LLM call, all connected by lunchtime.\nSix months prior, that would have been at least a two-week project.\nCome to think of it, that's actually how and why LangChain spread so fast. \nMost 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. \nLangChain showed up with answers that were modular, composable, and documented, and of course, teams grabbed them immediately, including mine.\nSo 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.\n## Where the Abstraction Breaks\nWhen 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.\nLangChain applies that same idea to LLM orchestration. It hides a lot of what's happening inside your system so you can move faster.\nBut production AI systems demand something that cuts against that: **clarity**. \nYou need to know exactly what your system did, in what order, with what inputs, and why. Not roughly. Exactly.\nAbstractions trade that visibility for speed. That’s a fair trade at first, until the hidden complexity becomes the very thing you need to understand.\nAnd it shows up in more ways than one.\n**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.\nI 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.\n**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.\n**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.\nWho created this information, when, and is it still valid?\nOne agent updates memory, another reads a stale version, and the coordinator makes a decision based on context that no longer matches reality.\nFramework-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.\n**Latency accumulates:** Every abstraction layer adds overhead through serialization, validation, callback firing, and internal routing that runs whether you need it or not.\nIn 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.\nThe 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.\nAt some point, you have to ask whether that overhead is still worth what it buys you.\nNone 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.\n## So What Does \"Building It Yourself\" Actually Look Like?\n\"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.\nState 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.\nThe model call is your code, which means you can instrument it directly and trace what matters.\nSure, 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.\nLet'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.\nMore design work upfront means less firefighting later.\n···\nI'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.\nTo me, that’s not progress.\nIf 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.\nThe 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.\nMost 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.\"\nThat's the moment to rethink the architecture, not after six months of piling on workarounds.\nFrameworks are how knowledge transfers in a new field. LangChain made LLM application development accessible for a generation of engineers. That contribution is real.\nBut 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.\" \nNot because frameworks are bad, but because owning your architecture means you know what’s happening under the hood.\nThe engineers building the most reliable production AI systems aren't the ones with the most sophisticated tooling.\nThey'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.\nThat clarity is hard to maintain through thick layers of abstraction.\n···\n## Final thoughts\nAbstraction 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.\nThat moment comes earlier than you expect, usually triggered by a debugging session or a monitoring ask rather than a planning meeting.\nState 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.\nTreat orchestration as a real architectural decision. Pick it on purpose, with the tradeoffs visible.\nThe 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.\n···\n## Before you go!\nI write more about the real engineering decisions behind AI systems, where abstractions help, where they hurt, and what it takes to build reliably. \nYou can [**subscribe to my newsletter**](https://thatcsguy.substack.com/?r=79lldp&utm_campaign=pub-share-checklist) if you'd like more of that.\n**Connect With Me**\n  * [LinkedIn](http://www.linkedin.com/in/nwekebenjamin)\n  * [Substack](https://thatcsguy.substack.com/)\n\n\n## Register Now to Continue Reading\n### Unlock Towards Data Science with a Free Account\nAll articles on Towards Data Science are available to registered users. Create a free account today to access this article and thousands more.\nRegister for freeSign in to your account\n* * *\n![](https://assets.insightmediagroup.io/media/1787657271062_x78p7k.jpeg)\nWritten By\n## [Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/)\nBenjamin 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.\n[See all from Benjamin Nweke](https://towardsdatascience.com/author/benjaminnweke/)\n[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/)\nShare This Article\n  * [](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)\n  * [](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)\n  * [](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)\n\n\nTowards Data Science is a community publication. Submit your insights to reach our global audience and earn through the TDS Author Payment Program.\n[Write for TDS](https://towardsdatascience.com/submissions/)\n## Related Articles\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2021/06/03pVXwsQ9tb-d3Xrh-scaled.jpg)](https://towardsdatascience.com/recreating-an-ml-masters-degree-with-online-courses-8f90a7088cf8/)\n## [Recreating an ML Master's degree with Online Courses](https://towardsdatascience.com/recreating-an-ml-masters-degree-with-online-courses-8f90a7088cf8/)\n[Deep Learning](https://towardsdatascience.com/category/artificial-intelligence/deep-learning/)\nUse online courses to create your curriculum\n[Pascal Janetzky](https://towardsdatascience.com/author/pascaljanetzky/)\nJune 14, 20217 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2021/01/1_UwsI_zuBVkMJSMKbKgsvg.jpeg)](https://towardsdatascience.com/recognizing-cats-and-dogs-with-tensorflow-105eb56da35f/)\n## [Recognizing Cats and Dogs With TensorFlow](https://towardsdatascience.com/recognizing-cats-and-dogs-with-tensorflow-105eb56da35f/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nCreate a neural network using TensorFlow to recognize cats and dogs\n[Patrick Kalkman](https://towardsdatascience.com/author/pkalkman/)\nJanuary 11, 202110 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2022/07/1YpWbqiMz5wNQIfM09GRnAA-scaled.jpeg)](https://towardsdatascience.com/sort-pandas-df-5748eaadcd4f/)\n## [How To Sort Pandas DataFrames](https://towardsdatascience.com/sort-pandas-df-5748eaadcd4f/)\n[Machine Learning](https://towardsdatascience.com/category/artificial-intelligence/machine-learning/)\nSorting pandas DataFrames using one or more columns\n[Giorgos Myrianthous](https://towardsdatascience.com/author/gmyrianthous/)\nJuly 5, 20225 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2017/06/1fhY4NoaIfexwj3PdVHYQyQ.png)](https://towardsdatascience.com/why-hire-an-ai-consultant-50e155e17b39/)\n## [How to Hire an AI Consultant](https://towardsdatascience.com/why-hire-an-ai-consultant-50e155e17b39/)\n[Artificial Intelligence](https://towardsdatascience.com/category/artificial-intelligence/)\nSo, you know you need some machine learning/AI development. Why not just do it yourself? Well, the short answer is that specialists have...\n[Daniel Shapiro, PhD](https://towardsdatascience.com/author/lemaysolutions/)\nJune 27, 201711 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/04/image.jpeg)](https://towardsdatascience.com/deep-dive-into-context-engineering-for-ai-agents/)\n## [Context Engineering for AI Agents: A Deep Dive](https://towardsdatascience.com/deep-dive-into-context-engineering-for-ai-agents/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nHow to optimize context, a precious finite resource for AI agents\n[Clara Chong](https://towardsdatascience.com/author/clarachong13/)\nApril 7, 20267 min read\n  * [![](https://assets.insightmediagroup.io/media/1788826212972_oh160i.jpg)](https://towardsdatascience.com/how-to-design-architectural-guardrails-around-ai-agents/)\n## [How to Design Architectural Guardrails Around AI Agents](https://towardsdatascience.com/how-to-design-architectural-guardrails-around-ai-agents/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nAgent design patterns every data engineer must know\n[Thuwarakesh Murallie](https://towardsdatascience.com/author/thuwarakesh/)\nSeptember 29, 202612 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/07/factor_cube.jpg)](https://towardsdatascience.com/stop-ranking-agent-configs-by-average-score/)\n## [Stop Ranking Agent Configs by Average Score](https://towardsdatascience.com/stop-ranking-agent-configs-by-average-score/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nBest-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.\n[Doster Esh](https://towardsdatascience.com/author/doster.esh/)\nJuly 6, 202613 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2025/12/812d5a6c-49d8-4c98-b338-542ea67ba67c.jpeg)](https://towardsdatascience.com/production-ready-llms-made-simple-with-nemo-agent-toolkit/)\n## [Production-Ready LLMs Made Simple with the NeMo Agent Toolkit](https://towardsdatascience.com/production-ready-llms-made-simple-with-nemo-agent-toolkit/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nFrom simple chat to multi-agent reasoning and real-time REST APIs\n[Mariya Mansurova](https://towardsdatascience.com/author/miptgirl/)\nDecember 31, 202522 min read\n  * [![](https://assets.insightmediagroup.io/media/wp-content/uploads/2026/08/Context-Compiler.jpg)](https://towardsdatascience.com/coding-agents-dont-need-bigger-context-windows-they-need-a-context-compiler/)\n## [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/)\n[Agentic AI](https://towardsdatascience.com/category/artificial-intelligence/agentic-ai/)\nMost 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.\n[Emmimal P Alexander](https://towardsdatascience.com/author/emmimalp.alexander/)\nAugust 1, 202613 min read\n\n\n  * [YouTube](https://www.youtube.com/c/TowardsDataScience)\n  * [X](https://x.com/TDataScience)\n  * [LinkedIn](https://www.linkedin.com/company/towards-data-science/)\n  * [Threads](https://www.threads.net/@towardsdatascience)\n  * [Bluesky](https://bsky.app/profile/towardsdatascience.com)\n\n\n[](https://towardsdatascience.com/)\nYour home for data science and AI. The world's leading publication for data science, data analytics, data engineering, machine learning, and artificial intelligence professionals.\nSubscribe 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/)\n© Insight Media Group, LLC 2026•[The New Stack](https://thenewstack.io)•[roadmap.sh](https://roadmap.sh)•[Creator Network](https://insightmediagroup.io/creator-network)\n####  Recommended Articles \nClose\n  * [ ![](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\")\n  * [ ![](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\")\n  * [ ![](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\")\n  * [ ![](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?\")\n\n\n",
  "body_base_path": "attachments/00a265af0151/pages/",
  "body_markdown_path": "attachments/00a265af0151/pages/archived-body.md",
  "local_html": "attachments/00a265af0151/pages/archived-body.html",
  "body_source": "prior_capture"
}