Lance Martin
Software Engineer & Educator, LangChain. On 1 show, 1 appearance. The Shows tab opens the full record on each.
engineerscientistauthor@RLanceMartin ↗LinkedIn ↗rlancemartin.github.io ↗
Lance Martin builds open-source agent frameworks and educational curricula at LangChain, having created LangChain Academy, the "RAG From Scratch" series, and Open Deep Research. Holding a Ph.D. from Stanford University, he previously worked as a perception tech lead on autonomous vehicle systems at Uber ATG, Ike, and Nuro.
1shows
1appearances
21statements
8resolved
6supported
1contradicted
75%fully supported
1said about them ↓ Everything Lance Martin said on any show that made the record, most notable first. Each card names its show and opens the statement there.
Martin: AI engineers must continuously remove scaffolding as underlying models improve
“We should be adding structure necessary to get things to work today, but keeping an eye on improving models and keep, but keeping a close eye on models, improving rapidly and removing structure in order to un-bottleneck ourselves.”
Martin: OpenDeep Research is the top-ranked open-source Deep Research agent
“OpenDeep Research is a deep research agent that I've been working on for about a year, and it's now, according to Deep Research Spence, the best performing Deep Research agent at least on that particular benchmark. So it's pretty good. Listen, it's not as good…”
Martin: Multi-agent systems excel at parallel read-only tasks, not writing tasks
“I like the take that apply multi-agents to problems that are easily parallelizable, that are read-only, for example, context gathering for deep research, and do, like, the final quote-unquote write, in this case report writing, at the end. I think this is tric…”
Martin: Tool-based search with llms.txt beats maintaining vector indexes
“You give an LLM access to simple files, file tools. In this case, I actually use an LLM.txt to help it out. So it can actually know what's in each file. It's extremely effective and much more simple and easy to maintain, easier to maintain than building an ind…”
Martin: Selective History Pruning Adds Unnecessary Complexity to Agent Scaffolding
“So I'm not sure I love the idea of kind of selectively trying to prune your message history when you're building an agent. It can add more logic than you need to manage within your kind of agent scaffolding or harness.”
Martin: Context caching solves cost and latency, but not context rot
“I do think an important and subtle point here is that caching doesn't solve the long context problem. So it, of course, solves the problem of, like, latency and cost, but if you still have a 100,000 tokens in context whether it's cached or not, the LM is utili…”
Lance Martin: Black-box agent abstractions break when underlying models evolve
“Agent abstractions are problematic because you don't know what's necessarily under the hood of the abstraction. You don't understand it. And if I was building, for example, you know, OpenDeep research with an abstraction, I wouldn't necessarily know how to rip…”
Martin: Agent architectures are simple conceptually but managing context is hard
“When you kind of put together an agent, it's just tool clawing a loop. It's relatively simple to lay out, but it's actually quite tricky to get it to work well. In a particular, managing context with agents is a hard problem.”
Lance Martin: Prompt engineering is a subset of context engineering
“Well, I think that, you know, prompt engineering is kind of a subset of context engineering.”
Martin: Claude Code operates entirely without codebase indexing
“Clock code doesn't do any indexing. It's just doing, quote unquote, agentic retrieval, just using simple tool calls, for example, using grep, to kind of poke around your files, no indexing whatsoever, and obviously works extremely well.”
Martin: Reading agent memory at scale is just a multi-step RAG pipeline
“Memory retrieval at large scale is just retrieval, right? I kind of view them as... In the case of sophisticated memory retrieval, it is just like a, you know, complex rag system in the same way we talked about with like Varun and building windsurf. It's kind …”
Manus: A typical AI agent task requires approximately 50 tool calls
“Manus put out a great piece talking about content engineering with Manus, and they made the point that the typical Manus task is like 50 tool calls.”
Anthropic: Typical production agents execute hundreds of tool calls per task
“Anthropics multi-agent research is another nice example of this. They mentioned that the typical production agent, and this is probably referring to Cloud Code, could be other agents that they've produced, is like hundreds of tool calls.”
Martin: A naive deep researcher loop consumed 500,000 tokens per run
“My deep researcher, for example, with the naive tool calling loop was using 500,000 tokens. It was like a dollar to two dollars per run.”
Martin: Agents should offload raw tool context to external storage
“Rather than just writing back the full context of your tool calls, which could be token heavy, write those to disk and you can write back a summary. It could be a URL, something so that the agent knows it's retrieved a thing. It can fetch that on demand, but y…”
Martin: Anthropic uses parallel sub-agents for research and single-shot final writing
“Anthropic reported on this too. So their deep researcher just uses parallelized subagents for research collation, and they do the writing in one shot at the end.”
Martin: Claude Code triggers context compaction at 95% of context window
“If you use Cloud Code, you hit that
Kind of, you know, you've hit 95% of the context window, and you're about to, and Cloud Code's about to perform compaction.”
Martin: Cognition's Devin uses a fine-tuned model for context summarization
“Devin uses a fine-tuned model for doing summarization within the context of coding.”
Martin: Claude Code uses zero automation for reading and writing memory
“For reading memories, they just suck in your Claude MDs every time. So every time you spin up Claude Claude code, it pulls in all your Claude MDs. For writing memories, The user specifies, hey, I want to save this to memory, and then CloudCode writes it to Clo…”
Martin: Agent memory pairs best with human-in-the-loop feedback
“Memory pairs really well with human in the loop. So for example, in my little email assistant, it's just an agent that runs my email, I have the opportunity to pause it before it sends off an email and correct it if I want, like, change the tone of this email,…”
Martin: The best open-source strategy pairs building tools with educational on-ramps
“I like this one, two punch of building a thing like open deep research, then creating a class so people can actually understand how to build it themselves. And I kind of like that build a thing, create an on-ramp for it.”
The other half of the tape: Lance Martin's own voice is left out of every number here. Other people bring the name up 1 time in 1 episode across the shows. every mention, with the transcript →
Who brings them up most Shawn Wang 1
Every mention by year
tap a year for its mentions
Latent Space 1
2025 1 mention in 1 episode
One line per show, most statements first. The link opens Lance's full record on that show: the calibration, argument clarity, speaking style and every statement made there.
| Show | Role there | Eps | Statements | Record | |
|---|---|---|---|---|---|
| LATENT SPACELEDGER | Software Engineer & Educator, LangChain | 1 | 21 | 75% 6/8 | full record on Latent Space → |