Open-source project
pwntester/octo.nvim avatar
pwntester/octo.nvim

octo.nvim ships no releases, truncates both of its install snippets, and has no test target

Edit and review GitHub issues and pull requests from the comfort of your favorite editor

3,411 stars253 forksLuaMIT

At a glance

What is it?
An MIT-licensed Neovim plugin for editing GitHub issues, pull requests and discussions as ordinary buffers, driven through the GitHub CLI. It has published no GitHub releases, its plugin-manager example and its default configuration both stop mid-line, the Makefile has no test target and filters a class of diagnostics out of its type check, and a commits badge points at a branch that is not the default.
Who is it for?
octo.nvim is the right tool if you already live in Neovim and want issue and pull request work to happen in the same window as code, because a buffer you edit and write is a much smaller loop than a browser tab, and it covers the review workflow rather than only issue creation. Three things to know.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 1 day 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.

From daily snapshots

Star history

  • pwntester/octo.nvim3,411 ★ · +26
Star history
Repository2026-09-242026-11-15
pwntester/octo.nvim3.4k3.4k

26 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

There are no releases, so a plugin manager entry is the install

The repository has published no GitHub releases at all. That is normal for a Neovim plugin and it has a direct consequence: there is no tag, no archive and no changelog entry to point somebody at, so a plugin manager resolves the plugin from the default branch and the version you get is whatever was there when it cloned. The documented install is a lazy.nvim spec, which is the current convention, and the spec is lazy-loaded on the Octo command rather than at startup. If you need reproducibility for a shared configuration, the branch has to be pinned by commit, because the project offers nothing else to pin. The default branch is master and the last push to it is dated 2026-08-28.

A commits badge points at a branch that is not the default

The badge row at the top of the readme carries six links. Five of them are consistent with the repository: the project itself, the issues, the licence file under master, the stargazers list, and a link to the author. The sixth points at the commit history of a branch named main. The default branch of this repository is master, so that badge either points at a stale mirror that nothing maintains or at a branch that exists but is not the trunk. Either way it is a small signal about how carefully the header is maintained, and it is worth noticing because a contributor who trusts that badge to see recent activity will see the wrong thing. The rest of the documentation, including the licence link and every command example, uses master.

Both the install snippet and the default configuration stop mid-line

There are five code blocks in the readme and two of them are unfinished. The lazy.nvim installation spec ends in the middle of a keybinding, on a line that opens a command string for notifications and stops there, with no closing quote and no closing braces. The block holding the full default configuration ends inside a picker mapping table, on a keybinding whose description string has been opened and never closed. Both blocks are delimited by comment markers in the source, and the configuration block in particular sits between generated markers, so it is meant to be regenerated rather than edited. As published, neither can be pasted. The three example blocks that show commands and URL schemes are complete.

The type check filters diagnostics and there is no test target

The build file has three targets and none of them runs a test suite. The format target hands every file to a pre-commit style runner, the docs target runs a generation script, and the check target runs the Lua language server over the plugin's own directory with a configuration file that lives inside the workflows directory rather than at the root, at a check level of Information. Its output is piped through a filter that discards every line reporting an undefined global named vim, which is the standard complaint from analysing Neovim plugins without the editor's own runtime. The consequence is that a check can end up discarding everything it reported and still look clean, so the target is a useful smoke test rather than a gate.

Configuration documentation is generated by a shell script

The full default configuration in the readme is not maintained by hand. It sits between a pair of marker comments and is produced by a script in the scripts directory, which is a shell script rather than a Lua one in a project that is otherwise entirely Lua. That is a sensible arrangement for a configuration reference, since the alternative is a table that drifts from the code, and it explains why the block has markers around it. The repository layout is otherwise unusually small: one directory for the module itself, one for files loaded after startup, one for editor help, and one for scripts. Formatting is handled by StyLua with its own configuration and ignore file, and a pre-commit configuration sits alongside.

A GraphQL config at the root is the plugin's quiet dependency

One file in the repository tree is worth attention on its own: a GraphQL configuration file at the root, sitting next to the licence and the Makefile. In a repository with no GraphQL source directory, a file like that is normally there so that an editor extension picks up a project's queries and schema, which means the plugin's GitHub access is expressed as GraphQL somewhere, in addition to going through the GitHub CLI. The readme's feature list names the pieces that depend on it: labels, reactions, assignees, project cards and reviewers all come from APIs that the CLI's simpler commands do not cover. It is also the kind of file that reveals the shape of the integration to anyone who opens the repository expecting only Lua.

The GitHub CLI is required, and Projects v2 needs a scope refresh

The requirements list names Neovim at 0.10.0 or newer, the GitHub CLI, and one required plugin for the asynchronous work. Beyond that, the picker is a choice: one of three picker plugins, or none at all, in which case the built-in select interface is used. Two details in that list are practical rather than obvious. First, Projects v2 support needs a scope the token does not have by default, and the readme gives the exact refresh command to add read access, plus the alternative scope for modifying projects. Second, file panel icons come from a separate icon plugin unless you supply your own function, which is configured in a small block that does survive intact in the readme:

lua
require("octo").setup({
  file_panel = {
    icons = function(name, _ext)
      return require("mini.icons").get("file", name)
    end,
  },
})

There is also a health check: after installing, running it for this plugin verifies the setup rather than leaving you to discover a missing dependency from a failed command.

Editorial conclusion

octo.nvim is the right tool if you already live in Neovim and want issue and pull request work to happen in the same window as code, because a buffer you edit and write is a much smaller loop than a browser tab, and it covers the review workflow rather than only issue creation. Three things to know. It has no published releases, so installation is a plugin manager entry and there is no tag to pin. The GitHub CLI is a hard dependency, and using Projects v2 means refreshing your token with an extra scope before that feature will work. And the plugin's own development tooling is thin in one specific way: the Makefile formats, generates docs and type checks, but has no test target, so the correctness of a change rests on the type check and on manual use.

Frequently asked questions

What does octo.nvim do in Neovim?

It edits GitHub issues, pull requests and discussions from the editor. You open an item as a normal buffer, edit the title, body or comments as text, and write the buffer to sync the change back to GitHub. It can add, modify and delete comments, and manage labels, reactions, assignees, project cards and reviewers.

What are the requirements for octo.nvim?

Neovim 0.10.0 or newer, the GitHub CLI, plenary.nvim, and either one of the supported picker plugins or none at all, in which case the built-in select interface is used. File panel icons need an icon plugin unless you supply your own function.

Does octo.nvim support GitHub Enterprise?

Yes. The Octo command accepts GitHub Enterprise URLs and detects the hostname, and there is a URL scheme you can open with the edit command, with or without a host, which is how you work with several instances without setting a global host variable. Both singular and plural forms of the issue and pull path segments work.

How do I get Projects v2 working with octo.nvim?

Refresh the GitHub CLI token with the project read scope using the auth refresh command with that scope. To modify projects rather than only read them, add the project scope instead.

Are there any released versions of octo.nvim?

No releases have been published, so installation goes through a plugin manager entry pointing at the repository, and there is no tag to pin. The last push to the default branch was on 2026-08-28.

Official sources

  1. Issues
  2. License: MIT
  3. pwntester/octo.nvim on GitHub
  4. README
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.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/pwntester-octo-nvim.svg)](https://hysenlabs.com/projects/pwntester-octo-nvim)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/pwntester-octo-nvim.svg)](https://hysenlabs.com/projects/pwntester-octo-nvim)

Was this useful?