Openleetcode – Local LeetCode runner where tests live in the repo

You write a standard solution, just like on LeetCode, and run it through the CLI. It identifies the problem by ID or title, executes your code against local test cases, and shows the result.It currently supports around 1.4k problems and multiple languages, including Python, C++, Rust, Java, Go, TypeScript, Swift, and others.The project is still an MVP. System design, SQL, and concurrency problems are not supported yet, but support for more problem types is planned.Made in Haskell!

Hacker NewsToolAISource
0Sign in to voteCopy link

FL score

42

out of 100

Verdict

SKIP

medium confidence

Competition

No competitor data yet

Trend

No signal yet

A CLI tool that lets developers practice LeetCode problems locally with their own test infrastructure instead of using the web platform.

The pain

LeetCode users waste time context-switching between their IDE and the web platform, can't version control their solutions easily, and can't integrate problem-solving into their existing development workflow. They also have no way to run problems offline or customize test execution.

The gap

LeetCode is a closed platform. There's friction between where people want to code (their IDE) and where they have to code (the browser). Local execution removes that friction, but only if the tool is significantly better than just copying problems into a text file.

Build angle

Position this as a developer experience layer on top of LeetCode's problem set. The real value isn't the problems themselves, it's making them feel native to a developer's workflow. Focus on: (1) seamless integration with git/GitHub, (2) running problems in CI/CD pipelines, (3) tracking progress across teams, (4) offline-first capability. Start by validating whether competitive programmers actually want this versus just using LeetCode's interface.

Strengths

  • Solves a real friction point in the LeetCode workflow
  • Multi-language support from day one shows technical depth
  • MVP exists with 1.4k problems already integrated
  • Built in Haskell suggests strong engineering foundation
  • Can be distributed as a single binary (CLI tools have low friction)

Risks

  • LeetCode could add offline/local features and eliminate the need
  • Unclear if the target user (competitive programmers) actually wants this, they may prefer the gamification and social features of the web platform
  • No monetization model articulated; hard to charge for a tool that wraps free content
  • Maintenance burden: keeping 1.4k problems in sync as LeetCode updates them
  • Limited TAM: only appeals to people actively doing LeetCode, not beginners or casual learners
  • Haskell is a liability for adoption and maintenance, most developers won't contribute
  • Missing system design and SQL problems limits appeal to senior engineers preparing for real interviews

Questions about this idea?

FlyBot reads the scoring and gives you a second opinion on “Openleetcode – Local LeetCode runner where tests live in the repo”.

Open FlyBot