openleetcode

openleetcode [--plain] [--no-color] [--version] command [args]openleetcode submit PATH {--id INT | --title STR} [--lang LANG]openleetcode download {all | runtimes | tests}openleetcode config listopenleetcode config set KEY VALUEopenleetcode update

openleetcode is a Haskell CLI that judges LeetCode-style solutions on your machine. It reads a normal solution file, finds the matching problem manifest in a downloaded open test suite, wraps the code in a language-specific harness, sends the batch to a pluggable execution backend, and reports LeetCode-like verdicts locally.The CLI is the glue. Tests live as per-problem directories (`manifest.yaml` plus reference solutions). Runtime templates (entry `main` plus utilities for arrays, linked lists, trees, and similar LeetCode types) live next to them. Neither is bundled inside the binary: first interactive start creates the XDG config directory and offers to download both. Non-interactive starts skip that prompt; run openleetcode download all yourself.submit requires a selector. --id looks under `tests/<range>/` for a directory whose name starts with `<id>.`. --title does a substring search of directory names and takes the first hit. Language comes from the file extension unless --lang is set. The runner talks to the configured backend (default Piston at `http://localhost:2000`); a 20-second batch timeout applies. Verdicts include accepted, wrong answer, time limit exceeded, and runtime error. The project is not affiliated with LeetCode; it aims to keep imports and environments close to the official language setups.

--plain

Disable animations and colors. Output is line-oriented (`scope: message`).

Disable ANSI colors. `NO_COLOR` in the environment has the same effect.

Print `openleetcode <version>` and exit.

Run the solution file against a local test suite. Either --id or --title is required.

Problem id (for example `1` for Two Sum). Takes precedence over --title when both are given.

Substring matched against problem directory names under the downloaded tests tree. The first match is used.

Override language detection from the file extension. Supported values include `cpp`, `rust`, `python3`, `python2`, `ruby`, `java`, `csharp`, `kotlin`, `go`, `dart`, `swift`, and `typescript`.

Fetch the upstream repository archive and unpack runtime templates, test manifests, or both into the data directory.

Print `backend.type`, `backend.url`, and the config file path.

Write a config key. Allowed keys: `backend.type` (currently only `piston`) and `backend.url`.

Download the official installer and run it (`bash` on Unix, PowerShell on Windows).

$XDG_CONFIG_HOME/openleetcode/ (default ~/.config/openleetcode/)

Data directory created on first run. Holds `config.yml`, unpacked `runtimes/`, and unpacked `tests/`.

YAML with `backendType` and `backendUrl`. Created automatically with defaults if missing. A parse error falls back to defaults and prints a warning.

CLI keys for config set. The only allowed type is `piston`. Default URL is `http://localhost:2000`.

Used as the default backend URL when a new config is created. It does not override an existing `config.yml`.

Judging requires a reachable backend. If Piston is down, submit exits with an infrastructure error and suggests config list. Tests and runtimes must already be downloaded; a missing suite prints "test suite not found". --title is an unanchored substring and uses the first match, so short titles can hit the wrong problem. Manifests are community-maintained and vary in quality. update re-runs a remote installer script. Exit codes are 0 (success / accepted), 1 (bad input: missing selector, unknown extension, missing suite), 2 (infrastructure: backend, download, config write), and 3 (solution verdict failure).

Written in Haskell (Cabal) by therepanic. The repository was published in January 2026. Licensed under the Unlicense. The executable name is openleetcode.

docker(1), docker-compose(1), cabal(1), python(1), rustc(1)

Source code