99: a Neovim agent plugin with nine options and no licence file
Neovim AI agent done right
At a glance
- What is it?
- 99 is a Lua plugin that puts an agentic workflow inside Neovim, driving an external coding agent process rather than talking to a model directly. Its README is generated, every entry in its option table says no description, and the repository ships no licence.
- Who is it for?
- 99 fits a Neovim user who wants the agent to search and report rather than rewrite, since the author's own account is that hand coding still matters and that the useful direction is search and work rather than replacement. Three things to know before you configure it.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Yes. The repository last received commits 157 days ago.
- What is it written in?
- Mainly Lua, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- ThePrimeagen/994,751 ★ · +4
| Repository | 2026-09-11 | 2026-11-15 |
|---|---|---|
| ThePrimeagen/99 | 4.7k | 4.8k |
4 Stars in the last 65 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The README opens with two warnings and no licence
The first two sections of the file are warnings, and they are the most consequential content in it. There is a notice for anyone arriving from the author's video, saying that many things have changed and asking for care, and then a heading that announces API changes right now, with the explanation that APIs will disappear or be changed and an apology, because this is a beta product. Two further warnings follow in the body: prompts are temporary right now and could be massively improved, and the project is officially in beta but the API can still change, with the author adding that this is unlikely at this point. Then the licence question. The repository has no LICENSE file at the top level and the metadata reports no licence. For a plugin meant to be dropped into someone's editor configuration and modified, that is a real gap, and it is not a judgement about the code.
It drives an external agent process, and the default is OpenCode
The plugin does not speak to a model. It runs an agent as a separate process, and the clearest evidence is the description of `stop_all_requests`, which says that stopping in-flight requests means the underlying process will be killed, naming OpenCode, and that any result will be discarded. The setup block confirms the arrangement: the provider option takes a value from `_99.Providers`, with a commented line naming `ClaudeCodeProvider` and a note that the default is `OpenCodeProvider`. So the plugin is a front end for whichever coding agent CLI you already use, and the process lifecycle is the interesting part. A request returns a `TraceID`, so a search can be tracked and revisited, and there is an `in_flight_options` option for the spinner behaviour, which the README says setup configures along with default values and completion. The logger is separately configurable, and the setup example writes its log under `/tmp` using the working directory's base name. The Makefile separately has a clean target that removes files matching `/tmp/lua_*`.
Nine options and nine lines that say no description
The options table for `_99.Options` is the most revealing page in the documentation, because the table exists and the prose does not. Nine fields are listed: `logger`, `model`, `in_flight_options`, `md_files`, `provider`, `display_errors`, `auto_add_skills`, `completion` and `tmp_dir`. Each has a type, all optional, and each has a default column that is empty. And then, under the API heading, each of the nine is documented with the same sentence: no description. So the surface you are expected to configure is nine names wide and entirely unexplained in the file. Some are inferable from context, since a model string is a model, a boolean for displaying errors is a flag, and markdown file paths suggest which files the agent reads, but `auto_add_skills` and `completion` have no explanation at all. The typed approach is still worth something: the signatures are precise, the types are named types rather than loose tables, and a language server can check a call against them.
search and work are the direction, and work is heading for worktrees
The author's own account of where the project is going appears before the API reference. The original video was about replacing specific pieces of code, but the more the author uses the tool, the more the useful direction turned out to be through `search` and `work`, and the usage section recommends starting with `search` as the direction the library is taking. `search` performs a search across the project with the prompt you provide and returns a list of locations with notes that land in a quick fix list, which `open` then displays in what the file calls the qfix window. `visual` takes the current selection and the prompt and replaces the selection with the results. The `work` side is the Extensions namespace, described as a persistent way to keep track of work, holding a single work item at present. The stated plan is to take it into worktree territory and be able to swap between things, and the file says that is where most of the change and focus will go.
The documentation is generated, and the tables show it
The repository listing explains why the API reference reads the way it does. There is a `README_HEADER.md` beside the `README.md`, and a `gen-docs` file at the root, which suggests the reference section is produced by a generator rather than written by hand. That explains several things at once. It explains why the type tables are precise while the prose is thin, since types come from annotations. It explains the repeated placeholder sentence, since an undocumented item has nothing to generate from. Two other documents sit beside it for the same reason: `TODO.md` for what is planned and `AGENTS.md` for the instructions given to coding agents working in the repository, with an `.agents/` directory beside it holding whatever rules and skills the project expects an agent to load.
Tests run Neovim headless, and pr_ready checks formatting without fixing it
The whole toolchain for a plugin like this is four lines of make, and one of them is the interesting one. Formatting is StyLua with the repository's own configuration file, checked separately from being applied. Linting is luacheck over the Lua directory with a `vim` global declared, which is the standard concession for editor plugins. And the test target runs the editor itself:
lua_test:
echo "===> Testing"
nvim --headless --noplugin -u scripts/tests/minimal.vim \
-c "PlenaryBustedDirectory lua/99 {minimal_init = 'scripts/tests/minimal.vim'}"There is no mock in that line. A headless Neovim, with plugins disabled and a minimal configuration, runs a Plenary busted directory over `lua/99`, which is also why the plugin directory is `lua/99/` and the module is required as `require("99")`. The practical consequence is that a change to a Neovim-facing behaviour has to be exercised in an editor process, and the environment is pinned by `scripts/tests/minimal.vim`. The pull request target then chains lint, test and the format check, which means a contributor's change is verified for style but not reformatted for them.
Queries, syntax and scratch sit beside the plugin source
The rest of the root listing suggests what kind of plugin this is. There is a `queries/` directory and a `syntax/` directory, both of which are trees rather than plugin modules, and `scratch/`, which is where work in progress tends to live. Configuration for the tooling sits next to them: `.luacheckrc` for the linter, `.luarc.json` for the Lua language server, and `.stylua.toml` for the formatter. The single most interesting option name in the API table connects back to this layout, since `md_files` takes a list of markdown paths and `auto_add_skills` is a boolean, which together suggest the plugin feeds a set of instruction files and skills into the agent's request. The `additional_rules` option makes that explicit: you can provide extra arguments, and if you have a skill called cloudflare you can provide the rule for it and its context will be injected into your request.
Editorial conclusion
99 fits a Neovim user who wants the agent to search and report rather than rewrite, since the author's own account is that hand coding still matters and that the useful direction is search and work rather than replacement. Three things to know before you configure it. It is a beta by the README's own warning, with an API that may change or disappear and prompts the author calls temporary. It drives an external process, so `stop_all_requests` kills that process rather than cancelling a thread, and the default provider is OpenCode. And it has no licence: there is no licence file at the root and the metadata reports none, which matters if you intend to vendor or redistribute it. Treat it as a tool to read and adapt, pin the commit you use, and expect the option names to move.
Frequently asked questions
What is the 99 plugin for Neovim?
99 is an agentic workflow for Neovim, described as augmenting the programmer rather than replacing one. Its functions are setup, search, vibe, open, visual, view_logs, stop_all_requests and clear_previous_requests, plus an Extensions namespace whose Worker abstraction tracks work items for the project.
How do I set up 99 in Neovim?
Add it as a plugin in your configuration, require the module with `require("99")` and call `_99.setup`, optionally with a logger block, where the level and path are configurable. The documented provider default is OpenCodeProvider, with ClaudeCodeProvider shown as an alternative.
What does the search function in 99 do?
It performs a search across your project with the prompt you provide and returns a list of locations with notes, which are put into a quick fix list. The `open` function then displays the last interaction, opening the qfix window for search and vibe results and a tutorial window for tutorial items.
Does the 99 Neovim plugin have a licence?
There is no licence file at the root of the repository and the repository metadata reports no licence, while the README describes the project as a beta whose API may still change and whose prompts are temporary.
What does stop_all_requests do in 99?
It stops all in-flight requests, which means the underlying process is killed, named in the README as OpenCode, and any result is discarded. A separate function, clear_previous_requests, clears previous search and visual operations.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/theprimeagen-99)Star history chart for your README
[](https://hysenlabs.com/projects/theprimeagen-99)Was this useful?