forcedotcom / forcedotcom/cli

sf org open not opening orgs in browser

Open
#3,646 22 comments 1 reaction 0 assignees View on GitHub
bug investigating validated
Dominant language
No language data
Stars
571
Forks
80
Avg merge
7d 7h
Merged PRs (30d)
3

Description

> **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](https://github.com/trailheadapps/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

```json
{
"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)"
]
}
```

Contributor guide

Open the contributing guide

Research direction

Start by reproducing `sf org open` on Windows with PowerShell or the VSCode terminal, using the reported CLI version and default sandbox org. Compare normal browser launching with `--url-only` and `--browser chrome`, then trace the `sf org open` command's browser-opening entry point. Done means the org opens in the selected browser while the existing URL-only workaround continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.