A telescope.nvim extension that offers intelligent prioritization when selecting files from your editing history.
Lua
917
281 commits
updated Sep 7, 2026
A telescope.nvim extension that offers intelligent prioritization when selecting files from your editing history.
Using an implementation of Mozilla's Frecency algorithm (used in Firefox's address bar), files edited frecently are given higher precedence in the list index.
As the extension learns your editing habits over time, the sorting of the list is dynamically altered to prioritize the files you're likely to need.
Frecency naturally works best for indexed files that have been given a reasonably high score.
New projects or rarely used files with generic names either don't get listed at all or can be buried under results with a higher score.
Frecency tackles this with Workspace Filters:
The workspace filter feature enables you to select from user defined filter
tags that map to a directory or collection of directories. Filters are applied
by entering :workspace_tag: anywhere in the query. You can complete names by
pressing <Tab> after the first : character (the case when
enable_prompt_mappings = true).
When a filter is applied, results are reduced to entries whose path is a descendant of the workspace directories. The indexed results are optionally augmented with a listing of all files found in a recursive search of the workspace directories. Non-indexed files are given a score of zero and appear below the frecent entries. When a non-indexed file is opened, it gains a score value and is available in future frecent search results.
In default, pre-defined workspace tag: CWD is available. that is, you can
filter entries into ones under the current working directory.
If the active buffer (prior to the finder being launched) is attached to an LSP
server, an automatic LSP tag is available, which maps to the workspace
directories provided by the language server.
^0.9.0 tag for Neovim 0.9.x (See Notice for versioning).NOTE: fd or ripgrep will be used to list up workspace files. They are
extremely faster than the native Lua logic. If you don't have them, it
fallbacks to Lua code automatically.
This is an example for Lazy.nvim.
{
"nvim-telescope/telescope-frecency.nvim",
-- install the latest stable version
version = "*",
config = function()
require("telescope").load_extension "frecency"
end,
}
See :h telescope-frecency-configuration to know about further configurations.
A tagged release 1.0.0 is published and it drops the support for Neovim 0.9.x.
If you are still using Neovim 0.9.x, use ^0.9.0 tag for your favorite plugin
manager.
{
"nvim-telescope/telescope-frecency.nvim",
-- install any compatible version of 0.9.x
version = "^0.9.0",
config = function()
require("telescope").load_extension "frecency"
end,
}
Heads-up for users tracking master (or otherwise pulling HEAD without pinning
to a tag): 2.0.0 is a breaking release.
file_frecency.bin to
file_frecency_v2.bin and prints a one-time vim.notify. Your v1 file is
preserved on disk so you can roll back by pinning to ^1.0.0.query({ record = true }) no longer returns a timestamps array. Use
reference_time + last_accessed to get the most-recent access epoch (single
value). The count field is preserved as an alias for num_accesses.db_version config option is removed.If you want the previous behaviour (v1 algorithm, Neovim 0.10.x support), pin to the v1 line:
{
"nvim-telescope/telescope-frecency.nvim",
version = "^1.0.0",
config = function()
require("telescope").load_extension "frecency"
end,
}
See :help telescope-frecency-database-v2-migration for the full story.
:Telescope frecency
" Use a specific workspace tag:
:Telescope frecency workspace=CWD
" You can use with telescope's options
:Telescope frecency workspace=CWD path_display={"shorten"} theme=ivy
Filter tags are applied by typing the :tag: name (adding surrounding colons)
in the finder query. Entering :<Tab> will trigger omni completion for
available tags (the case when enabled_prompt_mappings = true).
You can run unit tests included in this repository by a script.
# Run this in /path/to/telescope-frecency.nvim
bin/run-tests
Run bin/run-tests -h for more details.
725 followers · starred Jan 2021
62 followers · starred Jul 2021
321 followers · starred Jan 2021
80 followers · starred May 2022
A telescope.nvim extension that offers intelligent prioritization when selecting files from your editing history.
Lua
917
281 commits
updated Sep 7, 2026
A telescope.nvim extension that offers intelligent prioritization when selecting files from your editing history.
Using an implementation of Mozilla's Frecency algorithm (used in Firefox's address bar), files edited frecently are given higher precedence in the list index.
As the extension learns your editing habits over time, the sorting of the list is dynamically altered to prioritize the files you're likely to need.
Frecency naturally works best for indexed files that have been given a reasonably high score.
New projects or rarely used files with generic names either don't get listed at all or can be buried under results with a higher score.
Frecency tackles this with Workspace Filters:
The workspace filter feature enables you to select from user defined filter
tags that map to a directory or collection of directories. Filters are applied
by entering :workspace_tag: anywhere in the query. You can complete names by
pressing <Tab> after the first : character (the case when
enable_prompt_mappings = true).
When a filter is applied, results are reduced to entries whose path is a descendant of the workspace directories. The indexed results are optionally augmented with a listing of all files found in a recursive search of the workspace directories. Non-indexed files are given a score of zero and appear below the frecent entries. When a non-indexed file is opened, it gains a score value and is available in future frecent search results.
In default, pre-defined workspace tag: CWD is available. that is, you can
filter entries into ones under the current working directory.
If the active buffer (prior to the finder being launched) is attached to an LSP
server, an automatic LSP tag is available, which maps to the workspace
directories provided by the language server.
^0.9.0 tag for Neovim 0.9.x (See Notice for versioning).NOTE: fd or ripgrep will be used to list up workspace files. They are
extremely faster than the native Lua logic. If you don't have them, it
fallbacks to Lua code automatically.
This is an example for Lazy.nvim.
{
"nvim-telescope/telescope-frecency.nvim",
-- install the latest stable version
version = "*",
config = function()
require("telescope").load_extension "frecency"
end,
}
See :h telescope-frecency-configuration to know about further configurations.
A tagged release 1.0.0 is published and it drops the support for Neovim 0.9.x.
If you are still using Neovim 0.9.x, use ^0.9.0 tag for your favorite plugin
manager.
{
"nvim-telescope/telescope-frecency.nvim",
-- install any compatible version of 0.9.x
version = "^0.9.0",
config = function()
require("telescope").load_extension "frecency"
end,
}
Heads-up for users tracking master (or otherwise pulling HEAD without pinning
to a tag): 2.0.0 is a breaking release.
file_frecency.bin to
file_frecency_v2.bin and prints a one-time vim.notify. Your v1 file is
preserved on disk so you can roll back by pinning to ^1.0.0.query({ record = true }) no longer returns a timestamps array. Use
reference_time + last_accessed to get the most-recent access epoch (single
value). The count field is preserved as an alias for num_accesses.db_version config option is removed.If you want the previous behaviour (v1 algorithm, Neovim 0.10.x support), pin to the v1 line:
{
"nvim-telescope/telescope-frecency.nvim",
version = "^1.0.0",
config = function()
require("telescope").load_extension "frecency"
end,
}
See :help telescope-frecency-database-v2-migration for the full story.
:Telescope frecency
" Use a specific workspace tag:
:Telescope frecency workspace=CWD
" You can use with telescope's options
:Telescope frecency workspace=CWD path_display={"shorten"} theme=ivy
Filter tags are applied by typing the :tag: name (adding surrounding colons)
in the finder query. Entering :<Tab> will trigger omni completion for
available tags (the case when enabled_prompt_mappings = true).
You can run unit tests included in this repository by a script.
# Run this in /path/to/telescope-frecency.nvim
bin/run-tests
Run bin/run-tests -h for more details.
725 followers · starred Jan 2021
62 followers · starred Jul 2021
321 followers · starred Jan 2021
80 followers · starred May 2022