Ally

The deciding trait is scope. This is not a code specialist that happens to have a shell. It edits files, walks directories, reaches the internet and executes code, which makes it closer to a general assistant with hands than to a pair programmer. That breadth is genuinely useful on a machine where your work is not only a repository.

The cost of breadth is depth. Nothing here is tuned for the specific job of turning an issue into a merged change. Pick it for a private everyday helper. Pick Aider when the deliverable is a diff.

The approval model has a hole in it by design. Everything else prompts, and the documented escape hatch does not, which means the safety property depends on a human never taking the shortcut that exists specifically because approving things is tedious. There is no container boundary, so the shortcut runs with whatever the user runs with.

What it does right is sequencing. Tool calls are processed one after another rather than in parallel, so when something goes wrong there is an order to read and a single point where it went wrong.

1. Context acquisition here is an operation a user performs, not a heuristic the system applies. A corpus is embedded deliberately and queried afterwards, which makes the retrieval boundary visible and reproducible, and avoids the common failure of a repository map guessing wrongly at relevance. 2. The embedding backend is user-chosen, so the vector representation is a configuration rather than a hidden constant.

2. Nothing measures whether retrieval improves answers, and no evaluation is offered. The design is defensible; the effect size is unknown.

A personal project distributed through a package listing is a hobby with users, and that is a respectable thing to be. It is not a business. Two hundred and forty stars finances nothing, there is no paid tier to price and no entity for anyone to acquire, so continuity is entirely a question of one person's remaining enthusiasm.

Moat: none. Likely acquirer: none, and none needed. Likely path: a burst of releases, then slowing, then an archived badge. Position: use it, expect nothing, and keep your own copy of the commit you liked.

Finance would approve this in a minute and security would stop it in the same meeting. There is no identity layer of any kind, which means access is whoever holds the laptop, and no administrative surface, which means configuration drifts across every installation from the first week.

It does not run unattended, so it never becomes a step in a pipeline I can measure or a gate I can require. Onboarding a mid-level engineer is an afternoon, and the ongoing spend is model usage on keys I would have to issue and cannot currently revoke centrally. Not yet.

Local first, and I mean the design rather than the marketing. The default path runs entirely on my own inference, so the machine keeps its secrets, and the seven other providers are options I reach for rather than defaults I have to escape. The licence is permissive, the source is short enough to read in an evening, and a fork survives the author losing interest.

What is missing is a protocol. Servers I already run cannot attach, so every capability has to exist inside this project or not at all.