# leetcode-cli mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für leetcode-cli in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:leetcode-cli
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install leetcode-cli
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#leetcode-cli
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/le/leetcode-cli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:leetcode-cli
- **Paketmanager:** Homebrew
- **Version:** 0.5.4
- **Quellzusammenfassung:** May the code be with you
- **Homepage:** <https://github.com/clearloop/leetcode-cli>
- **Repository:** <https://github.com/clearloop/leetcode-cli>
- **Zuletzt aktualisiert:** 2026-06-29T07:59:28Z
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- leetcode (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 0.5.4
## Projektgeschichte und Nutzung

clearloop's `leetcode-cli` is a Rust command-line client for LeetCode workflows: picking problems, opening generated solution files, running sample tests, submitting solutions, filtering problem lists, and managing local cache data.

### Projektgeschichte

The project is distributed from GitHub and crates.io-style Rust installation paths, with the README emphasizing `cargo install leetcode-cli`, a Nix flake, shell completions, and local configuration.

A notable configuration milestone appears in the v0.4.0 release on 2024-06-24, which introduced the documented TOML configuration layout for editor, cookies, and storage. Later releases expanded everyday coding-practice ergonomics, including daily challenge flags, LeetCode China support, environment-variable cookie overrides, clap-derived commands, and README/docs restructuring.

### Adoptionsgeschichte

The repository shows hundreds of stars and dozens of forks, and the input package facts list Homebrew and Nix packaging. That puts it in the small but active ecosystem of terminal-first LeetCode clients used by programmers who want editor-centric practice instead of browser-only workflows.

### Wie es verwendet wird

The README's quickstart has users sign in to LeetCode in a browser, then run commands such as `leetcode pick`, `leetcode edit`, `leetcode test`, and `leetcode exec`. On macOS and Linux, the tool can read Chrome cookies automatically; manual cookie setup and environment-variable overrides are documented for other cases.

### Warum Paket-Nerds sich dafür interessieren

The package is interesting because it packages an authenticated web-workflow CLI: browser cookies, local code generation, editor integration, shell completions, SQLite/OpenSSL build concerns, and LeetCode API changes all meet in one terminal tool.

### Zeitleiste

- 2024-06-24: v0.4.0 release introduced the documented TOML configuration format.
- 2024-12-24: v0.5.0 release switched command definitions to clap derive.
- 2026-06-21: v0.5.1 release notes document README/docs restructuring and macOS Chrome-cookie fixes.
- 2026-06-21: v0.5.2 release bundled SQLite to reduce system build dependency friction.

### Related projects

- It overlaps with other LeetCode CLIs in this batch, especially `leetgo`, `leetup`, and older JavaScript-era LeetCode command-line clients, but clearloop's implementation is Rust-centered and packaged for cargo, Homebrew, and Nix users.

### Quellen

- <https://crates.io/crates/leetcode-cli>
- <https://github.com/clearloop/leetcode-cli>
- <https://github.com/clearloop/leetcode-cli/releases>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.leetcode/leetcode.toml

## Credential files

- Unix: ~/.leetcode/leetcode.toml
## Andere Paketmanager-Einträge

- Nix - leetcode-cli: normalized package name match | nixpkgs package indexes: pkgs/by-name/le/leetcode-cli/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/leetcode-cli.yml](https://github.com/mxcl/pkgdb/blob/main/combined/leetcode-cli.yml)


## Quellen

- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph