Topic
4 articles on LangGraph, written from production systems rather than documentation.
A second agent multiplies the coordination problem, not the capability. What decides whether it holds together is who owns the shared plan.
Most things called agents are workflows with a model bolted on. The line is whether the system picks its own next step, and everything difficult follows.
Every agent framework needs to call your internal APIs, not just the web. A custom MCP server exposes them safely once, instead of bespoke glue per agent.
LangChain chains are a pipeline. LangGraph graphs are a state machine. The moment your agent needs to loop or branch on its own output, you've outgrown a chain.
Whether it needs designing from scratch or rescuing from its own success, tell me what you’re building and I’ll tell you how I’d architect it.
Open to remote and hybrid work worldwide