Oh My Coder

The deciding trait is honesty about why it exists. This was written for developers who cannot get to the usual vendors, and the documentation includes the path back out, which is a strange and admirable thing for a project to publish about itself. Nobody writes a migration guide away from their own tool unless they mean it.

Judged against the tools it substitutes for, it is rougher and younger. Pick it when access is the binding constraint. Pick the thing it replaces when access stops being one.

The count is the warning. Thirty-one specialists means every request needs a selection decision, and the description names the roster without naming the selector, the fallback, or what happens when two of them would both accept the job. When that goes wrong the result is not an error, it is a competent answer to a question you did not ask.

What it does right is stay on the machine. Nothing is described as uploading your code, so a bad routing decision costs tokens rather than confidentiality.

1. Tiering memory is a reasonable structure and an empty phrase without a policy, because the entire value of a hierarchy lies in the rule that moves an item between levels. That rule is the contribution, and it is not published. 2. Awareness of the working directory is presumably a scoping signal, though whether it filters retrieval or only labels it is unstated.

2. An active-learning module appears in the same list, which is a term with a precise meaning in the literature and no definition here.

Access arbitrage is a real business until it is not. This exists because certain vendors cannot be reached from its market, which is genuine demand and entirely contingent on decisions made by people who have never heard of the project. Domestic model providers are also building their own tooling, and they have distribution this does not.

Moat: none that is durable. Likely path: superseded by a provider-backed client, or maintained as a personal utility. Position: use it for what it solves today, and assume the reason it exists has a shorter life than the code.

What stops me is the interface. A local web front end on sixty developer machines is sixty listening services my security team did not approve, and nothing published describes a login, a bind address or a way for me to turn it off centrally. That is a conversation I would rather not start.

Everything else is the usual absence: no directory integration, no usage reporting, no retention statement, and nothing that would run in a pipeline where I could measure it. Not yet: the web interface has to be documented or disabled before this reaches a work laptop.

The provider breadth is the point and it is genuinely broad, which matters more than it sounds: a dozen endpoints means no single vendor decision can strand me, and a local runtime in that list means the floor is my own hardware. Permissive licence, Python source I can read on a train, and no account anywhere.

What is missing is the connector everything else grew. Without protocol support my existing servers are unreachable, so extending it means patching the package rather than editing a config. Fixable, and somebody should.