Org Picker - sorting org options (by Alias/Username)

[AndrewStopchenko-SO]

Is your feature request related to a problem? Please describe.
Currently, Default Org Picker shows known org options in a somewhat random order. I wasn't able to follow the ordering principle - maybe there is no any sorting at the moment, since fast-clicking the toolbar Default Org picker item sometimes shuffles the rendered options.

This is an example with only 3 orgs authorized in the WSL - it seems the options are sorted neither by alias, nor by username in this case:

When having more orgs registered in the SF CLI, this randomness makes it really hard to locate the needed org quickly without filtering the list by typing the alias/username search text.

Describe the solution you'd like
It would be nice if the org options are sorted alphabetically by their Aliases.

I am not sure if the Org Picker even displays orgs that were authorized but not assigned with an alias (possible via CLI) - but if these orgs also get listed, they can probably use the username as a fallback sorted value.

The sf org list CLI command's output might also be a good reference point for sorting the org options: it looks like CLI output first buckets all orgs into DevHubs/non-DevHubs/Sandboxes/scratchOrgs sub-categories, and then sorts (probably by Alias, then by Username) within each sub-category.

Describe alternatives you've considered
Nothing I could think of, except of using the unsorted orgs list (as it is now).

Salesforce Extension Pack: v64.5.1
SF CLI version: @salesforce/cli/2.98.6 wsl-x64 node-v20.18.3
VSCode Version: 1.103.0-insider (user setup)
OS: Windows_NT x64 10.0.19045

SF CLI details:

{
  "architecture": "wsl-x64",
  "cliVersion": "@salesforce/cli/2.98.6",
  "nodeVersion": "node-v20.18.3",
  "osVersion": "Linux 6.6.87.2-microsoft-standard-WSL2",
  "rootPath": "/root/.nvm/versions/node/v20.18.3/lib/node_modules/@salesforce/cli",
  "shell": "bash",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 3.2.33 (core)",
    "@oclif/plugin-commands 4.1.29 (core)",
    "@oclif/plugin-help 6.2.31 (core)",
    "@oclif/plugin-not-found 3.2.60 (core)",
    "@oclif/plugin-plugins 5.4.45 (core)",
    "@oclif/plugin-search 1.2.27 (core)",
    "@oclif/plugin-update 4.7.1 (core)",
    "@oclif/plugin-version 2.2.31 (core)",
    "@oclif/plugin-warn-if-update-available 3.1.44 (core)",
    "@oclif/plugin-which 3.2.39 (core)",
    "@salesforce/cli 2.98.6 (core)",
    "agent 1.23.3 (core)",
    "apex 3.6.19 (core)",
    "api 1.3.3 (core)",
    "auth 3.7.9 (core)",
    "data 4.0.46 (core)",
    "deploy-retrieve 3.22.33 (core)",
    "info 3.4.73 (core)",
    "limits 3.3.60 (core)",
    "marketplace 1.3.8 (core)",
    "org 5.9.9 (core)",
    "packaging 2.18.0 (core)",
    "schema 3.3.73 (core)",
    "settings 2.4.36 (core)",
    "sobject 1.4.65 (core)",
    "telemetry 3.6.48 (core)",
    "templates 56.3.54 (core)",
    "trust 3.7.109 (core)",
    "user 3.6.29 (core)",
    "@salesforce/sfdx-scanner 4.12.0 (user) published 91 days ago (Tue Apr 29 2025)"
  ]
}

[svc-idee-bot]

Thank you for filing this feature request. We appreciate your feedback and will review the feature at our next grooming session. We prioritize feature requests with more upvotes and comments.

[git2gus[bot]]

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

[AndrewStopchenko-SO]

Looks like this was already requested in the #6074 Discussion... I believe I checked across the Issues, but didn't review discussions on this topic.

At the same time, the #6074 Discussion doesn't seem to have the work item linked.
Please advise if these two items can be "merged" somehow, or linked, or should I close the current one?

[mshanemc]

they are now grouped by org type (scratch, sandbox, devhubs, etc)
then, ordered by alias (if there is one) then non-alias by username