Wizard

The deciding trait is how little stands between deciding and using. One command installs one binary, and the first run asks you a single question before it starts working. Nobody who has abandoned a promising tool at the third configuration file will underestimate what that is worth, and most projects here could learn from it.

What it is not is a repository specialist: no branch or commit handling, and the scope is your machine rather than your codebase. Pick it as a personal assistant. Pick a coding agent for code.

Self-extension is the property that makes every other guarantee provisional. An agent that grows new abilities has a capability set that differs from the one you installed, and the row records no approval step for an addition, no isolation around what it writes, and no version control operations that would let you see the difference or undo it. Two users on the same release do not have the same tool.

What it does right is putting everything in one directory, so at least the drift is confined to a place you can inspect.

1. Persisting context in a human-readable document rather than an opaque store is a substantive design position: a wrong memory is findable and editable, which is the only practical remedy when an agent has learned something false. 2. Line-delimited session records make replay and analysis trivial with ordinary tools, so evaluating this agent's behaviour requires no cooperation from its authors.

2. No measurement of retrieval quality is offered, and none is claimed, so nothing is overstated.

That ratio is a story, not a product. Being discussed twice as often as it is starred means the idea travels further than the software, which is exactly the pattern that precedes either a funded company or a widely imitated blog post. There is currently no entity, no service and nothing charged.

Moat: the positioning, which is genuinely distinctive and entirely copyable. Likely acquirer: none, though attention at this level is how a solo maintainer gets an offer. Position: watch the author, use the binary.

Two problems compound. Fetching and executing a script from the internet is not permitted on managed hardware, and what arrives is software that changes after installation, so the version recorded in my inventory stops describing what is on the machine within a week.

Serving a model locally also consumes the hardware I bought for compiling, which is a capacity question nobody has budgeted for. No single sign-on, no directory sync, no audit export and nothing unattended. Not yet.

No other project here does this. Most tools that claim local support mean you may configure an endpoint if you already run one; this one picks a quantisation for the machine it is on and starts the server itself, so the path from install to working with nothing leaving the room is a single choice. Everything it keeps is plain configuration and readable text under one directory.

Sixteen hosted providers are there when I want them, switchable mid-session. Permissive terms, one binary, no account. This is what ownership looks like.