yoagent

The deciding trait is that it is honest about being a component. The loop is the product, the bundled coding agent is a demonstration of the loop, and nothing pretends otherwise. If you are building something and have written that loop yourself twice already, this is the part you were going to reimplement and now do not have to.

For anyone hoping to install a tool and start working, the example is a starting point and not a finished one. Pick it if you are building. Pick a maintained terminal agent if you are not.

Examples become production, which is why an example's defaults matter. This one ships the full destructive tool set with no gate described between a model's suggestion and its execution, and the first thing anyone does with a working example is point it at a real repository. Nothing in the row records a confirmation prompt or a restricted mode.

What it does right is keep the example separate from the library. The loop itself takes no position on tools, so a careful builder supplies their own and inherits none of this.

1. Publishing the contract as machine-generated reference means every type and signature is stated rather than summarised, which is the difference between a library another engineer can evaluate and one they must read to understand. Very little in this category reaches that bar. 2. Unifying seven protocols behind a single streaming abstraction is the correct scope for a component: the loop is the invariant, the wire format is not.

2. No evaluation is published, and nothing here asserts a capability that would require one.

A component this narrow is uninvestable by construction, and that is not a criticism. The value it creates accrues entirely to the people building on it, there is no place to insert a price, and no hosted surface could be added without changing what it is. The author almost certainly knows this.

Moat: none, and none was ever available. Likely path: continued volunteer maintenance while the author needs it, then stillness. Position: use it, vendor the version you tested, and accept that the maintenance contract is you.

Procurement never hears about this and neither do I until an incident. Whatever gets built on it becomes an internal service with our name on the rota, and the governance questions, logging, retention, key custody, all land on the team that shipped it rather than on a supplier.

There is no unattended runner, no console and no identity integration, so it produces nothing I can measure and nothing I can police. Not yet as anything organisational, though I will not stand between an engineer and a dependency inside a service they already own.

Four local serving options named in the same list as the hosted ones is the thing I keep asking for, and switching between them is a flag rather than a code path. It runs against a model on my own machine with no key, which means evaluating it costs nothing and sends nothing anywhere. That is the correct first impression.

A permissive licence over a small Rust crate means the fork is trivially mine. No MCP client is the one omission, and in a library rather than a product I mind it considerably less.