nvim-treesitter repository archived on GitHub, users left wondering what's next

What happened

It has been reported that the nvim-treesitter repository on GitHub has been archived and made read‑only. For years the plugin has been the go‑to manager for Tree‑sitter parsers in Neovim — installing, updating and removing parsers, hosting language‑specific queries, and acting as a staging ground for features intended for upstreaming into Neovim. The project README even warns users that a full, incompatible rewrite exists and that the master branch is locked but kept for backward compatibility with older Neovim releases.

Why it matters

This isn’t just a cosmetic move. nvim‑treesitter coordinated parser compatibility, provided queries that enabled highlighting, folding, injections and experimental indentation, and recommended automation like :TSUpdate or build hooks in plugin managers. Many users have configs that assume this plugin will keep receiving parser updates and fixes. An archived repo means no new commits, no issue triage, and a lot of folks suddenly facing stale parsers or subtle breakage — or at least a pit in the stomach when you open Neovim and a syntax highlight misbehaves. Who wants to debug that at 2 a.m.?

Next steps for users

First, don’t panic. Check the archived README for instructions: the master branch remains available for compatibility, and the usual bootstrapping commands (including require('nvim-treesitter').setup and :TSUpdate) still work against existing releases. Then decide: pin to a known commit, migrate to a maintained fork, or lean on Neovim’s upstream Tree‑sitter support if that covers your needs. Community discussion on Lobsters and other forums is already bubbling with suggestions — forks, mirrors, and upstream moves are on the table. Will Tree‑sitter live on inside Neovim core, or will the community rally behind a new home for these tools? Time will tell, but now’s the moment to check your configs.

Sources: github.com/nvim-treesitter, Lobsters