I'm unable to forward a port

Erid · February 12, 2024, 11:44pm

Hi, I just tried to forward a port; and I’m getting the following:

Could it be something on my side?

Thanks!

Jasonk10 · March 24, 2024, 4:24pm

same

kotrfa · May 13, 2024, 10:00am

same

silouanwright · May 14, 2024, 10:52pm

Yes this is broken for me as well, but it works in VSCode

Erid · May 22, 2024, 7:35pm

Still not working for me

Corey3D · June 29, 2024, 11:23pm

The problem is that the exe used for tunneling does not exist for Cursor in
C:\Users\username\AppData\Local\Programs\cursor\bin

I got around this problem by copying the bin folder from VS Code to Cursor.

Be aware tho’, closing the port from Cursor does not stop the process and the forwarding stays active, you have to manually stop code-tunnel.exe eg. from task manager.

eduardomylonas · October 21, 2024, 6:25pm

this worked for me. thank you!

noor-ul-amin-emumba · January 20, 2025, 8:46am

getting same issue

danperks · January 21, 2025, 8:37pm

Hey, currently the code-tunnel functionality, which powers this feature, is not available in Cursor as it is proprietary to VSCode.

I’ve added this to our internal feedback tracker to see if we can ship an alternative method to get this functionality to work in a future release.

silouanwright · March 4, 2025, 11:58pm

Some suggestions in light of that: remove the button, or pop up a message to your sentiments when you press the button, add some docs around it, etc.

Being that this is a VSCode fork, I expect for this to work, so if it doesn’t, not expressing that is somewhat false advertising?

davidq2210 · April 23, 2025, 4:06pm

More than a year, and we have the same issue.. Can’t believe

evsar3 · July 21, 2025, 1:14pm

A very easy fix that is taking years to be addressed.

For the Cursor dev team:

github.com/microsoft/vscode

extensions/tunnel-forwarding/src/extension.ts

fd706d279


      
          * the CLI. This is primarily used since privacy changes to port will appear
          * as a dispose+re-create call, and we don't want to have to restart the CLI.
          */
          const CLEANUP_TIMEOUT = 10_000;
          
          const cliPath = process.env.VSCODE_FORWARDING_IS_DEV
          	? path.join(__dirname, '../../../cli/target/debug/code')
          	: path.join(
          		vscode.env.appRoot,
          		process.platform === 'darwin' ? 'bin' : '../../bin',
          		vscode.env.appQuality === 'stable' ? 'code-tunnel' : 'code-tunnel-insiders',
          	) + (process.platform === 'win32' ? '.exe' : '');
          
          class Tunnel implements vscode.Tunnel {
          	private readonly disposeEmitter = new vscode.EventEmitter<void>();
          	public readonly onDidDispose = this.disposeEmitter.event;
          	public localAddress!: string;
          
          	constructor(
          		public readonly remoteAddress: { port: number; host: string },
          		public readonly privacy: TunnelPrivacyId,

Replace “code” by “cursor” in this line. Done.

zank · August 15, 2025, 10:09am

How after all this time this is not fixed yet

Tobi_Delbruck · November 2, 2025, 6:49am

With the help of cursor agent I got the below tasks.json that you put in your .vscode folder in cursor root of your project; I don’t know why it needs this complex embedded powershelll script but it works. This one forwards port 8765 for foxglove robotics simulation visualization.

Method 1: Using Cursor Tasks (Recommended)

Press Ctrl+Shift+P (or Cmd+Shift+P on Mac)
Type “Tasks: Run Task”
Select “Forward WSL Port 8765 (Foxglove)”
You may need to enter your Windows admin password

Note: The task automatically bypasses PowerShell execution policy.

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "Forward WSL Port 8765 (Foxglove)",
            "type": "process",
            "command": "powershell.exe",
            "args": [
                "-ExecutionPolicy",
                "Bypass",
                "-NoProfile",
                "-Command",
                "Write-Host 'Requesting Administrator privileges...' -ForegroundColor Yellow; $scriptBlock = 'Write-Host \"Setting up WSL port forwarding for Foxglove Bridge (port 8765)...\" -ForegroundColor Cyan; $wslIP = wsl hostname -I | ForEach-Object { $_.Trim() -split \"\\s+\" | Select-Object -First 1 }; Write-Host \"WSL IP Address: $wslIP\" -ForegroundColor Green; netsh interface portproxy delete v4tov4 listenport=8765 listenaddress=0.0.0.0 2>$null; Write-Host \"Cleaned up existing port proxy rules\" -ForegroundColor Yellow; netsh interface portproxy add v4tov4 listenport=8765 listenaddress=0.0.0.0 connectport=8765 connectaddress=$wslIP; Write-Host \"Added port proxy: 0.0.0.0:8765 -> $wslIP:8765\" -ForegroundColor Green; $firewallRule = Get-NetFirewallRule -DisplayName \"WSL Foxglove Bridge 8765\" -ErrorAction SilentlyContinue; if (-not $firewallRule) { New-NetFirewallRule -DisplayName \"WSL Foxglove Bridge 8765\" -Direction Inbound -LocalPort 8765 -Protocol TCP -Action Allow | Out-Null; Write-Host \"Added Windows Firewall rule for port 8765\" -ForegroundColor Green } else { Write-Host \"Windows Firewall rule already exists\" -ForegroundColor Yellow }; Write-Host \"\"; Write-Host \"Port forwarding configured successfully!\" -ForegroundColor Green; Write-Host \"\"; Write-Host \"Connect Foxglove Studio to:\" -ForegroundColor Cyan; Write-Host \"  ws://localhost:8765\" -ForegroundColor White; Write-Host \"  or\" -ForegroundColor Gray; Write-Host \"  ws://$wslIP:8765\" -ForegroundColor White; Write-Host \"\"; Write-Host \"Press any key to close...\"; $null = $Host.UI.RawUI.ReadKey(\"NoEcho,IncludeKeyDown\")'; $encoded = [Convert]::ToBase64String([Text.Encoding]::Unicode.GetBytes($scriptBlock)); Start-Process powershell.exe -ArgumentList \"-ExecutionPolicy Bypass -NoProfile -EncodedCommand $encoded\" -Verb RunAs"
            ],
            "problemMatcher": [],
            "presentation": {
                "reveal": "always",
                "panel": "new",
                "focus": false,
                "echo": true,
                "showReuseMessage": true,
                "clear": false
            },
            "runOptions": {
                "runOn": "default"
            }
        },
        {
            "label": "Check WSL Port Forwarding",
            "type": "shell",
            "command": "powershell.exe",
            "args": [
                "-Command",
                "netsh interface portproxy show all; Write-Host ''; Test-NetConnection -ComputerName localhost -Port 8765 -InformationLevel Quiet"
            ],
            "windows": {
                "options": {
                    "shell": {
                        "executable": "powershell.exe",
                        "args": ["-NoProfile"]
                    }
                }
            },
            "problemMatcher": [],
            "presentation": {
                "reveal": "always",
                "panel": "new",
                "focus": false
            }
        },
        {
            "label": "Remove WSL Port Forwarding",
            "type": "shell",
            "command": "powershell.exe",
            "args": [
                "-Command",
                "netsh interface portproxy delete v4tov4 listenport=8765 listenaddress=0.0.0.0; Write-Host 'Port forwarding removed' -ForegroundColor Green"
            ],
            "windows": {
                "options": {
                    "shell": {
                        "executable": "powershell.exe",
                        "args": ["-NoProfile"]
                    }
                }
            },
            "problemMatcher": [],
            "presentation": {
                "reveal": "always",
                "panel": "new",
                "focus": false
            }
        }
    ]
}

kirillram · November 10, 2025, 10:46am

The quickest fix: rename the bin file to code-tunnel

Shivam_Bhatnagar · November 30, 2025, 5:12pm

same issue. Can’t believe this isn’t fixed. I thought this was a VS code fork!

Christian_Prinz · January 17, 2026, 10:27am

As of now this error still exists and you don’t need VSCode for a workaround. Everything is there:

look at the path the error (disguised as a warning) shows:
<AppData-Local>\Programs\cursor\bin\code-tunnel.exe
It might look a little different based on your system (this is windows11), but that’s the missing target.
So within the same root there is a source file you can use:
<AppData-Local>\Programs\cursor\resources\app\bin\cursor-tunnel.exe
It might also be slightly different based on your system
Just create the bin folder: <AppData-Local>\Programs\cursor\bin
Copy the file over there and rename it from cursor-tunnel.exe to code-tunnel.exe (THATS IMPORTANT!)

This problem should totally be solvable by the Cursor team, but I guess with 2.5K Github Issues at this point, that might not have a high priority - especially when there is a workaround. But it’s annoying to do this over and over again with every update deleting the bin folder. Especially when there are multiple Cursor updates in a week, or sometimes a day.

And also as mentioned before:
You have to kill the code-tunnel.exe from your Task manager manually afterwards

ravirahman · January 20, 2026, 4:35am

Thank you for raising this issue and for the detailed workaround. We have identified the cause for this issue and are fixing it in version 2.4 of Cursor, which should be released later this month.

Topic		Replies	Views
Ports forwarding is not working Bug Reports	3	563	July 11, 2025
Forward localhost:3000 with spawn - Windows Bug Reports	18	9717	December 21, 2025
Port forwarding not working Bug Reports	1	282	July 27, 2025
Cursor port forwarding issue Bug Reports	1	556	July 3, 2025
Cursor port forward useless Bug Reports	3	24	January 22, 2026

I'm unable to forward a port

Method 1: Using Cursor Tasks (Recommended)

Related topics