gitwtfhub

wtf is lcx?

harryycchou/lcx — explained in plain English

Analysis updated 2026-05-18

13RustAudience · developerComplexity · 2/5LicenseSetup · easy

TL;DR

A terminal application for browsing, solving, testing, and submitting LeetCode problems without leaving the command line.

Mindmap

mindmap
  root((lcx))
    What it does
      Interactive TUI for LeetCode
      CLI subcommands for scripting
      Local problem cache
    Tech stack
      Rust
      LeetCode GraphQL API
      TUI framework
    Use cases
      Solve LeetCode problems in the terminal
      Test and submit solutions via CLI
      Track daily challenges
    Audience
      Developers practicing coding interviews
      Terminal-first programmers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Browse and solve LeetCode problems entirely from the terminal.

REASON 2

Test and submit solutions using CLI subcommands for scripting workflows.

REASON 3

Track and scaffold the daily LeetCode challenge automatically.

What's in the stack?

RustLeetCode API

How it stacks up

harryycchou/lcxanthropics/cargo-nix-pluginbrassworks-smp/brassworkslauncher
Stars131313
LanguageRustRustRust
Setup difficultyeasyhard
Complexity2/54/53/5
Audiencedeveloperdevelopergeneral

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

Windows cookie auto-detection requires running as administrator.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

Wtf does this do

lcx is a terminal application that lets you browse, read, write, test, and submit LeetCode coding problems without opening a web browser. It connects directly to LeetCode's own API and keeps a local cache of the problem list, so browsing problems feels instant once that cache is built. Running the program with no extra options opens a full interactive text interface inside your terminal, complete with a login screen, a dashboard showing your profile stats and a searchable problem list, and a solve screen with the problem description on one side and your code on the other. People who prefer scripting or one off commands can instead use individual subcommands to list problems, show a specific one, generate a solution file, run tests, or submit for a verdict, all without touching the interactive interface. Since LeetCode has no official public API for this kind of use, lcx logs in the same way your browser does, using session cookies. It can often detect these automatically from a browser you are already signed into, though on Windows this auto detection needs administrator permissions because Chrome, Edge, and Brave encrypt their cookies more strictly there. You can also copy your session cookie values in manually if you prefer not to grant that access. Installation is straightforward on Linux, macOS, and Windows through prebuilt binaries attached to each release, or you can build it from source if you have a recent Rust toolchain installed. The project separates its core logic, the part that talks to LeetCode and manages the cache, from its interface layer, so the command line tools and the interactive interface share the same underlying code. This tool is aimed at developers who practice coding problems on LeetCode and prefer working from the terminal instead of a browser tab. It is released under the MIT License, so it can be freely used, modified, and shared.

Yoink these prompts

Prompt 1
Help me install lcx and log in using my browser session cookies.
Prompt 2
Explain how lcx's interactive TUI is organized for solving problems.
Prompt 3
Walk me through using lcx subcommands to test and submit a solution.
Prompt 4
Why does cookie auto-detection require administrator rights on Windows?

Frequently asked questions

wtf is lcx?

A terminal application for browsing, solving, testing, and submitting LeetCode problems without leaving the command line.

What language is lcx written in?

Mainly Rust. The stack also includes Rust, LeetCode API.

What license does lcx use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice.

How hard is lcx to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is lcx for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.