r/LangChain
Anyone else building their own agent harness instead of relying on out-of-the-shelf frameworks?
- upvotes
- 4
- comments
- 7
Post
Highlighted: the lines this signal was extracted from
Curious where everyone here lands on the "build vs. wrap" spectrum when it comes to running agent workflows for actual, daily work. Between orchestration libraries like LangChain/LangGraph, off-the-shelf multi-agent frameworks, and native CLI tooling (Claude Code, Codex wrappers, etc.), the options are everywhere. Yet, it feels like half the builders I talk to eventually get frustrated by framework lock-in or context bloat and just end up scripting their own custom harness. If you’ve rolled your own harness or bespoke workflow for a specific task:1. What was the specific task or failure mode that pushed you to build your own? (e.g., state recovery, tool sandboxing, deterministic linting/test gates, API token bleeding?) 2. What does your stack actually look like? Did you build on top of LangGraph/CrewAI, wrap an existing harness (Claude/Codex/Gemini CLI), or just write a bare-metal loop in Python/TypeScript with standard API calls? 3. Where did it get messy? Context window management, runaway tool loops, or overengineering a state machine that was supposed to "stay simple"? Would love to hear what worked, what blew up, and whether you’d build it from scratch again or stick to managed tooling next time.
Also quoted as evidence
[comment u/_goofballer] Running something like Langchain or whatever in a prod setting is insane. Simpler is better - Pi or Claude SDK is really as much abstraction as you should be using here