Qwen-Agent

The deciding trait is that this is not a side project. It is the backend of the vendor's own chat product, which means the code path you depend on is the code path they debug on a Monday morning when something breaks in production. Very few frameworks on this board can say that, and it shows in how little you have to work around.

The tilt toward one model family is real and mostly invisible until you leave. Pick it if Qwen is your model. Pick something neutral if it might not be.

The coupling is the risk. A framework whose examples are refreshed to follow one vendor's releases is a framework whose regressions are found on that vendor's models first, and anything else you point it at is territory nobody is testing on your behalf. That is not lock-in by licence, it is lock-in by attention.

The second exposure is the interpreter, which writes and runs code by design. What it does right is scope the install: capabilities arrive as named extras, so a deployment that does not want execution simply does not ask for it.

1. Releasing an evaluation openly is a genuine good, because a benchmark nobody can inspect is not evidence, and most vendors on this board publish scores without publishing the harness. 2. The authorship problem does not disappear by being open: a suite designed alongside a model family will reflect the tasks its designers found interesting.

2. The correct reading is that this is a useful instrument and not an independent one, and the distinction between the two is the distinction the reader has to maintain themselves.

Frameworks published by model vendors are distribution, and distribution is the only durable advantage in this category. Three years of continuous shipping from a team whose day job is the models underneath means the maintenance is funded by something other than goodwill, and seventeen thousand stars is the adoption signal that makes the funding easy to defend internally.

Moat: the model family it is built to serve. Likely acquirer: none, and no exit is needed. Position: the lowest abandonment risk on this row, bought with a directional preference you should be honest about.

As a library this never reaches procurement, which is fine, and whatever my engineers build with it becomes a service my platform team runs, budgets and pages on. That is the usual trade and I am used to it.

The part that is not usual is the shipped browser extension. Anything that installs into a developer's browser and reads the page they are on is a data path my security review has to approve separately from the framework itself. Approved with conditions: the library yes, inside a service we operate; the extension no, until it has been through review.

This is the rare case where the vendor's own framework does not trap you in the vendor's own service. The endpoint is a setting, the weights for its preferred family are downloadable, and the combination means I can run the entire stack on hardware I built without asking anyone for a key. Permissive licence keeps the fork alive.

Extras in the install line are the detail I appreciate: I take the retrieval and protocol pieces and leave the interface behind, so the dependency tree is the one I asked for rather than the one somebody assumed.