folke/noice.nvim

💥 Highly experimental plugin that completely replaces the UI for messages, cmdline and the popupmenu.

View on GitHub ↗Jump to charts ↓Open shareable report →

Summary Information

Updated 46 minutes ago
Added to GitGenius on September 11th, 2026
Created on September 21st, 2022
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 177
Total Stargazers: 5,817 (+0)
Total Subscribers: 14 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.4 days
Mean response time: 30.0 days
90th percentile: 39.2 days
Tracked items: 154

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 5% of issues opened in the past year have been closed. Three people close 74% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 1
Avg open age: 446 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (152)
  • stale (99)
  • wontfix (32)
  • enhancement (27)
  • upstream (4)
  • documentation (1)
  • pinned (1)

Detailed Description

Noice is a Neovim plugin that completely replaces the UI for messages, command-line input, and the completion menu.

The plugin addresses the limitations of Neovim's default message and command-line interface by leveraging the experimental vim.ui_attach API to provide a fully customizable replacement. It routes different types of messages to configurable views—including notifications, splits, popups, and virtual text—using a filter system. Message highlights are preserved across views, command output appears in normal buffers for easier interaction, and the command-line supports syntax highlighting for Vim and Lua code. The tool eliminates the more-prompt behavior and provides a full message history accessible through a dedicated command.

Adoption suits developers who want fine-grained control over how Neovim displays messages and command-line interactions and who are comfortable running nightly builds. It depends on nui.nvim for rendering and optionally integrates with nvim-notify for notifications, telescope.nvim or fzf-lua for message history search, and nvim-treesitter for syntax highlighting. The README explicitly marks the project as highly experimental and recommends checking a tracking issue for known problems before adopting it.

Maintainers typically respond to issues and pull requests within one to two weeks. The issue tracker is dominated by bug reports, enhancement requests, and upstream-related work, reflecting the project's reliance on experimental Neovim APIs and its active engagement with stability concerns.