Library / SDK
shuzijun/leetcode-editor avatar
shuzijun/leetcode-editor

LeetCode Editor puts two sites, fifteen languages and a cache in one settings page

Do Leetcode exercises in IDE, support leetcode.com and leetcode-cn.com, to meet the basic needs of doing exercises.Support theoretically: IntelliJ IDEA PhpStorm WebStorm PyCharm RubyMine AppCode CLion GoLand DataGrip Rider MPS Android Studio

3,993 stars418 forksJavaApache-2.0

At a glance

What is it?
shuzijun/leetcode-editor is a JetBrains plugin that browses, debugs and submits LeetCode problems without leaving the IDE, and it works against two different sites with independent accounts. The configuration surface is small but consequential: a site switch, a login name and password, fifteen language choices, a temporary file directory, and a cache the toolbar can delete.
Who is it for?
This plugin earns its place for someone who already lives in a JetBrains IDE and wants problem statements, notes, submissions and local runs in the same window as the code. It is a worse choice if you want to work outside JetBrains tools, if you mind that two account systems have to be kept separate, or if you keep unsubmitted work in the cache, because the toolbar can delete those files for the current site in one click.
Can I use it commercially?
Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 94 days ago.
What is it written in?
Mainly Java, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • shuzijun/leetcode-editor3,993 ★ · +11
Star history
Repository2026-09-242026-11-15
shuzijun/leetcode-editor4k4k

11 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Two sites, two independent accounts, one pair of credentials

The plugin's first decision is which site it talks to. There is a URL option in the settings with exactly two values, `leetcode.com` and `leetcode.cn`, and everything else follows from that choice, including the login. The configuration page asks for a login name and a password for the selected site, and the toolbar's sign in action is where you supply them. The two account systems are independent, so a subscriber account on one site says nothing about the other, and the toolbar carries a separate session action for viewing or switching sessions. Two behaviours are worth knowing before you get stuck. If sign in fails, the page's advice is to sign out first and try again, which implies the plugin holds session state it will not overwrite by asking again. And the refresh action loads the problem list without signing in at all, while submitting still requires an account, so you can browse and plan before committing to a login. The HTTP proxy, when you need one, is not configured on the plugin page but through the IDE's own system settings.

Fifteen code types, including Python and Python 3 as separate entries

The code type list on the settings page has fifteen entries: Java, Python, C++, Python 3, C, C#, JavaScript, Ruby, Swift, Go, Scala, Kotlin, Rust, PHP, Bash and SQL. Python and Python 3 appear as separate choices rather than one version aware option, which is the kind of detail that dates a plugin, since it means the template selection is fixed rather than negotiated with the site. The plugin itself is written in Java, so the target language and the implementation language are unrelated, and the generated code is a starting point you can replace. Three more settings change what the plugin produces rather than what it talks to. A temporary file path decides where generated temporary files land. A custom code template lets you rewrite the generated code entirely, with a separate documentation page and an example to copy. And the level colour setting, which changes the problem difficulty colours, needs the IDE restarted before it takes effect, the only setting on the page that does.

The cache holds the files the toolbar can delete

One toolbar entry deserves a paragraph of its own. Clear is described as removing files from the cache directory for the current website, and the page tells you to use it carefully when work has not been submitted. That is the honest warning: the working copy of a problem you are editing lives in that cache, the deletion is scoped to one site rather than both, and nothing in the description suggests a confirmation step or a backup. There is a second, narrower version of the same action in the problem context menu, where clear cache removes the cached files for the current problem only. Reading the two together suggests the intended use is switching cleanly between sites or discarding a problem you have finished with, rather than routine housekeeping. If you keep notes in the plugin's note view, those notes are part of the per problem state that the problem level clear touches, so treat the toolbar button as a reset of local work rather than a cache eviction.

Three problem list modes, one of them a curated CodeTop list

The navigator has a toggle that switches between three views of the same catalogue: the all problems list, a paginated problem list, and a CodeTop problem list. The first is the complete set, the second splits it into pages, and the third is a curated selection. Alongside them sit a find panel for searching, filtering and sorting, and a pick action that opens a random problem, which is the fastest way to start a session when you have not decided what to work on. The status bar carries a timer for tracking how long you have been on a problem, and the submissions action opens the record list with a show detail option in a pop-up window. Run code executes the default test case for the problem, and a separate testcase action is there for writing your own, so the local loop does not need the browser at all.

The IDE list is longer than the project's own confidence in it

The page names twelve JetBrains IDEs as supported: IntelliJ IDEA, PhpStorm, WebStorm, PyCharm, RubyMine, AppCode, CLion, GoLand, DataGrip, Rider, MPS and Android Studio. The repository description lists the same set with a caveat that is easy to miss, saying the support is theoretical rather than stating it outright. That is the honest reading of any plugin marketplace listing: the plugin is a JVM artifact, so it loads in anything built on the platform, but each IDE's own integration surface differs, and DataGrip, MPS and Android Studio are the ones where a database tool, a language workbench and a mobile IDE have little in common with the editor the plugin was written for. The README does not claim that, which is why the difference between the two descriptions is worth noticing before you pick an IDE for the purpose.

Two plugins with two marketplace ids and a version scheme change

There are two listings, not one. The free plugin is number 12132 on the JetBrains marketplace, and the version badge for the Pro plugin points at a different id, 17166, so they are separate installations rather than a paid tier of the same plugin. The README links a support page for the Pro version in its installation list, alongside installing from the marketplace and downloading a package from the repository's releases. The release history shows what looks like a scheme change. Three releases are listed: a 2024.1.7 entry from 2025-10-30, then two published within a minute of each other on 2026-08-13, one numbered 9.0.0 and one numbered 2026.2.0 with the Pro name attached and a public tag. So the project moved from a plain dotted number to a year and build number in the same style the IDE platform itself uses, and the free and Pro lines now carry different suffixes on their tags.

Two sections of the page are empty paragraphs where screenshots belong

The document leans on images, and where the images are missing the text is missing too. The Getting Started section and the Local debugging section each contain a single empty centred paragraph and nothing else, so the parts of the page a new user most needs, how to get from installation to a first run, have no written content on the repository at all. The icons and badges are loaded from a CDN that points at the master branch of this repository rather than at a release, so the artwork follows whatever is on the branch. Two workflow badges report release and snapshot build status for that same branch. The repository itself is a Gradle project with a wrapper for Linux and Windows, and there are no build instructions anywhere on the page, which is consistent with a plugin whose distribution path is the marketplace or a release archive rather than a source build.

The extra functionality lives in a second repository

The repository is a Java plugin project with a changelog, a Gradle build, a documentation directory, an action directory and two readmes, one English and one Chinese. Beyond that sit three documentation links the page points at separately: an English document, a Chinese document, and a login help page, which tells you that the sign in flow has its own instructions rather than being self evident from the toolbar. A custom code page with a worked example covers the template override, and a second repository is linked for what the page calls more open functionality, so the division of labour is that this repository holds the IDE plugin and that other project holds the pieces that are not tied to a JetBrains toolchain. For anyone deciding whether the plugin fits, that split is the useful detail: the parts that would survive a move to another editor are the ones published separately.

Editorial conclusion

This plugin earns its place for someone who already lives in a JetBrains IDE and wants problem statements, notes, submissions and local runs in the same window as the code. It is a worse choice if you want to work outside JetBrains tools, if you mind that two account systems have to be kept separate, or if you keep unsubmitted work in the cache, because the toolbar can delete those files for the current site in one click. Before you install it, check four things. Which of the two sites you will use and whether your account exists there, since sign in is configured per site and the accounts are independent. Which of the fifteen code types matches the language you want to practise, and whether you need the template override at all. Where the generated temporary files go, since that directory is your choice and it is separate from your project. And whether you want the free plugin or the Pro one, which is a separate listing on the marketplace with its own plugin id and its own release naming.

Frequently asked questions

Which sites does LeetCode Editor support?

It supports leetcode.com and leetcode.cn, chosen through a URL option in the plugin settings. Accounts for the two sites are independent, the problem list can be refreshed without signing in, and submitting still requires an account on the selected site.

Which languages can LeetCode Editor submit code in?

The code type setting offers fifteen choices: Java, Python, C++, Python 3, C, C#, JavaScript, Ruby, Swift, Go, Scala, Kotlin, Rust, PHP, Bash and SQL. A custom code template can replace the generated code entirely.

Which JetBrains IDEs does LeetCode Editor run in?

The page names IntelliJ IDEA, PhpStorm, WebStorm, PyCharm, RubyMine, AppCode, CLion, GoLand, DataGrip, Rider, MPS and Android Studio. The repository description lists the same IDEs while describing the support as theoretical.

What does the Clear button in LeetCode Editor delete?

It removes files from the cache directory for the current website, and the page says to use it carefully when work has not been submitted. The problem context menu has a separate clear cache entry that removes cached files for the current problem only.

Is there a paid version of LeetCode Editor?

There is a separate Pro plugin with its own marketplace listing and plugin id alongside the free one, and the installation section links a support page for it. The two lines also carry different suffixes on their release tags.

Official sources

  1. License: Apache-2.0
  2. Project website
  3. README
  4. Releases
  5. shuzijun/leetcode-editor on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/shuzijun-leetcode-editor.svg)](https://hysenlabs.com/projects/shuzijun-leetcode-editor)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/shuzijun-leetcode-editor.svg)](https://hysenlabs.com/projects/shuzijun-leetcode-editor)

Was this useful?