shuzijun/leetcode-editor

Do Leetcode exercises in IDE, support leetcode.com and leetcode-cn.com, to meet the basic needs of doing exercises.Support theoretically: IntelliJ IDEA...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 17th, 2026
Created on March 19th, 2019
Open Issues & Pull Requests: 142 (+0)
GitHub issues: Enabled
Number of forks: 423
Total Stargazers: 3,982 (+0)
Total Subscribers: 33 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.9 days
Mean response time: 68.4 days
90th percentile: 299.9 days
Tracked items: 25

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 32
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 599 days
Stale 30+ days: 30
Stale 90+ days: 25

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

LeetCode Editor is a JetBrains IDE plugin that lets you solve LeetCode problems without leaving your development environment, supporting both leetcode.com and leetcode.cn.

The tool addresses the friction of switching between a code editor and a web browser when practicing algorithm problems. It integrates problem browsing, local code editing, debugging, and submission directly into JetBrains IDEs including IntelliJ IDEA, PyCharm, WebStorm, GoLand, and others. Users configure their LeetCode credentials and preferred programming language within the IDE settings, then browse problems through a navigator panel, write and test solutions locally with full IDE features, and submit directly to LeetCode.

The plugin suits developers who spend most of their time in JetBrains IDEs and want to maintain workflow continuity while practicing algorithms. It works across multiple programming languages and supports custom code templates for personalized problem setup. The tool is particularly valuable for those who prefer local debugging over browser-based coding environments.

The project receives issue reports primarily from its user base rather than internal sources, indicating substantial real-world adoption. Responses to issues and pull requests typically arrive within one to two weeks. Bug reports dominate the issue tracker, suggesting the maintainers focus on stability and correctness rather than feature expansion.