I'm increasingly convinced LangGraph beats Claude Plugins
Summary
The author shares their experience building a Claude Plugin for stock valuation, finding it increasingly difficult to handle errors and complexity. They are now considering switching to LangGraph as a more reliable solution for multi-step agent workflows.
Similar Articles
Are LangGraph agents and other agent frameworks becoming obsolete?
The author reflects on building many LangGraph agents and questions their necessity with new generative models, advocating for simpler single-agent solutions with MCP tools and controlled endpoints over complex predefined frameworks.
Learning LangGraph : A Journey Through Agents, Blackboards, and Bottlenecks
An educational article exploring LangGraph, covering agent architectures, the blackboard pattern, and common bottlenecks in building agent systems.
@LangChain: We built a plugin that traces every Claude Code session straight into LangSmith. Three commands, one JSON block, and ev…
LangChain released a plugin that logs all Claude Code sessions into LangSmith for debugging, with a quick three-command setup.
@LangChain: Improving agents The old way: Manually reading traces, looking for patterns, writing evals, and creating fixes. The bet…
This tweet contrasts the old manual approach to improving AI agents with a new automated method using LangSmith Engine, which cycles through tracing, eval, and fixes.
@LangChain: This agent drafts a cited VC investment memo in ~90 seconds for $0.40. 4 LangGraph nodes powered by the @Perplexity_AI …
LangChain demonstrates an agent that drafts a cited VC investment memo in ~90 seconds for $0.40 using the Perplexity Agent API and LangGraph, with four parallel research nodes and a synthesizer.