leetcode-compat.nvim

A Neovim plugin for LeetCode that is fully compatible with the VSCode LeetCode extension file format. Work on your existing solution files directly — no migration needed.

Features

• VSCode Compatible — Reads and writes the same @lc header and code=start/code=end markers used by the VSCode LeetCode extension
• Use Your Existing Workspace — Opens solution files from your current workspace directory (e.g. {id}.{title}.js)
• No External CLI — Communicates directly with LeetCode's GraphQL API via curl
• Problem Browser — Browse and search problems with fzf-lua integration
• Run & Submit — Run test cases and submit solutions without leaving Neovim
• Problem Description — View problem descriptions in a split window
• Dual Site Support — Works with both leetcode.cn and leetcode.com

Requirements

• Neovim >= 0.10
• curl (for HTTP requests)
• fzf-lua (for the problem picker)

Installation

Using lazy.nvim:

{
  "your-username/leetcode-compat.nvim",
  dependencies = { "ibhagwan/fzf-lua" },
  cmd = { "LCList", "LCOpen", "LCRun", "LCSubmit", "LCDesc", "LCAuth", "LCInfo" },
  keys = {
    { "<leader>ll", "<cmd>LCList<cr>",   desc = "LeetCode: Browse problems" },
    { "<leader>lr", "<cmd>LCRun<cr>",    desc = "LeetCode: Run test cases" },
    { "<leader>ls", "<cmd>LCSubmit<cr>", desc = "LeetCode: Submit solution" },
    { "<leader>ld", "<cmd>LCDesc<cr>",   desc = "LeetCode: Problem description" },
    { "<leader>li", "<cmd>LCInfo<cr>",   desc = "LeetCode: Problem info" },
  },
  opts = {
    -- see Configuration below
  },
}

For local development, use dir instead of the GitHub URL:

{
  dir = "~/Documents/leetcode-nvim",
  -- ... same config as above
}

Configuration

All options with their default values:

{
  -- Path to your solution files directory
  -- Compatible with VSCode LeetCode extension's workspace
  workspace = vim.fn.expand("~/leetcode"),

  -- Default language for new files
  lang = "javascript",

  -- Use leetcode.cn (China) instead of leetcode.com
  cn = true,

  -- Path to store the authentication cookie
  cookie_path = vim.fn.stdpath("data") .. "/leetcode-compat/cookie",

  -- File naming pattern
  -- Available variables: ${id}, ${slug}, ${title}, ${cn_title}, ${ext}
  file_pattern = "${id}.${cn_title}.${ext}",

  -- Language to file extension mapping
  lang_ext = {
    javascript = "js",
    typescript = "ts",
    python3 = "py",
    java = "java",
    cpp = "cpp",
    c = "c",
    golang = "go",
    rust = "rs",
    -- ... and more
  },

  -- Picker type: "fzf" | "telescope" | "vim_select"
  picker = "fzf",

  -- Problem description window position and width
  desc_position = "right",
  desc_width = 80,
}

Commands

Command	Description
:LCList	Browse problems (opens fzf picker)
:LCOpen {n}	Open problem by number (e.g. :LCOpen 1)
:LCRun	Run test cases for current file
:LCSubmit	Submit solution for current file
:LCDesc	Toggle problem description window
:LCAuth	Set LeetCode authentication cookie
:LCInfo	Show current problem info

Authentication

This plugin requires a LeetCode session cookie for API access.

How to Get Your Cookie

1. Log in to leetcode.cn (or leetcode.com) in your browser
2. Open DevTools (F12) → Application → Cookies
3. Copy the values of LEETCODE_SESSION and csrftoken
4. Run :LCAuth in Neovim and paste in this format:

   LEETCODE_SESSION=xxx; csrftoken=xxx
   

The cookie is stored locally at ~/.local/share/nvim/leetcode-compat/cookie.

VSCode Compatibility

This plugin reads and writes the same file format as the VSCode LeetCode extension:

/*
 * @lc app=leetcode.cn id=1 lang=javascript
 *
 * [1] Two Sum
 */
// @lc code=start
var twoSum = function(nums, target) {
    // your solution
};
// @lc code=end

• The @lc header stores problem metadata (site, ID, language)
• Code between // @lc code=start and // @lc code=end is extracted for submission
• File naming follows the same {id}.{title}.{ext} convention

You can seamlessly switch between VSCode and Neovim — both tools read the same files.

License

MIT