ROADMAP

September 25, 2025 · View on GitHub

High-level overview of the project’s goals, tasks, and milestones for future releases.

Any new ideas related to the content here are welcome.

Sections:

Current Prioritized Changes - tasks that might are not yet supported, but are being looked into for the next major release.
General Codebase Changes - tasks useful for future additions
Server Features and Providers - future general features that the server provides
Automation and Pipelines - CI/CD or tooling related to the project
Documentation - modifications for the project's documentation (wiki, README, site, etc.)

Current Prioritized Changes

abbr parser to build expandable CompletionItem snippets that insert the cursor in the abbr --set-cursor=% output.
- Normal case without --set-cursor would just directly insert the abbr and add more CompletionItem.commitCharacters to these specific items.
- Special case using --set-cursor would get the output of the abbr, and then replace the --set-cursor=% token with the snippet expansion token. Lots to consider here -- do we read this from a subshell? Performance could be a concern here if we do use a subshell.
Add code actions to replace absolute paths w/ variable that points to the previous location
- inefficient path diagnostics (inefficient meaning, things like absolute paths that could be replaced with relative paths, or variables that point to the same location)
- checking if a symbol is a path (could be isString(), isConcatenation(), ...). Currently considering a simple check for / in the node.text, to solve this
make __fish_contains_opt opt be considered as a argparse reference to the variable opt
- __fish_contains_opt -s o opt would match the argparse o/opt definition in the matching function/completion file
- complete -c cmd -n '__fish_contains_opt opt' would be a common usage
add support for hovering a ~/some/file/path and show the expanded result
- add info diagnostics for replacing absolute paths with expandable paths
- allow disabling this feature
add support for renaming ALL autoloaded files (currently requires atleast two code-actions to be used)
- when a code-action changes an autoloaded function, also rename its completions file, and vice versa
Add virtual document support for go-to-definition of a manpage
Server Command to display fish_config in a browser
add headless mode for the server (allows for using the server via the commandline, without opening any client).
- for example, fish-lsp headless --code-action='generate.completions' --file=~/.config/fish/functions/foo.fish would create a completions file for the foo.fish function, if it has an argparse in its body.
  - fish-lsp headless --show-tree --file=~/.config/fish/functions/foo.fish would show the client tree of the file
  - fish-lsp headless --get-references --file=~/.config/fish/functions/foo.fish --function=foo would show the references for the symbol defined in the file with the name foo
    - allow passing options for which scope to match the definition symbol, to search for specific references
      - --scope=local would only match references in the current file
      - --scope=global would match references in the current file and all files in the workspace
  - fish-lsp headless --show-tree --file=~/.config/fish/functions/foo.fish --scope=global would show all global symbols in the file
  - fish-lsp headless --get-references --file=~/.config/fish/functions/foo.fish --function=foo --scope=global would show all references to the symbol foo in the file and all files in the workspace
  - fish-lsp headless --diagnostics would show all diagnostics for the current workspace, or a specific file if passed with --file=~/.config/fish/functions/foo.fish
  - fish-lsp headless --workspace-symbols would show all symbols in the current workspace, or a specific file if passed with --file=~/.config/fish/functions/foo.fish
  - add completions for using the headless mode, so that the user does not have to remember how to use each subcommand
add support for a document to contain changes to the server's settings, and the server to update its settings based on the document changes
- cli command to generate the default settings file with default values
- cli command to show the current settings file of the directory $PWD
- server command to create a new settings file in the current workspace
- server command to update the server's settings file in the current workspace
- server command to show the current server's settings file inside of the current workspace
- create a schema for the server's settings file, so that a json-lsp client can validate the settings file and provide completions
- allow the user to specify custom fish file paths in the current workspace that should be treated like they were autoloaded files
- consider allowing converting the server's settings file to its equivalent fish source code
- allow any code-action that uses # @fish-lsp-disable to also be specified in the server's settings file. (NEED TO THINK ABOUT BEST WAY TO STORE THIS)

allow function definitions with --no-scope-shadowing or other flags that would change how the caller's scope is used, to be recognized as references relative to the request position.

function foo
    set -l baz 1
    #      ^^^---------- getReferences() to this variable [TOTAL: 2] (CASE 1)
    bar
    # since we call bar from the same scope as the getReferences() definition symbol
    # and bar has the `--no-scope-shadowing` flag, the reference to `baz` would be
    # considered a matching reference to the `baz` variable in the `foo` function
end
function bar --no-scope-shadowing
    echo $baz
    #     ^^^----------- getReferences() to this variable [TOTAL: 0] (CASE 2)
end
# Summary: 
# 
# When baz references are requested from inside the foo function,
# we check all commands called inside of the foo function. if any of them
# inherit the scope of the foo function, add the local references from the 
# called function to the references of the foo function.
#
# 
# When we check the references for `baz` inside of the `bar` function, we
# only show references that are used inside of the `bar` function.

NOTE: You could also try to find all references to the parent function and then add the caller scopes to the references of the parent function. This way, Case 2 would include the references to $baz in foo

allow functions with --argument-names to provide inlay hints for the arguments that are passed into the function calls, so that named arguments are shown in the client as inlay hints.

add support for expanding concatenation SyntaxNode: definitions, references and hovers

for opt in fish_lsp_{enabled_handlers,disabled_handlers,commit_characters,log_file,log_level,all_indexed_paths,modifiable_paths,diagnostic_disable_error_codes,enable_experimental_diagnostics,max_background_files,show_client_popups,single_workspace_support}
#          ^^^^^^^^^^---------------------- Hovering here would show the expansion 
    if not contains -- $opt $features_to_skip
        echo -e "$opt\t'fish-lsp env variable'"
    end
end

Inline Value provider (debugger for current line of script)
Allow formatting of files without using fish_indent command
Write server handler for Call Hierarchy requests
Allow server to support registering a capability for the client to check the type -ap a command under the current location.
Support options to enable from client configuration
- if_statement must be silent: if command -s -> if command -sq
- prefer command _ prefix for ambiguous commands
- default case for switch_statement
- test number/string flags from condition argument's
- function requires returning a status number
- fish_add_path instead of set -gx PATH _
- logger location
- private functions need underscore prefix
- prefer universal scope, or prefer global scope
- prefer specific redirect to /dev/null
- hover documentation fallback: tldr, cht.sh, ...
- format specific options
- remove showing lsp kind in completions list
Add server handler for onSemanticToken support
Add server handler for textDocument/publishDiagnostics to allow project wide diagnostics
Add code action to convert shebangs
- #!/usr/bin/fish to #!/usr/bin/env fish
- #!/usr/local/bin/fish to #!/usr/bin/env fish
add hover support to end stdin token --
add code-action to convert external shell commands to fish builtins (where applicable)
add fish-lsp info --time-startup --use-workspace $PWD support, to time how long it takes to start the server with only the current workspace
consider if exported variables should not be included in the unused FishSymbol[] reported by diagnostic 4004

General Codebase Changes

Server Features and Providers

status variable documentation

0 is generally the exit status of commands if they successfully performed the requested operation.
1 is generally the exit status of commands if they failed to perform the requested operation.
121 is generally the exit status of commands if they were supplied with invalid arguments.
123 means that the command was not executed because the command name contained invalid characters.
124 means that the command was not executed because none of the wildcards in the command produced any matches.
125 means that while an executable with the specified name was located, the operating system could not actually execute the command.
126 means that while a file with the specified name was located, it was not executable.
127 means that no function, builtin or command with the given name could be located.

Current Prioritized Changes

General Codebase Changes

Server Features and Providers

Automation and pipelines

Documentation