Crab Code

The deciding trait is that nothing here is new to you. The tools behave the way you expect, the permission prompts read the way you expect, and the shape of a session is one you have already internalised, so the cost of switching is close to nothing. That familiarity is the entire pitch and it is a reasonable pitch.

The catch is the same familiarity: you get a follower, and followers arrive late to whatever lands next. Pick it if independence is worth a lag. Pick the tool it mirrors if it is not.

The boundary is a text file. Rules decide what a tool may do, and there is no container beneath them, so a rule that does not anticipate a command simply lets it through onto the host. That matters more here than in a read-only assistant, because this one is allowed to touch version control, which is the state a developer least wants rewritten.

What it does right is putting the policy in a file you can review and version, instead of behind a settings screen nobody opens twice.

1. Precedence is where permission systems usually rot. Two lists that both match a request need a rule for the collision, and most projects leave it to evaluation order, which means behaviour changes when somebody reorders the file. Fixing denial as dominant makes the outcome predictable from the policy alone. 2. That property is testable without running a model, which is unusual in this category.

2. No evaluation of the agent's own capability is offered, and none is claimed, so there is nothing here to overstate.

Being a faithful alternative to a well-funded incumbent is the weakest commercial position I know. There is no pricing power, because the thing it resembles is already free, and no differentiation to sell, because differentiation would break the resemblance. Under a hundred stars means no community that would carry it if the author stopped.

Moat: none, by construction. Likely acquirer: nobody; a company adopting it would simply fork it. Likely path: a personal project that stays personal. Position: pass on the vendor, keep an eye on the code.

The unattended mode is the part with operational value. Something that runs without a person present can be scoped, budgeted and reported on, which is how any tool earns a place in our delivery process rather than on a laptop.

Against that, we compile it ourselves and then own the binary, the updates and the distribution, because there is no packaged release. No single sign-on, no directory sync, no central log of which repository an agent touched. Licence cost across the team is zero and model spend is the only invoice. Not yet.

Cloning and compiling is not a barrier, it is the point: I see what goes in, I can patch before I build, and the permissive licence means the fork stays legitimate. Routing between several providers on my own credentials keeps the cost mine to manage rather than a subscription somebody else meters.

Two things stop me short. My own hardware is not among the destinations, and there is no port for attaching servers I already run, so extending it means changing this codebase. Which, given the licence, I can do.