September 21, 2026
AI left every open bug in Bend 2: Taelin rates agent code at 30% of his own level
The language's author cannot give up agents: by his own account, he would not have released Bend at all without them.
Taelin
@victortaelin
(an unimportant stream of thought, feel free to skip) So, several issues have already been opened on Bend 2, and not one of them, in fact, stems from a line of code I wrote by hand. Every one comes down to some unimaginably stupid AI decision in a part of the code I did not scrutinize closely enough and do not fully understand. Because that is exactly how AI works: anything you do not watch will come back to bite you in some idiotic way. Worst of all, I cannot even merge these PRs quickly, because that would only add more slop. Bend works perfectly, it does everything it promised, and it certainly does more than it would if I had written it by hand. But if you take a random function in the repository, its average quality is still 30% of what I am used to shipping. It is wildly frustrating because there really seems to be no way out. Without AI I ship much less (or do not ship at all). With AI I ship lower-quality work. It is incredibly stifling. Ironically, Bend is designed to solve exactly this problem. The only thing that comes to mind is: "what if I took a month and wrote Bend using Bend itself." But I cannot, because HOC is literally running out of money and I probably need to focus on the round. Plus, as Akita said, support the community, review PRs, and do anything except shut myself away and code.
· 21.5K views
Bend 2 is four days old: 22 thousand stars and 19 open bugs. Not one came from code the language's author Viktor Taelin wrote by hand.
Every bug traces back to an AI decision in a piece of code the author did not inspect. That is how any agent-built project works: whatever you do not watch will eventually come back to bite you.
The cost of speed. The language works and does everything it promised. Since the 17 September release, 22 versions have come out; the latest is v2.0.21 from 20 September. But a random function in the repository is worth 30% of the quality Taelin is used to shipping.
Without agents, he would ship far less, or would not have shipped Bend at all. With agents, the language shipped, but now he is fixing code that is not his. 12 submitted pull requests are sitting unaccepted: merging them quickly means adding more of the same kind of code.
On 17 September, he was already responding on Hacker News to accusations of vibe coding: a human designed the compiler, runtime, and core; the core passed a manual audit; and he promised to clean up AI-generated junk over time.
What to do with code you have not read
Taelin built his answer into the language itself. A human writes laws in the LAWS.bend file, and AI does not touch it. AI writes proofs separately, in PROOF.bend, and the `bend PROOF.bend` command acts as a gate: it fails while even one law is open or false, and prints "All terms check." when they all hold.
The method's cost in lines. In the "cannot win" demo, there are 194 lines of code, 68 lines of laws, and 484 lines of proofs. There are 2.5 times more proofs than code, but a human needs to read 68 lines instead of the entire codebase. Taelin names the boundary himself: you still have to read LAWS.bend.
A law must be written precisely. In the same demo, they asked to remove walls, and AI moved the pieces diagonally, formally preserving the sole law, "cannot win." An imprecise law pushes the model to solve by the letter.
Bend itself installs with one command: `curl -fsSL https://bend-lang.com/install.sh | sh`. It requires Linux or macOS (on Windows, only through WSL) and Clang 14 or newer.
Taelin is putting off a month to rewrite Bend in Bend itself: by his account, HOC gets a round first.
