HarryYCChou/lcx

LeetCode in your terminal. Contribute to HarryYCChou/lcx development by creating an account on GitHub.

0 stars · 0 forks · Rust

README

lcx — LeetCode in your terminal

lcx lets you browse, read, solve, test, and submit LeetCode problems without leaving your terminal. It talks to the live LeetCode API (GraphQL + judge endpoints) and caches the problem list locally for instant browsing. Run it with no arguments for a full interactive TUI, or use the individual subcommands for scripting and one-offs. The core (HTTP client, cache, config) is deliberately separated from the presentation layer, so the CLI and TUI share the same LeetCode logic. Support Enjoying lcx? A little support goes a long way toward keeping it maintained:

Crypto Prefer crypto? Scan a QR code below, or expand "Copy wallet addresses" to copy one.

BTCBitcoin ETHEthereum (ERC-20) SOLSolana USDTTron (TRC-20)

Copy wallet addresses

BTC (Bitcoin): bc1qdj0jpd7kyx0zy33vaj4nqy86ljswhrda6n04kf ETH (Ethereum / ERC-20): 0x612a806a87e0d99f2a7492dbb875cca6f056fa57 SOL (Solana): ELcq1ibh4zcmueHF4MocpntZ3atcdfkei2gW9ybvmCRx USDT (Tron / TRC-20): TS1wPw1MR5PXvfC4R62jMgVzn5FYMTDnB4

Demo

lcx.mp4

Screenshots Login modal — auto-detects browser cookies:

Main dashboard — menu, profile stats, and problem search:

Solve view — description, solution preview, and test/submit output:

Installation Prebuilt binaries are attached to the latest release. Linux

x86_64

Apple Silicon

universal (works with or without Homebrew)

or, if you use Homebrew (already on PATH, no sudo needed):

binary at ./target/release/lcx

1. Populate the local problem cache

2. Launch the interactive TUI

From here everything happens inside the TUI:

3. Log in <F1> opens the login modal; it auto-detects your browser

cookies (<F3> opens the LeetCode login page), then <Enter>

manual login? see "Finding your session cookies" below

4. Set language first time only: <Tab> to the menu, pick "Set default

language", <Enter> to choose (used for new solution files)

5. Pick a problem <Tab> back to search, type to filter, <↑>/<↓> move, <Enter> open

6. Write code <e> (or <Enter>) opens the file in $EDITOR; <r> starts over

7. Test & submit <t> runs the sample cases, <s> submits for a verdict

<Esc> goes back to the list (<Esc> again quits)

Windows: cookie auto-detect with Chrome/Edge/Brave needs an admin PowerShell — see Authentication for details.

TUI at a glance

Login modal — hands-free cookie auto-detection (F3 open login page, F2 toggle auto-detect, F4 browse offline, Esc cancel). Function keys are used because multiplexers like tmux reserve the Ctrl prefix. Main dashboard — Tab switches focus between the action menu (set language, login, delete cache, reset config, quit) and the problem search; F5 refresh, F1 login, Esc quit. Solve view — left: description with LeetCode's inline markup preserved; right: read-only solution preview. e/Enter edit in $EDITOR, r start over, Tab cycle panes, j/k scroll, t test, s submit, Esc back.

Commands

Command Description

lcx Launch the interactive TUI (default)

lcx login [--session <s>] [--csrf <c>] Save session credentials (prompts if omitted)

lcx whoami Show the currently authenticated user

lcx list [--difficulty] [--tag] [--status] [--query] [--limit] List cached problems with filters

lcx show <id|slug> [--lang] [--code] Show a problem's description (optionally starter code)

lcx pick <id|slug> [--lang] [--no-open] Generate a solution file and open it

lcx edit <id|slug> [--lang] [--no-open] Reopen (or generate) a solution file

lcx test <id|slug|path> [--case] [--lang] Run a solution against sample/custom cases

lcx submit <id|slug|path> [--lang] Submit a solution and print the verdict

lcx daily [--pick] Show today's daily challenge (optionally scaffold it)

lcx cache [--update] [--clear] Manage the local problem cache

lcx config [set <key> <value>] View or change configuration (lang, editor, workspace)

Authentication LeetCode has no official API, so lcx uses the same session cookies your browser does.

Easiest: launch lcx and let the login modal auto-detect cookies from a browser you're already signed into (press F3 to open the login page first). On Windows, Chrome/Edge/Brave encrypt cookies with app-bound encryption, so auto-detect can only read them if you run lcx as administrator — right-click PowerShell -> "Run as administrator" (or run Start-Process powershell -Verb RunAs), then run lcx. Firefox and the manual method below work without admin. Manual: copy your LEETCODE_SESSION and csrftoken cookies (see Finding your session cookies), then:

lcx login --session "<LEETCODE_SESSION>" --csrf "<csrftoken>"

or just `lcx login` to be prompted

Open leetcode.com in your browser and sign in. Open your browser's developer tools:

Chrome / Edge / Brave: F12 (or Ctrl+Shift+I, Cmd+Option+I on macOS) → Application tab → Storage → Cookies → https://leetcode.com. Firefox: F12 → Storage tab → Cookies → https://leetcode.com.

Find these two rows and copy each Value:

LEETCODE_SESSION — a long token (this is your session). csrftoken — a shorter token.

Pass them to lcx login as shown above.

Treat these like a password: they grant access to your LeetCode account. They expire periodically, so if requests start failing, grab fresh values or run lcx login again. Advanced: work from the command line Prefer to skip the TUI? The whole solve loop is available as plain commands: lcx login # sign in (see Authentication / Finding your session cookies) lcx list --difficulty easy # browse problems lcx pick 1 --lang rust # scaffold a solution file and open your editor lcx test 1 # run against sample cases lcx submit 1 # submit for a verdict More examples: lcx list --tag array --status todo --query "two sum" --limit 20 lcx show two-sum --code lcx test ~/lcx/1.two-sum.rs lcx test 1 --case $'[2,7,11,15]\n9' lcx daily --pick lcx config set editor "code -w" Solution files are written to the workspace directory as {id}.{slug}.{ext} with a metadata header comment so test/submit can identify the problem automatically. Config lives at ~/.config/lcx/config.toml, the cache at ~/.config/lcx/cache.sqlite, and solutions default to ~/lcx/. Supported languages rust, python3, cpp, c, java, csharp, javascript, typescript, go/golang, ruby, swift, kotlin, scala, php, dart, elixir, erlang, racket, mysql, and more. Set a default with lcx config set lang <slug> or override per command with --lang. Roadmap

leetcode.cn endpoint support Tag/difficulty/status filters inside the TUI browser Syntax highlighting in the solve-view code preview Submission history browsing

Contributing Contributions are welcome! Before opening a pull request, make sure the following pass: cargo fmt --all cargo clippy --all-targets -- -D warnings cargo test Guidelines:

Branch off main (feat/…, fix/…, chore/…). Use Conventional Commits (feat:, fix:, chore:, …); the type drives the version bump. Follow Semantic Versioning; the version lives in Cargo.toml, and notable changes go in CHANGELOG.md. Keep the client layer (src/client) free of presentation logic and reuse the shared helpers. Never commit credentials (config.toml, session/csrf cookies).

LeetCode's endpoints are unofficial and may change; if requests start failing, refresh your cookies with lcx login.

License MIT

source