I spent 883 commits and 8 months building an LLM agent harness, overengineered it, and abandoned it - lol.
- 发布
- 09/06 02:18
- 收录
- 09/06 15:00
- 来源类型
- 开发者社区
- 档位
- 社区
- 信源状态
- 正常
(I am open sourcing what i have as MIT, link on the comments and yes all 8 months i mostly used 1 20x claude or sometimes 2 20x accounts, so this was basically all made by claude models/claude code harness - by the way don’t use my agents.md or claude.md etc, its old and its not what i use now and far from what i would recommend.)
So yeah, I spent 883 commits, 8 months and billions of tokens building this thing and eventually abandoned it:
It started as my attempt to build a better coding-agent harness, where the LLM is basically a replaceable worker instead of being trusted to control everything.
The harness was supposed to own the actual planning, state, permissions, context, verification, evidence, orchestration, etc. The model could say “I finished the task,” but the system would check what actually happened instead of just believing it.
Then I kept adding shit.
Code graphs, RAG, deterministic orchestration, isolated workers, crash recovery, model routing, local models, replayable runs, verification gates, self-improvement experiments, dashboards, computer use, personal automation, and a million other ideas.
Eventually it became a ridiculously overengineered mess. I spent more time researching, planning, and adding systems than actually using the thing to get work done. Other harnesses were already becoming much more usable while mine was still mostly a giant headless experiment.
So I killed it.
I’m not posting this as a working product, and I definitely don’t recommend downloading it expecting some polished Claude Code alternative. A lot of it is incomplete, disconnected, outdated, or just plans that never became real.
But there is also a stupid amount of research, architecture, experiments, failed ideas, and code in there. Some parts might still be useful to people building agent harnesses, especially around:
- keeping state and verification outside the model
- deterministic/replayable agent runs
- codebase retrieval and dependency graphs
- orchestrator/worker separation
- context budgeting and session handoffs
- sandboxing and permission gates
- checking agent claims with evidence it didn’t generate itself
The archive has the original experimental Rust/Python/Tauri code, thousands of planning and research documents, and the sanitized commit history.
Basically: it failed as a product, but maybe someone can steal a good idea from the corpse.
I’d be curious what people here think is actually worth salvaging, or whether the whole architecture was doomed from the moment I kept expanding the scope.
I might one day finish it, but who knows if it will be necessary, i aimed at solving everything and ended up solving nothing, i hope this helps you in any means so at least its not a total loss, even if its only a lesson or confirmation of what type of shit to not do.