
🌉 Interrupt, The Agent Conference by LangChain, returns to San Francisco March 24 + 25 🎟️ Early Bird tickets available until Dec 7th Info + RSVP: interrupt.langchain.com/
✓Own your intelligence. Makers of LangSmith, @LangChain_OSS, and @LangChain_JS.

🌉 Interrupt, The Agent Conference by LangChain, returns to San Francisco March 24 + 25 🎟️ Early Bird tickets available until Dec 7th Info + RSVP: interrupt.langchain.com/

🙋 Have questions that you want the LangChain Academy team to answer in future videos? 💬 Let us know below!

LangChain was ranked #79 on the AI 100 list by @BessemerVP and @NewcomerMedia. We are honored to be featured as one of the most promising private AI companies today, and look forward to continuing our mission to help every organization own their intelligence. ai100.newcomer.co/


Under the hood: ✅ A sandbox with Office tools + our brand kit ✅ Skills for sales stages and templates ✅ Memory across each deal ✅ Scheduled runs for pre-meeting briefs Built on Managed Deep Agents.

Deals where a rep sent a GTM Agent artifact moved to a later stage 47% of the time. Matched deals without one: 16%. ✅ 1,540 artifacts in 12 weeks ✅ 46% followed by a customer call within 14 days ✅ 337 rep hours saved on artifacts sent to customers langchain.com/blog/gtm-agent…

🚀 Just Announced! Lenny’s Newsletter subscribers now get one free year of LangSmith Plus.

trace data contains a ton of valuable insights to mine, but also a lot of sensitive data you need to manage carefully these three new controls stack up nicely to enable responsible trace governance: - by default, trace everything to langsmith, but restrict access to inputs/ouputs. this lets people see number of calls, tools getting invoked, etc; but restricts any sensitive info - when a customer complains, get their permission and enable a small set of engineers to see inputs/outputs for their bad traces sounds simple/basic/boring, but security and governance is really important to get right for data like traces which can contain sensitive info!

💻 Engineers get the visibility they need to improve agents. 🔒 Security teams keep sensitive data limited to authorized users. Our new trace access controls are now available in LangSmith Enterprise plans. langchain.com/blog/protect-s…

We’re adding 3 new controls in LangSmith to help your team manage sensitive trace data. 1️⃣ Control who can see trace inputs and outputs 2️⃣ Manage team-by-team permissions with user groups 3️⃣ Set trace-level access policies using metadata

knowing how to build proactive agents means defining how those agents can act on their own. proactive agents can handle - - real-world events, like a new email or a newly opened pull request. - schedules set by the developer, like a nightly job that updates the agent's memory or a weekly sweep for stale pull requests. - schedules set by the agent, like a reminder to follow up on a thread tomorrow, or a daily brief a user asked for. these triggers mean the agent can perform actions far beyond what's possible with a simple chat interface (and makes them much more valuable in an organizational context). having the right toolkit to get there is a pretty crucial piece of the puzzle! take managed deep agents for a spin, where proactivity is baked in as first principles: langch.in/mda

Learn how we use memory and UX to keep our proactive agents helpful without being annoying in @sydneyrunkle's new blog ⤵️

Running a workshop with @ishaan_lal1 today on Managed Deep Agents, come along to see what the future of agents looks like !

.@ishaan_lal1 answers one of the most frequently asked questions during our LangChain Academy workshops at Interrupt. What is an Agent vs. a Deep Agent vs. a Managed Deep Agent? 🙋 Have any other LangChain questions you want our team to answer? 💬 Let us know below!

Happening today!

On December 3rd, learn how to build agents that can find and apply the knowledge needed for complex, regulated workflows. RSVP for our live session ⤵️ events.langchain.com/webinar…