LeetCode VS Code Authy

VS Code extension:

Browser extension:

Solve LeetCode problems in VS Code with a companion browser extension that syncs your signed-in leetcode.com session to a local VS Code listener.

This independent project is maintained by wilmtang at wilmtang/leetcode-vscode-authy. It is not affiliated with, endorsed by, sponsored by, or published by LeetCode. The original MIT license and copyright notices are preserved in LICENSE, with source attribution in NOTICE.md.

Older LeetCode VS Code workflows can break when LeetCode changes auth, CSRF, or bot-protection behavior. This project keeps the workflow local and direct:

• No manual cookie copying: sign in to leetcode.com in your browser, then sync that browser session into VS Code.
• More reliable test and submit: VS Code reuses the synced cookie and captured browser request headers.
• Local-first sync: session data is posted only to the VS Code listener on 127.0.0.1.
• Useful failure messages: auth-sync and Cloudflare failures surface as explicit sync/debug messages instead of generic login errors.

leetcode.cn support is currently broken and untested. Favorites and Solutions do not work on .cn after the move to direct API calls. Details live in docs/maintainer-guide.md.

Install both pieces on the same machine:

1. Install LeetCode VS Code Authy from the VS Code Marketplace or Open VSX.
2. Install the companion browser extension:
   • Firefox Add-ons
   • Chrome Web Store
3. Sign in to leetcode.com in that browser.
4. In VS Code, open the LeetCode side bar, click Sign In, and choose Auto Cookie Sync.
5. In the browser extension popup, click Expire now, then open or refresh any leetcode.com page.

When sync succeeds, the VS Code notification closes, the LeetCode side bar refreshes, and test/submit commands use the same LeetCode session as your browser.

If a browser store listing is not available for your browser, load browser-extension/ manually from a local checkout. See Local Development.

• Browse, search, preview, and open LeetCode problems from the VS Code side bar.
• Generate local solution files under the configured workspace folder.
• Run tests and submit solutions from editor CodeLens shortcuts.
• Star and unstar problems on the validated leetcode.com endpoint.
• Click the LeetCode: <username> status bar item to open a personal stats panel with solved counts, ranking, language stats, and recent accepted submissions.
• Sync auth from Chrome, Chromium, or Firefox through the companion browser extension.

Core commands:

• LeetCode: Sign In
• LeetCode: Sign Out
• LeetCode: Show User Profile
• LeetCode: Search Problem
• LeetCode: Pick One
• LeetCode: Show Browser Auth Sync Status
• LeetCode: Restart Browser Auth Sync Server

Browser extension controls:

• Expire now: bypasses the cooldown for the next real LeetCode request.
• Cookie-only sync: optional advanced button that sends cookies immediately, without browser request headers.
• Enabled: turns browser-side sync on or off.
• Port: must match leetcode.authSync.port in VS Code. Default: 17899.
• Shared secret: optional. If set in VS Code, set the same value in the browser extension.
• Cooldown: controls how often automatic browser sync can run after a successful unchanged-session sync.

The browser extension does not log in to LeetCode by itself. It copies the already-signed-in browser session into VS Code over a loopback-only HTTP endpoint.

flowchart LR
    A["You sign in on leetcode.com"] --> B["Browser extension reads LeetCode cookies"]
    B --> C["POST http://127.0.0.1:17899/auth/update"]
    C --> D["VS Code auth-sync server"]
    D --> E["Session stored in VS Code secrets"]
    E --> F["LeetCode explorer refreshes"]
    E --> G["Browse, test, and submit use the synced session"]

Important details:

• The VS Code extension listens on 127.0.0.1 only. Default endpoint: POST http://127.0.0.1:17899/auth/update.
• The health endpoint is GET http://127.0.0.1:17899/health.
• If several VS Code windows are open, only one owns the listener. Other windows verify the live owner through /health and can take over when that listener is gone.
• Automatic sync observes LeetCode XHR/fetch requests and respects the configured cooldown after a successful unchanged-session sync.
• Expire now bypasses the cooldown for the next real LeetCode request.
• Cookie values are sent only to the local VS Code listener and are not intentionally logged.
• If leetcode.authSync.secret is set, the browser extension must send the same value in the X-LeetCode-AuthSync-Secret header.

leetcode.authSync.secret is empty by default for zero-config local sync. With no secret set, the listener accepts a request that reaches 127.0.0.1:<port> and carries a valid LeetCode session cookie, as long as it is not identified as a cross-site browser request.

That blocks ordinary malicious websites through the Origin/CORS checks, but it is not a boundary against another local process on the same machine. If you do not trust local processes or other local users, set leetcode.authSync.secret in VS Code and enter the same value in the browser extension settings.

Install dependencies:

npm ci --replace-registry-host=always

Common commands:

npm run compile
npm test
npm run local -- vscode:dev
npm run local -- vscode:install
npm run local -- chrome:dev
npm run local -- chrome:dev-current
npm run auth-sync:lint:firefox
npm run auth-sync:build:firefox
npm run auth-sync:build:chrome

Manual browser-extension loading:

• Chrome: open chrome://extensions, enable Developer mode, click Load unpacked, and select browser-extension/.
• Firefox: open about:debugging#/runtime/this-firefox, click Load Temporary Add-on, and select browser-extension/manifest.json.

End-to-end local smoke test:

1. Start VS Code locally with npm run local -- vscode:dev.
2. Start the browser extension with npm run local -- chrome:dev, or load it manually.
3. Sign in to https://leetcode.com in that browser profile.
4. In VS Code, choose LeetCode: Sign In, then Auto Cookie Sync.
5. In the browser extension popup, click Expire now, then open or refresh any leetcode.com page.
6. Confirm the VS Code waiting notification closes and the LeetCode explorer refreshes as signed in.
7. Run a problem test or submit command to confirm the synced cookie works.

For the full local workflow, current caveats, audit notes, and release process, see docs/maintainer-guide.md.

• VS Code 1.57.0+

No Node.js runtime is required for extension users. The extension talks to LeetCode directly over HTTP/GraphQL using your synced browser cookie. On the rare occasion LeetCode serves a Cloudflare challenge, the extension falls back to the system curl, which ships with macOS, Windows 10+, and most Linux distributions.

Check the Troubleshooting and FAQ pages first. If the issue is still unresolved, file an issue.

See CHANGELOG.md.

This extension originated from @jdneo's vscode-leetcode, which built on @skygragon's leetcode-cli. This project no longer bundles leetcode-cli; it talks to LeetCode directly using a synced browser cookie.

Special thanks to the project contributors.