Cursor Extension Marketplace Does not render extension

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I cannnot install/access any plugins in the extension market place.

Steps to Reproduce

idk

Screenshots / Screen Recordings

photo_2026-02-18_00-27-45.jpg
photo_2026-02-18_00-27-45.jpg310×131 12 KB

Operating System

Windows 10/11

Version Information

Version: 2.5.17 (user setup)
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

I inspected the extensionquery request in DevTools. The backend returns a valid JSON response with extension results (including TotalCount > 0), but the Marketplace UI still shows 0 extensions and does not render the results.

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report.

A few debugging questions:

  1. What country or region are you connecting from? Are you using a VPN, proxy, or a corporate firewall? There’s a known case where network-level filtering causes failures when fetching Marketplace data: Extenstions marketplace don't working

  2. Can you run Cursor Settings > Network > Run Diagnostics and share the full output here?

  3. In DevTools, are there any failed requests besides the main extensionquery call? For example, icon or extension metadata requests that error or time out. That could explain why the request succeeds but the UI doesn’t render.

Also, try opening https://marketplace.cursorapi.com directly in your browser and let me know if the page loads.

4

Hi,

I tested the issue both with and without a VPN, and the behavior is identical. The problem does not appear to be VPN-related.

I ran Cursor Settings → Network → Run Diagnostics (without VPN. HTTP/1.1). All checks passed successfully:

  • Cursor Network Diagnostic Results

    DNS: Success
    Logs:
    [2026-02-18T11:06:26.136Z] Host: link
    [2026-02-18T11:06:26.137Z] Servers: 8.8.8.8,8.8.4.4,198.18.0.2
    [2026-02-18T11:06:26.137Z] Resolved to 3.227.99.225 in 0ms
    [2026-02-18T11:06:26.224Z] Resolved to 3.227.99.225 in 8ms
    [2026-02-18T11:06:26.274Z] Resolved to 3.227.99.225 in 0ms
    [2026-02-18T11:06:26.295Z] Resolved to 3.227.99.225 in 11ms
    [2026-02-18T11:06:26.297Z] Host: api2.cursor.sh
    [2026-02-18T11:06:26.297Z] Servers: system
    [2026-02-18T11:06:26.297Z] Resolved to 3.227.99.225, 18.209.232.138, 52.4.99.64, 34.227.120.215, 3.213.214.236, 18.210.19.4, 54.83.36.117, 54.152.78.165 in 0ms
    [2026-02-18T11:06:26.297Z] Resolved to 3.227.99.225, 18.209.232.138, 52.4.99.64, 34.227.120.215, 3.213.214.236, 18.210.19.4, 54.83.36.117, 54.152.78.165 in 0ms
    [2026-02-18T11:06:26.308Z] Resolved to 3.227.99.225, 18.209.232.138, 52.4.99.64, 34.227.120.215, 3.213.214.236, 18.210.19.4, 54.83.36.117, 54.152.78.165 in 1ms
    [2026-02-18T11:06:26.309Z] Resolved to 3.227.99.225, 18.209.232.138, 52.4.99.64, 34.227.120.215, 3.213.214.236, 18.210.19.4, 54.83.36.117, 54.152.78.165 in 1ms
    [2026-02-18T11:06:26.309Z] Result: true

    SSL: Success
    Logs:
    [2026-02-18T11:06:26.009Z] Start
    [2026-02-18T11:06:26.659Z] URL: link
    [2026-02-18T11:06:26.659Z] Status: 200
    [2026-02-18T11:06:26.659Z] IP: 3.227.99.225
    [2026-02-18T11:06:26.660Z] Issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M01
    [2026-02-18T11:06:26.660Z] Name: api2.cursor.sh
    [2026-02-18T11:06:26.660Z] AltName: DNS:api2.cursor.sh, DNS:prod.authentication.cursor.sh, DNS:*.api2.cursor.sh
    [2026-02-18T11:06:26.660Z] DNS Time: 6ms
    [2026-02-18T11:06:26.660Z] Connect Time: 201ms
    [2026-02-18T11:06:26.660Z] TLS Time: 196ms
    [2026-02-18T11:06:26.660Z] Result: true in 651ms

    API: Success
    Logs:
    [2026-02-18T11:06:26.037Z] Start
    [2026-02-18T11:06:26.868Z] Result: true

    Ping: Success
    Logs:
    [2026-02-18T11:06:26.059Z] Sending ping 1
    [2026-02-18T11:06:27.079Z] Response: ‘ping’ in 1020ms
    [2026-02-18T11:06:27.079Z] Sending ping 2
    [2026-02-18T11:06:27.856Z] Response: ‘ping’ in 777ms
    [2026-02-18T11:06:27.856Z] Sending ping 3
    [2026-02-18T11:06:28.631Z] Response: ‘ping’ in 775ms
    [2026-02-18T11:06:28.631Z] Sending ping 4
    [2026-02-18T11:06:29.398Z] Response: ‘ping’ in 767ms
    [2026-02-18T11:06:29.398Z] Sending ping 5
    [2026-02-18T11:06:30.171Z] Response: ‘ping’ in 773ms
    [2026-02-18T11:06:30.171Z] Result: true

    Chat: Success
    Logs:
    [2026-02-18T11:06:26.083Z] Starting streamSSE
    [2026-02-18T11:06:27.072Z] Response: ‘foo’ in 960ms
    [2026-02-18T11:06:28.073Z] Response: ‘foo’ in 1001ms
    [2026-02-18T11:06:29.071Z] Response: ‘foo’ in 998ms
    [2026-02-18T11:06:30.074Z] Response: ‘foo’ in 1002ms
    [2026-02-18T11:06:31.072Z] Response: ‘foo’ in 998ms
    [2026-02-18T11:06:32.074Z] Result: true

    Agent: Success
    Logs:
    [2026-02-18T11:06:26.109Z] Starting stream
    [2026-02-18T11:06:26.112Z] Pushing first message
    [2026-02-18T11:06:27.172Z] Response: ‘foo’ in 1060ms
    [2026-02-18T11:06:27.676Z] Pushing next message
    [2026-02-18T11:06:28.471Z] Response: ‘foo’ in 1299ms
    [2026-02-18T11:06:28.974Z] Pushing next message
    [2026-02-18T11:06:30.276Z] Response: ‘foo’ in 1805ms
    [2026-02-18T11:06:30.781Z] Pushing next message
    [2026-02-18T11:06:31.674Z] Response: ‘foo’ in 1398ms
    [2026-02-18T11:06:32.178Z] Pushing next message
    [2026-02-18T11:06:32.983Z] Response: ‘foo’ in 1309ms
    [2026-02-18T11:06:32.983Z] Result: true

    Marketplace: Success
    Logs:
    [2026-02-18T11:06:25.935Z] Host: link
    [2026-02-18T11:06:26.504Z] Response in 569ms
    [2026-02-18T11:06:26.504Z] Response: 200
    [2026-02-18T11:06:26.504Z] Response Type: cors
    [2026-02-18T11:06:26.504Z] Server: null
    [2026-02-18T11:06:26.504Z] Result: OK in 569ms

    Authentication: Success
    Logs:
    [2026-02-18T11:06:25.946Z] Host: link
    [2026-02-18T11:06:26.586Z] Response: 200 in 640ms

    Authentication UI: Success
    Logs:
    [2026-02-18T11:06:26.010Z] DNS lookup: authenticator.cursor.sh
    [2026-02-18T11:06:26.164Z] Resolved authenticator.cursor.sh to 8.47.69.6 in 95ms

    Cursor Tab: Success
    Logs:
    [2026-02-18T11:06:26.012Z] DNS lookup: link
    [2026-02-18T11:06:26.137Z] Resolved api3.cursor.sh to 104.18.18.125 in 1ms

    Agent Endpoint: Success
    Logs:
    [2026-02-18T11:06:26.014Z] DNS lookup: agent.api5.cursor.sh
    [2026-02-18T11:06:26.198Z] Resolved agent.api5.cursor.sh to 50.18.248.73 in 129ms

    Codebase Indexing: Success
    Logs:
    [2026-02-18T11:06:26.016Z] DNS lookup: repo42.cursor.sh
    [2026-02-18T11:06:26.237Z] Resolved repo42.cursor.sh to 98.82.255.204 in 182ms

    Downloads: Success
    Logs:
    [2026-02-18T11:06:25.992Z] Host: link
    [2026-02-18T11:06:26.759Z] Response: 403 in 767ms

    CDN: Success
    Logs:
    [2026-02-18T11:06:26.007Z] Host: http://cursor-cdn.com
    [2026-02-18T11:06:26.736Z] Response: 404 in 729ms

There are no connectivity errors in the diagnostics output.

In DevTools, the extensionquery request returns HTTP 200 and a valid JSON response. The response clearly contains extension results (TotalCount > 0) with full metadata and VSIX links.

However, the Marketplace UI still shows 0 extensions and does not render the returned results.

Opening https://marketplace.cursorapi.com/ directly in the browser works without issues.

Based on all of the above, this does not appear to be a network, DNS, VPN, or firewall issue. It seems to be a client-side rendering or filtering problem in the Marketplace UI.

Let me know if you need a HAR export or a full DevTools network capture.

5

Thanks for the info and the diagnostics. This clearly rules out any network issues.

Since the extensionquery request returns valid JSON with results, but the UI still shows 0, it looks like a client-side rendering issue. A few things to try:

  1. Open DevTools (Help > Toggle Developer Tools), go to the Console tab, then search for extensions in the Marketplace. Do you see any errors or warnings in the console at the moment the results should appear? A screenshot of the console output would really help.

  2. Also, going back to my earlier question. In the Network tab, after the main extensionquery request succeeds, are there any other failed requests (red entries)? For example, requests for icons or metadata that return 404 or time out can cause the UI to fail silently.

  3. You can also try clearing the Marketplace cache. Press Ctrl + Shift + P > “Clear Editor History”, then restart Cursor.

Let me know what the console shows. That should help narrow down what is causing the rendering issue.

6

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.