99

You will like this if you actually enjoy typing code. The premise is that hand coding still matters and the agent should augment the programmer, which shows up as commands that surface information and apply changes without taking the wheel. The deciding daily trait is restraint: it does not try to own the file, so you never spend an afternoon undoing an enthusiasm.

Pick it if that description sounds like your workflow. Pick CodeCompanion.nvim if you want chat, refactors and a wider provider list in one plugin instead.

The risk is indirection. Real work happens inside OpenCode or Claude Code, so when a run goes wrong the fault line sits in a process this plugin only launched, and the debugging surface is somebody else's log. On top of that the project is explicitly beta and its API still changes, which means a working config is a working config until the next commit.

What it does right: providers are pluggable rather than hardcoded, so a change of agent vendor is a change of configuration and not a change of editor.

1. Context gathering is delegated: the plugin surfaces information through search commands and hands the retrieval problem to the provider. 2. Edit application arrives through work commands that apply changes from inside the editor, though the mechanism is not specified anywhere in the repository. 3. Verification is unaddressed, which is consistent with a design that positions the human as the reviewer of every change.

The documentation is one file. That is honest for a beta and thin for an evaluation, and it means most architectural questions here can only be answered by reading Lua.

The asset is attention. ThePrimeagen brings an audience most seed-stage founders would pay for, and 4,752 stars arrived fast because of it. What is absent is everything a company needs: no entity, no pricing, no monetisation attempt, and therefore no obligation to anyone. Distribution without a business model is a hobby with good reach, and hobbies end when the creator's interest moves.

Likely path: quiet dormancy rather than acquisition, because there is nothing to buy. Position: use it freely, and do not let it become load-bearing in a workflow you must defend next year.

The demo is quick. Sixty seats costs nothing here, because the meter belongs to the underlying agent CLI and lands on a separate invoice we already have. There is no vendor to sign anything, no support path, no data retention statement, and nothing central to audit. It runs on macOS and Linux, so the Windows engineers are excluded before the conversation starts.

Onboarding is an afternoon for anyone already in Neovim, and a lost week for anyone who is not. Not yet.

The good part first: it is Lua, it installs as a lazy.nvim spec with require("99").setup({}), and the model is whatever the provider CLI is already configured to use, so my keys and my routing stay where I put them. Nothing here holds state I cannot reach.

The bad part is legal, not technical. The source is public and there is no licence file, which means I have no grant to fork, redistribute or vendor it into anything. I can read it. I cannot rely on being allowed to keep it.