PM @LangChain building Managed Deep Agents. I post demos, code, and what breaks. prev @plotly nathan (at) drezner (dot) xyz

Montréal, Québec
Joined May 2013
Browser use w/ @LangChain + @typesafeai's Jev! Really fun to build. ... I found it's excellent at playing the Wikipedia Game. (But, it's also great at "folding laundry" type tasks, like finding cheap flights.)
9
15
5
107
62,594
nathan drezner retweeted
What’s new in Managed Deep Agents 0.9? And how can you get started? Watch @VictorMoreira16's keynote from Interrupt London for an inside look. youtu.be/Wb3hQaG_xf0
8
2
1
36
15,268
nathan drezner retweeted
How do you build an adaptive company harness? If you've built a company megazoid agent, every team will end up wanting something different from it. E.g. finance needs billing skills while the platform team needs incident MCP server. You will inevitably face a context bloat problem when your agent loads hundreds of tools/skills/resources that have nothing to do with the request Solution is to use a factory! In Managed Deep Agents you can build your agent from a function instead of a fixed definition. That function runs at the start of every run with all relevant context, so you can load a different model/skills/tools/sandbox/memory/etc. to suit each team's needs
26
7
3
78
5,081
there are a lot of interesting takes in this post, but the modern computing metaphor is especially good. we're watching traditional computing get reinvented in real time, but the core constructs are still there: - the model is the cpu - the harness is the os - skills and plugins are the apps owning your harness layer means you control the ecosystem that plugs into your product. that's what makes the harness one of the most interesting places to work on right now. managed deep agents is an agent os built to be distributed across an organization. we're building the harness to be an even stronger os for multiplayer, long-term learning, self-initiation, and async work. langch.in/mda
I spent 48 hours in SF hanging out with billionaires, data labs and AI founders and execs running $1B to $100B companies. My observations: 1. Sooo MANY stories of data brokers making like $2M a WEEK selling company data to labs. I can't tell if it's the beginning or a bubble, and I kept wondering which niches are left. Digging into it actively. 2. At dinner, someone asked the table, "If a new model drops next month, does your company get better or worse?" HALF the table went quiet! I think that's the best question to ask about any AI startup right now. 3. The bar people talk about now is hitting $1B in revenue in 12 months (I guess that's the new unicorn?). What I didn't hear much about is retention. AI revenue can come in fast and leave fast, and I think we're going to see a lot of stories of AI companies with huge revenue and terrible retention. 4. It's pretty clear we're living through the reinvention of the computer. The model is the CPU, the harness is the operating system, and skills and plugins are the apps. Thinking about it that way makes it easier to see where the whitespace is. 5. We're maybe 12 months from an agent that can watch you work for a week and then do your job without any instructions. The screen recording plus agent memory plus local model combination makes this possible right now. 6. Agent harnesses feel like the new GPT wrappers, in a good way, especially vertical ones. The best teams I talked to treat the model as swappable. One founder walked me through routing different models to different jobs: one for taste and visuals, a cheaper one for the everyday stuff, another for text. They use prompts they can move across models over fine-tuning, and A/B test the output on what users actually do with it: do they edit it, export it, share it? A vertical harness is basically four things: the connectors for that industry's data, evals written by people who know the work, rules for what the agent can and can't touch, and a clean screen for a human to review. The model is maybe 20% of it. 7. There's a lot of reverse engineering going on/cloning going on more than I've ever seen. People are decompiling software and rebuilding it with agents, and someone showed a suite of like 10 apps that are worth $5B+ each all that he cloned open source. Me and everyone are still thinking through what it means when software gets this easy to copy. 8. My guess is the value moves to data. If the software can be rebuilt quickly, what's worth paying for in a legacy SaaS company is the years of customer data and workflows inside it. Some SaaS companies are secretly data companies. Gets me thinking about how do you truly value data for this saas companies? Like if we were buying these dying saas companies at 2x ARR before (as example), maybe there is a better metric. Idk, just thinking out loud here. 9. It feels like a good chunk of legacy software won't make it to the agentic era, especially anything built around people clicking through a lot of screens. 10. Every company I talked to wants to pipe its internal data into one place and expose it to agents through MCP. Then they look at the data and realize it's a mess: five versions of the same customer, old Slack channels, PDFs nobody can search. Cleaning that up feels like a big consulting opportunity! 11. A lot of founders are building the basic building blocks for agents: APIs, data layers and tools. Some of the companies I saw barely have a UI because the main user is an agent. I really believe the startups that build primitives to this agentic era will do extremely well. Building blocks is the best way to think about it. 12. Labs can get plenty of training data, but it's harder to get real examples of agents failing inside companies. Whoever has those logs has something valuable. 13. Someone running a big consumer company told me the next fight is over memory. The model that remembers the most about you wins, and the smartest model matters less than people think. 14. Physical AI came up a lot. Astra I think was the first model that got people into AI can actually do CAD, and I think a lot of people are thinking what does vibe manufacturing really look like. The line I keep thinking about came from a robotics founder: the hardest problems in AI are deployment problems now, not research problems. Their robots work on their own, call a human when they get stuck, and every one of those calls becomes training data. 15. Cybersecurity companies are having a moment and are actually cool companies to build now, especially the ones that clean up after a breach. Every agent with access to your systems is a new door into your company, and a lot of those doors were left open. 16. Some startups are worth more dead than alive now. A shutdown company with 5 years of Slack, email and code can get paid for licensing all of it. I wouldn't be surprised if founders start factoring that into when they shut down. 17. People are starting to talk about monetizing the agent web. It feels really early, but when the most popular user of the internet is an agent, what startups should you be building? 18. I think agent insurance is coming. Once an agent makes an expensive mistake, insurers will want audits before they cover anyone. 19. Several people said the hire they want most is someone with taste who can write evals. The models are getting good at generating ideas, so the hard part is judging which ones are good. 20. New trend I observed: startup raises VC, uses venture dollars to become a creator, startup fails, founder falls back on being a full-time creator and incubates other products bootstrapped. 21. Getting SIGNIFICANT distribution is HARD right now. Founders are sponsoring buses, buying billboards like crazy and throwing parties with famous DJs to get noticed. Kinda feels dotcom era in that sense. Attention is what's scarce! The growth guy going viral sharing his UGC strategy from Wispr Flow is a good example. It's the sauce everyone wants, and I truly believe there are probably only 50 people on the planet who know how to scale these types of businesses efficiently in this era. Always good to get that dose of SF. I felt sooo lucky to have such an incredible trip during such an incredible time in building businesses. Surreal in so many ways. Happy to be home and locked in. Until next time!
2
4
1,367
our internal design agent is fantastic - it's one of those internal tools where whenever I use it, it makes me smile because it's able to build things I hadn't even thought of yet. the managed deep agents team (along with our applied AI team including @amal_irgashev) have been building it on top of managed deep agents and it's been a seamless transition overall. can't wait for amal's webinar and if you're not registered you should definitely sign up!
our design agent at @LangChain has shipped 3,000+ assets since august, and posts with its work pulled ~4.5M views on socials (it made this promo too) it’s become the design brain for the whole org. decks, diagrams, ad creatives, launch films and more, all made from slack we encoded our designers’ judgment into its skills, a design wiki and brand checks that run on every render, so it knows what good looks like for us then we built a custom media harness around it: a headless photoshop, a shared visual canvas (thanks @paper), video tools like @HyperFrames_ plus our own animation engine, our brand assets and a library of design references it runs on Managed Deep Agents, which abstracts away a ton of infra including sandboxes, agent memory, slack integration, scheduling and more. we are going through the architecture, use cases and impact live at our oct 28 webinar 👇 events.langchain.com/gtm-eng…
1
1
6
282
This is a key design thesis for Managed Deep Agents! Model agnosticity makes experimentation possible, cost control easier. Build different agents on top of different models, or even build a single agent that can route requests to different models depending on user request, identity, and more (our new dynamic agent pattern is great for this)
LangChain’s Managed Deep Agents has one huge advantage over the managed agent harnesses from OpenAI and Anthropic: model independence. You can choose between models from different providers without changing your underlying agent architecture.
1
4
129
nathan drezner retweeted
4. Fork: start from our open source software factory Own the code without starting from zero langch.in/openswe
There are basically three ways to build a software factory right now: 1. Build: build your own factory infrastructure around coding agents 2. Buy: use a factory platform like Warp or Factory or Port to name a few 3. Delegate: skip the factory infrastructure and use an always-on agent like @bot or a dot as the factory The third is by far the easiest to set up and has many of the properties of a factory out of the box. It can coordinate work, update your ticketing system, ask for clarification, etc. But it’s missing a defining feature of software factories, a system you can measure, iterate on, and continuously improve.
3
3
1
68
12,128
nathan drezner retweeted
How do you build a company harness? We've built internal agents at LangChain across marketing, sales, and engineering. The results have been incredible but these agents were NOT easy to get right. We spent a ton of time solving the problems that come with a multiplayer harness. Every agent team landed on the same core primitives: - It lives where people already work (for us that's Slack) - It knows who's asking and acts OBO that person for some services and with its own identity for others - It has memory, scoped globally and/or at the user level - It runs code in a sandbox where authenticated CLIs and scripts just work (gh, curl, your internal APIs) - Large % of its runs are scheduled rather than explicitly invoked by someone (ambient agents!!) It became clear we needed one shared place for these primitives, so we built Managed Deep Agents. In my humble opinion it is the easiest way to build a company harness today Our docs are very agent-friendly, point them here to get started: langch.in/mda
16
13
3
141
22,475
approve / reject isn't a question sometimes your agent needs to actually ask you something. so let it: drop a few buttons in the slack thread ⏸️ keep going when you click ▶️ public beta in @LangChain Managed Deep Agents
4
1
9
6,902
here's the tool from this demo. the run waits at interrupt() until someone clicks, and the click comes back as its return value docs, so you can build something even more powerful: docs.langchain.com/langsmith…
2
109
nathan drezner retweeted
Steve Jobs emails Paul Rand March 2, 1996
47
106
52
4,716
968,490
it's not easy to properly secure production agents! we've spent a lot of time building great primitives for Managed Deep Agents to make agents you ship secure by default 🔐 langch.in/mda
A walkthrough of how Managed Deep Agents uses sandbox proxies to keep your credentials safe. langch.in/mda
2
1
7
2,698
nathan drezner retweeted
Most of the interesting agent harness work is happening at intersection of harness and infra: 1/ dreaming 2/ async subagents 3/ heartbeats 4/ letting agent schedule reminders Part of reason im so bullish on managed agents platforms! All of these in managed deep agents!
171
35
12
493
25,797
Drop a file in Slack, get a slide deck back in the same thread. Files upload to integrated Sandboxes in @LangChain Managed Deep Agents, where the agent can iterate on an output and send back a response in a @SlackHQ thread. Setup is a Slack channel and a Sandbox file. Take it for a spin: langch.in/slack-files
1
3
8
364
nathan drezner retweeted
Claude Platform traces can now be sent to LangSmith through OpenTelemetry. Export from Claude Managed Agents, the Messages API, or the Claude SDKs with native OTel support. Traces show up in LangSmith so you can inspect every step and improve agent performance. It’s available now in public beta. Docs: docs.langchain.com/langsmith…
Now in public beta, Claude Platform can send OpenTelemetry traces from the Messages API, Claude Managed Agents, and the Claude SDKs to your observability stack.
12
8
1
66
9,283
nathan drezner retweeted
Or don't pay, and use our open-source software factory instead: langch.in/openswe
If your company or startup is running engineering with everyone using their own license of Codex/CC then you're going to be completely left behind by fast moving teams who are using cloud-based agents. Local dev is like banging rocks together and grunting versus being on a rocket. Seriously, just pay the money for something like @DevinAI, @AmpCode, @FactoryAI, etc. Do NOT try to build your own "code factory". Props to @DaleSpoonemore for taking @HelloUntangle to the next level on this. Fun to watch.
8
18
339
63,416