sf org open not opening orgs in browser

Note
Before you submit your issue, make sure that:

You're using the latest version of Salesforce CLI. - yes, updated today

You've searched both open and closed issues for related posts. - yes, couldn't find anything on sf org open

You've used the doctor command to diagnose common issues. - yes, got pass on everything

You understand that GitHub Issues don't adhere to any agreement or SLA. - yes

If you require immediate assistance, use official channels such as Salesforce Customer Support.

Summary

Running sf org open, get the usual messages but it NEVER opens the org in my browser

Steps To Reproduce

I'm on a Windows machine using VSCode (recently upgraded).
I am on cli version @salesforce/cli/2.150.6 win32-x64 node-v24.19.0
I have my default org set to a sandbox
I type at the Terminal: sf org open
I get the following back in the terminal:
Opening org 00DO500000XXXXXXXX as user lkane@XXXXX.com.lkane
Waiting to resolve the Lightning Experience-enabled custom domain...... done
But the browser window never opens...

There are other developers on my team reporting the same issue (and have been since v2.149 (I upgraded today from v2.148)

I can't provide a repo you can access because we're only allowed to create private ones...

IMPORTANT
Provide a repository that's configured to reproduce the issue. If you are unable to provide a repo, please explain why not. The more info we have from the start, the faster we can resolve your issue.
We may close your issue if you don't include proper instructions.

Generate a project with sf project generate or fork dreamhouse-lwc.

Provide detailed step-by-step instructions on how to reproduce the issue.

Tip

use sf doctor --create-issue to automatically fill the required information

Expected result

It should have opened the org in a browser

Actual result

It didn't do anything - no new browser window opened at all on my machine

Additional information

Work around: using sf org open --url-only and the URL is working to open the org

I also tried sf org open --browser chrome but that didn't do anything either

System Information

in vscode so Terminal but powershell

{
  "architecture": "win32-x64",
  "cliVersion": "@salesforce/cli/2.150.6",
  "nodeVersion": "node-v24.19.0",
  "osVersion": "Windows_NT 10.0.26200",
  "rootPath": "C:\\Users\\lkane\\AppData\\Local\\sf\\client\\2.150.6-c049970",
  "shell": "cmd.exe",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.3.0 (core)",
    "@oclif/plugin-commands 4.2.0 (core)",
    "@oclif/plugin-help 6.3.0 (core)",
    "@oclif/plugin-not-found 3.3.0 (core)",
    "@oclif/plugin-plugins 5.5.1 (core)",
    "@oclif/plugin-search 1.3.0 (core)",
    "@oclif/plugin-update 4.8.0 (core)",
    "@oclif/plugin-version 2.3.0 (core)",
    "@oclif/plugin-warn-if-update-available 3.2.0 (core)",
    "@oclif/plugin-which 3.3.0 (core)",
    "@salesforce/cli 2.150.6 (core)",
    "agent 2.0.5 (core)",
    "apex 4.1.1 (core)",
    "api 2.0.9 (core)",
    "auth 5.0.6 (core)",
    "code-analyzer 5.16.0 (user)",
    "data 5.1.7 (core)",
    "deploy-retrieve 4.1.2 (core)",
    "info 4.0.9 (core)",
    "limits 4.0.4 (core)",
    "marketplace 2.0.5 (core)",
    "org 6.0.11 (core)",
    "packaging 3.0.6 (core)",
    "schema 4.0.6 (core)",
    "settings 3.0.6 (core)",
    "sobject 2.0.5 (core)",
    "telemetry 4.0.6 (core)",
    "templates 57.0.11 (core)",
    "trust 4.0.10 (core)",
    "user 5.0.2 (core)"
  ]
}

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

Root cause: the open dependency was bumped from 10.2.0 → 11.0.1, and v11
added stdio: 'ignore' to the Windows branch.

Env: Windows 11 build 26200, sf 2.150.6 (win32-x64, node 24.19.0), Chrome default.

Where it comes from

plugin-org org/open.js → utils.openUrl() → plain open(url, options)
with no wait. In open@11.0.1 index.js, the win32 branch now does:

if (!options.wait) {
    // PowerShell will keep the parent process alive unless stdio is ignored.
    childProcessOptions.stdio = 'ignore';   // <-- new in v11
}

@CPLynda

Hi @CPLynda , thanks for reporting! I've tried to reproduce on my window setup, but it opened my org in the browser successfully. I think this may be a race condition where the CLI process exits before the browser has time to launch. Could you help me confirm by running sf org open 5-6 times in a row? Thanks!!

Does the browser open some of the time, or never?
Could you also try to run in the terminal outside VS Code?
What does this command do from your terminal- does it open browser? powershell -Command "Start-Process 'https://example.com'"

Here's what I did now:
Ran the command in VS Code about 8 times and got nothing
Ran the command with --target-org lkane in my terminal outside of VS Code about 8 times and on the 9th it finally opened
Returned to VS code and ran once at it opened
Then in VS code tried to go to a different sandbox --target-org pete and tried 10 times and it didn't open
Then did that one in my terminal outside of VS code and it opened at the 2nd time

Tried the 3rd command you sent and it opens from both inside VS Code and Outside it immediately.

This issue has been linked to a new work item: W-24154138

@CPLynda

I'm experiencing the same issue, same steps to reproduce as @CPLynda

@CPLynda

Hi @CPLynda , @rcgomezap , we've published an updated build with the fix. Could you guys please run the commands below?

sf plugins install @salesforce/plugin-org@dev
sf org open

Let me know, how it goes. Thanks!!

@soridalac

@soridalac it is opening orgs consistently though the messaging has updated:

Waiting to resolve the Lightning Experience-enabled custom domain...... done
Warning: Detected unsettled top-level await at file:///C:/Users/lkane/AppData/Local/sf/client/2.150.6-c049970/bin/run.js:15
await cli.run();

@CPLynda

Same output here @CPLynda

@CPLynda

Hi @CPLynda , @rcgomezap , we've published an updated build with the fix. Could you guys please run the commands below?

sf plugins install @salesforce/plugin-org@dev

sf org open

Let me know, how it goes. Thanks!!

Opening org 00xxx as user xxxx
Waiting to resolve the Lightning Experience-enabled custom domain...... done
Warning: Detected unsettled top-level await at file:///C:/Users/username/AppData/Local/sf/client/2.150.6-c049970/bin/run.js:15
await cli.run();
^

Org didn't open also

@CPLynda

Just to clarify :
@CPLynda , it is working consistently opening orgs in the browser?
@rcgomezap, it didn't opening orgs at all? If yes what version shows when you run sf plugins inspect @salesforce/plugin-org ?

The warning is appear on node >=24 with the fix. I will check it and update later! Thanks :)

Just to clarify : @CPLynda , it is working consistently opening orgs in the browser? @rcgomezap, it didn't opening orgs at all? If yes what version shows when you run sf plugins inspect @salesforce/plugin-org ?

The warning is appear on node >=24 with the fix. I will check it and update later! Thanks :)

Correct, I didn't get any org opened. sf plugins inspect @salesforce/plugin-org shows 6.0.14-dev-0

@soridalac

@soridalac
Yesterday evening when I applied the plugin, it was working but this morning, it's working sometimes but I'm having to run the sf org open multiple times again (3-4 currently for most runs)

I get version 6.0.14-dev.0
and still getting the warning message

Also saw other CLI users posting in Ohana Slack code-development channel that they are and have been experiencing this issue for a while as well

@CPLynda

@CPLynda , @rcgomezap , can you run the sf plugins install @salesforce/plugin-org@dev and make sure the version is 6.0.14-dev.1. Let me know, how it goes!

@soridalac

@soridalac
ran install again and confirmed: version 6.0.14-dev.1
sf org open appears to be working though it seems to take a little longer that it did previously
no longer getting warning message

@CPLynda

@CPLynda , is it open org consistently or sometimes?

@soridalac

@soridalac I've done 8 org opens (different target orgs) since the installing the updated plug in and they have all opened without repeated request

@CPLynda

@CPLynda , can you run the commands again and make sure the version is 6.0.14-dev.2? this should fix the open browser and the delay you noticed.

@CPLynda

@CPLynda , @rcgomezap , can you run the sf plugins install @salesforce/plugin-org@dev and make sure the version is 6.0.14-dev.1. Let me know, how it goes!

Tried with dev.2, sf org open works without the previous await warning 👍

@soridalac

@soridalac updated to v2 and it's opening, not sure its much faster but the timing between the messaging and opening seems more realistic
but also have only done 4 opens since installing

@CPLynda

thanks @CPLynda and @rcgomezap for testing!! Currently we are in moratorium (dreamforce). You can still use dev tag or install nightly. When it become available, I will post it here:)

@CPLynda

thanks @CPLynda and @rcgomezap for testing!! Currently we are in moratorium (dreamforce). You can still use dev tag or install nightly. When it become available, I will post it here:)

Thank you for your support! 🫶

If you are on windows and lazy like me, you can mimic the sf org open by using

Start-Process ((sf org open --target-org MyTestOrg1  --url-only --json | ConvertFrom-Json).result.url)

Hey all 👋 this is now available in the latest version of the CLI (as of 2.152.13). Closing this issue

Navigation Menu

Repository navigation

sf org open not opening orgs in browser #3646

Summary

Steps To Reproduce

Expected result

Actual result

Additional information

System Information

Where it comes from

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

sf org open not opening orgs in browser #3646

Description

Summary

Steps To Reproduce

Expected result

Actual result

Additional information

System Information

Activity

github-actions commented on Sep 9, 2026

acantero-dev commented on Sep 9, 2026

Where it comes from

soridalac commented on Sep 9, 2026

CPLynda commented on Sep 10, 2026

git2gus commented on Sep 10, 2026

rcgomezap commented on Sep 10, 2026

soridalac commented on Sep 10, 2026

CPLynda commented on Sep 10, 2026

rcgomezap commented on Sep 10, 2026

rcgomezap commented on Sep 10, 2026

soridalac commented on Sep 10, 2026

rcgomezap commented on Sep 11, 2026

CPLynda commented on Sep 11, 2026

soridalac commented on Sep 11, 2026

CPLynda commented on Sep 11, 2026

soridalac commented on Sep 11, 2026

CPLynda commented on Sep 11, 2026

soridalac commented on Sep 11, 2026

rcgomezap commented on Sep 11, 2026

CPLynda commented on Sep 11, 2026

soridalac commented on Sep 11, 2026

rcgomezap commented on Sep 11, 2026

dalden1981 commented on Sep 17, 2026

iowillhoit commented on Oct 13, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions