Aizen

The deciding trait is weight. One static binary, no Node, no Python, no Docker and no cloud account means it fits on a 512 MB box you keep for exactly this sort of thing, and the whole install is a file you can delete. Anyone who has watched a coding agent drag a package manager onto a scratch container will know why that matters.

What you trade is maturity, and the feature list is broader than the audience testing it. Pick it for a small machine you own. Pick Aider when the repository is the one that pays you.

The risk is provenance. A documented install that pipes a shell script from one GitHub organisation into your machine while the canonical source lives under another is a gap nobody should have to reason about, and it is the first thing a careful engineer checks before running an agent with shell access and git write permissions on a repository.

What it does right is refuse the middleman. There is no vendor account, no hosted control plane and no telemetry endpoint described anywhere, so the trust question stops at the download rather than continuing for the life of the tool.

1. Pairing a semantic index with a language server is the correct pairing: the index answers questions about meaning and the server answers questions about symbols, and neither substitutes for the other. 2. Self-verification is asserted rather than described, and the description names no check, no test runner and no acceptance criterion.

2. A persona and self-evolution system sits in the same paragraph as those retrieval components, which is an unusual thing to publish without a measurement, since a loop that modifies its own behaviour is precisely the loop a reader wants numbers for.

There is nothing to acquire and nothing to fail. A hundred stars measures curiosity, not adoption, and a lab name on a repository is a signal of intent rather than of headcount. The economics are simple because there are none: no meter, no seat, no invoice, and therefore no reason for anyone to keep the lights on except pride.

Moat: none. Likely path: it stops receiving commits quietly, or the ideas reappear inside a better-funded terminal agent. Position: worth watching, not worth standardising on, and vendor it into your own tree if you ship anything that depends on it.

Financially this is free across sixty desks, and the permissive licence means legal reads it once and moves on. That is where the good news stops. Sixty independent installations with no administrative surface mean model configuration and key distribution land on my platform team, using tooling built for laptops rather than for agents.

It does not run unattended, so it never becomes something I can measure in the pipeline, and the onboarding story for a mid-level engineer is a README. Not yet: I want a named vendor, a retention policy and a managed install before this touches company code.

I like the shape. A compiled agent with no interpreter underneath it is one artefact to audit and one artefact to ship, and pointing it at whichever inference endpoint I feel like is a single setting rather than a provider integration somebody has to write. The licence means a fork survives whatever happens to the author.

What is missing is the protocol layer. Every tool I have already wired up as a server is unreachable here, so extending it means writing Rust and rebuilding rather than editing a JSON file. Grudging respect for the binary, less for the plug sockets.