{"id":33609376,"url":"https://github.com/salesforcecli/plugin-org","last_synced_at":"2026-05-31T11:01:02.156Z","repository":{"id":37980347,"uuid":"328679953","full_name":"salesforcecli/plugin-org","owner":"salesforcecli","description":"Commands to interact with Salesforce orgs","archived":false,"fork":false,"pushed_at":"2026-05-31T07:05:13.000Z","size":10896,"stargazers_count":25,"open_issues_count":5,"forks_count":21,"subscribers_count":7,"default_branch":"main","last_synced_at":"2026-05-31T09:08:20.145Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"TypeScript","has_issues":false,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/salesforcecli.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":"CODE_OF_CONDUCT.md","threat_model":null,"audit":null,"citation":null,"codeowners":"CODEOWNERS","security":"SECURITY.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":"AGENTS.md","dco":null,"cla":null}},"created_at":"2021-01-11T13:54:17.000Z","updated_at":"2026-05-31T07:02:34.000Z","dependencies_parsed_at":"2026-04-02T11:01:28.890Z","dependency_job_id":null,"html_url":"https://github.com/salesforcecli/plugin-org","commit_stats":{"total_commits":870,"total_committers":24,"mean_commits":36.25,"dds":0.6643678160919539,"last_synced_commit":"4fdbc7a528dbe719399dec1174c019677ec3a588"},"previous_names":[],"tags_count":507,"template":false,"template_full_name":"salesforcecli/plugin-template","purl":"pkg:github/salesforcecli/plugin-org","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-org","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-org/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-org/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-org/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/salesforcecli","download_url":"https://codeload.github.com/salesforcecli/plugin-org/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/salesforcecli%2Fplugin-org/sbom","scorecard":{"id":440541,"data":{"date":"2025-08-11","repo":{"name":"github.com/salesforcecli/plugin-org","commit":"7a45b3b97a8a8caf9202e675ebc17fff82b217b5"},"scorecard":{"version":"v5.2.1-40-gf6ed084d","commit":"f6ed084d17c9236477efd66e5b258b9d4cc7b389"},"score":5.2,"checks":[{"name":"Code-Review","score":1,"reason":"Found 1/6 approved changesets -- score normalized to 1","details":null,"documentation":{"short":"Determines if the project requires human code review before pull requests (aka merge requests) are merged.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#code-review"}},{"name":"Security-Policy","score":9,"reason":"security policy file detected","details":["Info: security policy file detected: SECURITY.md:1","Info: Found linked content: SECURITY.md:1","Warn: One or no descriptive hints of disclosure, vulnerability, and/or timelines in security policy","Info: Found text in security policy: SECURITY.md:1"],"documentation":{"short":"Determines if the project has published a security policy.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#security-policy"}},{"name":"Maintained","score":10,"reason":"30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10","details":null,"documentation":{"short":"Determines if the project is \"actively maintained\".","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#maintained"}},{"name":"Binary-Artifacts","score":10,"reason":"no binaries found in the repo","details":null,"documentation":{"short":"Determines if the project has generated executable (binary) artifacts in the source repository.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#binary-artifacts"}},{"name":"Packaging","score":-1,"reason":"packaging workflow not detected","details":["Warn: no GitHub/GitLab publishing workflow detected."],"documentation":{"short":"Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#packaging"}},{"name":"Dangerous-Workflow","score":10,"reason":"no dangerous workflow patterns detected","details":null,"documentation":{"short":"Determines if the project's GitHub Action workflows avoid dangerous patterns.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#dangerous-workflow"}},{"name":"CII-Best-Practices","score":0,"reason":"no effort to earn an OpenSSF best practices badge detected","details":null,"documentation":{"short":"Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#cii-best-practices"}},{"name":"Pinned-Dependencies","score":0,"reason":"dependency not pinned by hash detected -- score normalized to 0","details":["Warn: third-party GitHubAction not pinned by hash: .github/workflows/automerge.yml:9: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/automerge.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/create-github-release.yml:18: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/create-github-release.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/devScripts.yml:9: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/devScripts.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/failureNotifications.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/failureNotifications.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/notify-slack-on-pr-open.yml:23: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/notify-slack-on-pr-open.yml/main?enable=pin","Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/onRelease.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/onRelease.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/onRelease.yml:22: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/onRelease.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/onRelease.yml:25: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/onRelease.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/sandboxNuts.yml:7: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/sandboxNuts.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:9: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/test.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:13: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/test.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/test.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/test.yml:19: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/test.yml/main?enable=pin","Warn: third-party GitHubAction not pinned by hash: .github/workflows/validate-pr.yml:11: update your workflow using https://app.stepsecurity.io/secureworkflow/salesforcecli/plugin-org/validate-pr.yml/main?enable=pin","Info: 0 out of 1 GitHub-owned GitHubAction dependencies pinned","Info: 0 out of 13 third-party GitHubAction dependencies pinned"],"documentation":{"short":"Determines if the project has declared and pinned the dependencies of its build process.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#pinned-dependencies"}},{"name":"Token-Permissions","score":0,"reason":"detected GitHub workflow tokens with excessive permissions","details":["Warn: no topLevel permission defined: .github/workflows/automerge.yml:1","Warn: no topLevel permission defined: .github/workflows/create-github-release.yml:1","Warn: no topLevel permission defined: .github/workflows/devScripts.yml:1","Warn: no topLevel permission defined: .github/workflows/failureNotifications.yml:1","Warn: no topLevel permission defined: .github/workflows/notify-slack-on-pr-open.yml:1","Warn: no topLevel permission defined: .github/workflows/onRelease.yml:1","Warn: no topLevel permission defined: .github/workflows/sandboxNuts.yml:1","Warn: no topLevel permission defined: .github/workflows/test.yml:1","Warn: no topLevel permission defined: .github/workflows/validate-pr.yml:1","Info: no jobLevel write permissions found"],"documentation":{"short":"Determines if the project's workflows follow the principle of least privilege.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#token-permissions"}},{"name":"License","score":10,"reason":"license file detected","details":["Info: project has a license file: LICENSE.txt:0","Info: FSF or OSI recognized license: Apache License 2.0: LICENSE.txt:0"],"documentation":{"short":"Determines if the project has defined a license.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#license"}},{"name":"Fuzzing","score":0,"reason":"project is not fuzzed","details":["Warn: no fuzzer integrations found"],"documentation":{"short":"Determines if the project uses fuzzing.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#fuzzing"}},{"name":"Signed-Releases","score":-1,"reason":"no releases found","details":null,"documentation":{"short":"Determines if the project cryptographically signs release artifacts.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#signed-releases"}},{"name":"Branch-Protection","score":-1,"reason":"internal error: error during branchesHandler.setup: internal error: githubv4.Query: Resource not accessible by integration","details":null,"documentation":{"short":"Determines if the default and release branches are protected with GitHub's branch protection settings.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#branch-protection"}},{"name":"SAST","score":0,"reason":"SAST tool is not run on all commits -- score normalized to 0","details":["Warn: 0 commits out of 25 are checked with a SAST tool"],"documentation":{"short":"Determines if the project uses static code analysis.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#sast"}},{"name":"Vulnerabilities","score":7,"reason":"3 existing vulnerabilities detected","details":["Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8","Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw","Warn: Project is vulnerable to: GHSA-9wv6-86v2-598j"],"documentation":{"short":"Determines if the project has open, known unfixed vulnerabilities.","url":"https://github.com/ossf/scorecard/blob/f6ed084d17c9236477efd66e5b258b9d4cc7b389/docs/checks.md#vulnerabilities"}}]},"last_synced_at":"2025-08-19T05:29:38.465Z","repository_id":37980347,"created_at":"2025-08-19T05:29:38.465Z","updated_at":"2025-08-19T05:29:38.465Z"},"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":33728391,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-05-26T15:22:16.424Z","status":"online","status_checked_at":"2026-05-31T02:00:06.040Z","response_time":95,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-11-30T19:02:45.393Z","updated_at":"2026-05-31T11:01:02.148Z","avatar_url":"https://github.com/salesforcecli.png","language":"TypeScript","funding_links":[],"categories":[],"sub_categories":[],"readme":"# plugin-org\n\n[![NPM](https://img.shields.io/npm/v/@salesforce/plugin-org.svg?label=@salesforce/plugin-org)](https://www.npmjs.com/package/@salesforce/plugin-org) [![Downloads/week](https://img.shields.io/npm/dw/@salesforce/plugin-org.svg)](https://npmjs.org/package/@salesforce/plugin-org) [![License](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](https://opensource.org/license/apache-2-0)\n\nCommands for working with Salesforce orgs. As the Salesforce CLI is transitioning commands owned by various teams to\nopen source, it may not represent all of the `org` commands.\n\n## About Salesforce CLI plugins\n\nSalesforce CLI plugins are based on the [oclif plugin framework](https://oclif.io/docs/introduction). Read\nthe [plugin developer guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_cli_plugins.meta/sfdx_cli_plugins/cli_plugins_architecture_sf_cli.htm)\nto learn about Salesforce CLI plugin development.\n\nThis repository contains a lot of additional scripts and tools to help with general Salesforce node development and\nenforce coding standards. You should familiarize yourself with some of\nthe [node developer packages](https://github.com/forcedotcom/sfdx-dev-packages/) used by Salesforce. There is also a\ndefault circleci config using the [release management orb](https://github.com/forcedotcom/npm-release-management-orb)\nstandards.\n\nAdditionally, there are some additional tests that the Salesforce CLI will enforce if this plugin is ever bundled with\nthe CLI. These test are included by default under the `posttest` script and it is recommended to keep these tests active\nin your plugin, regardless if you plan to have it bundled.\n\nThis plugin is bundled with the [Salesforce CLI](https://developer.salesforce.com/tools/sfdxcli). For more information\non the CLI, read\nthe [getting started guide](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm).\n\nWe always recommend using the latest version of these commands bundled with the CLI, however, you can install a specific\nversion or tag if needed.\n\n## Install\n\n```bash\nsf plugins:install @salesforce/plugin-org\n```\n\n## Issues\n\nPlease report any issues at \u003chttps://github.com/forcedotcom/cli/issues\u003e\n\n## Contributing\n\n1. Please read our [Code of Conduct](CODE_OF_CONDUCT.md)\n2. Create a new issue before starting your project so that we can keep track of\n what you are trying to add/fix. That way, we can also offer suggestions or\n let you know if there is already an effort in progress.\n3. Fork this repository.\n4. [Build the plugin locally](#build)\n5. Create a _topic_ branch in your fork. Note, this step is recommended but technically not required if contributing\n using a fork.\n6. Edit the code in your fork.\n7. Write appropriate tests for your changes. Try to achieve at least 95% code coverage on any new code. No pull request\n will be accepted without unit tests.\n8. Sign CLA (see [CLA](#cla) below).\n9. Send us a pull request when you are done. We'll review your code, suggest any needed changes, and merge it in.\n\n### CLA\n\nExternal contributors will be required to sign a Contributor's License\nAgreement. You can do so by going to \u003chttps://cla.salesforce.com/sign-cla\u003e.\n\n### Build\n\nTo build the plugin locally, make sure to have yarn installed and run the following commands:\n\n```bash\n# Clone the repository\ngit clone git@github.com:salesforcecli/plugin-org\n\n# Install the dependencies and compile\nyarn install\nyarn build\n```\n\nTo use your plugin, run using the local `./bin/dev` or `./bin/dev.cmd` file.\n\n```bash\n# Run using local run file.\n./bin/dev.js org list\n```\n\nThere should be no differences when running via the Salesforce CLI or using the local run file. However, it can be\nuseful to link the plugin to do some additional testing or run your commands from anywhere on your machine.\n\n```bash\n# Link your plugin to the sf cli\nsf plugins:link .\n# To verify\nsf plugins\n```\n\n### Sandbox NUTs\n\nSandboxes are pretty slow, and there's a constraint to how many we can have. So if your changes might impact sandboxes,\nand you want to check those in the real world, run\nthe [SandboxNuts](https://github.com/salesforcecli/plugin-org/actions/workflows/sandboxNuts.yml) Github Action.\n\n## Commands\n\n\u003c!-- commands --\u003e\n\n- [`sf org auth show-access-token`](#sf-org-auth-show-access-token)\n- [`sf org auth show-sfdx-auth-url`](#sf-org-auth-show-sfdx-auth-url)\n- [`sf org auth show-user-password`](#sf-org-auth-show-user-password)\n- [`sf org create agent-user`](#sf-org-create-agent-user)\n- [`sf org create sandbox`](#sf-org-create-sandbox)\n- [`sf org create scratch`](#sf-org-create-scratch)\n- [`sf org delete sandbox`](#sf-org-delete-sandbox)\n- [`sf org delete scratch`](#sf-org-delete-scratch)\n- [`sf org disable tracking`](#sf-org-disable-tracking)\n- [`sf org display`](#sf-org-display)\n- [`sf org enable tracking`](#sf-org-enable-tracking)\n- [`sf org list`](#sf-org-list)\n- [`sf org list metadata`](#sf-org-list-metadata)\n- [`sf org list metadata-types`](#sf-org-list-metadata-types)\n- [`sf org open`](#sf-org-open)\n- [`sf org open agent`](#sf-org-open-agent)\n- [`sf org open authoring-bundle`](#sf-org-open-authoring-bundle)\n- [`sf org refresh sandbox`](#sf-org-refresh-sandbox)\n- [`sf org resume sandbox`](#sf-org-resume-sandbox)\n- [`sf org resume scratch`](#sf-org-resume-scratch)\n\n## `sf org auth show-access-token`\n\nShow the current access token for an org.\n\n```\nUSAGE\n $ sf org auth show-access-token -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [-p]\n\nFLAGS\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n -p, --no-prompt Skip the security warning and reveal the access token without confirmation.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Show the current access token for an org.\n\n Because access tokens are sensitive credentials that grant full access to an org, this command prompts for\n confirmation before revealing the token. Skip confirmation by specifying either the --no-prompt or --json flag.\n\nEXAMPLES\n Show the access token for the default org:\n\n $ sf org auth show-access-token\n\n Show the access token for an org with alias \"my-org\":\n\n $ sf org auth show-access-token --target-org my-org\n\n Show the access token without the confirmation prompt:\n\n $ sf org auth show-access-token --target-org my-org --no-prompt\n\n Get the access token as JSON for use in scripts:\n\n $ sf org auth show-access-token --target-org my-org --json\n```\n\n_See code: [src/commands/org/auth/show-access-token.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/auth/show-access-token.ts)_\n\n## `sf org auth show-sfdx-auth-url`\n\nShow the SFDX Auth URL for an org.\n\n```\nUSAGE\n $ sf org auth show-sfdx-auth-url -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [-p]\n\nFLAGS\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n -p, --no-prompt Skip the security warning and reveal the SFDX Auth URL without confirmation.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Show the SFDX Auth URL for an org.\n\n Shows the SFDX Auth URL for an org. This URL is only available for orgs authenticated via a web-based OAuth flow. This\n command prompts for confirmation before revealing it. Skip confirmation by specifying either the --no-prompt or --json\n flag.\n\nEXAMPLES\n Show the SFDX Auth URL for the default org:\n\n $ sf org auth show-sfdx-auth-url\n\n Show the SFDX Auth URL for an org with alias \"my-org\":\n\n $ sf org auth show-sfdx-auth-url --target-org my-org\n\n Show the SFDX Auth URL without the confirmation prompt:\n\n $ sf org auth show-sfdx-auth-url --target-org my-org --no-prompt\n\n Get the SFDX Auth URL as JSON for use in scripts:\n\n $ sf org auth show-sfdx-auth-url --target-org my-org --json\n```\n\n_See code: [src/commands/org/auth/show-sfdx-auth-url.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/auth/show-sfdx-auth-url.ts)_\n\n## `sf org auth show-user-password`\n\nShow the stored password for an org's user.\n\n```\nUSAGE\n $ sf org auth show-user-password -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [-p]\n\nFLAGS\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n -p, --no-prompt Skip the security warning and reveal the password without confirmation.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Show the stored password for an org's user.\n\n This command shows only passwords that were generated locally in your DX project with either the \"org generate\n password\" or \"org create user\" CLI command. If you generated a password for a user in Setup in your org, you can't\n show it with this command.\n\n Because passwords are sensitive credentials, this command prompts for confirmation before revealing it. Skip\n confirmation by specifying either the --no-prompt or --json flag.\n\nEXAMPLES\n Show the password for the default org's user:\n\n $ sf org auth show-user-password\n\n Show the password for an org with alias \"my-org\":\n\n $ sf org auth show-user-password --target-org my-org\n\n Show the password without the confirmation prompt:\n\n $ sf org auth show-user-password --target-org my-org --no-prompt\n\n Get the password as JSON for use in scripts:\n\n $ sf org auth show-user-password --target-org my-org --json\n```\n\n_See code: [src/commands/org/auth/show-user-password.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/auth/show-user-password.ts)_\n\n## `sf org create agent-user`\n\nCreate the default Salesforce user that is used to run an agent.\n\n```\nUSAGE\n $ sf org create agent-user -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [--base-username \u003cvalue\u003e]\n [--first-name \u003cvalue\u003e] [--last-name \u003cvalue\u003e]\n\nFLAGS\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n --api-version=\u003cvalue\u003e Override the api version used for api requests made by this command\n --base-username=\u003cvalue\u003e Base username pattern. A unique ID is appended to ensure global uniqueness of the\n usename.\n --first-name=\u003cvalue\u003e [default: Agent] First name for the agent user.\n --last-name=\u003cvalue\u003e [default: User] Last name for the agent user.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Create the default Salesforce user that is used to run an agent.\n\n You specify this user in the agent's Agent Script file using the \"default_agent_user\" parameter in the \"config\" block.\n\n By default, this command:\n\n - Generates a user called \"Agent User\" with a globally unique username. Use flags to change these default names.\n - Sets the user's email to the new username.\n - Assigns the user the \"Einstein Agent User\" profile.\n - Assigns the user these required permission sets: AgentforceServiceAgentBase, AgentforceServiceAgentUser,\n EinsteinGPTPromptTemplateUser\n - Checks that the user licenses required by the profile and permission sets are available in your org.\n\n The generated user doesn't have a password. You can’t log into Salesforce using the agent user's username. Only\n Salesforce users with admin permissions can view or edit an agent user in Setup.\n\n To assign additional permission sets or licenses after the user was created, use the \"org assign permset\" or \"org\n assign\n permsetlicense\" commands.\n\n When the command completes, it displays a summary of what it did, including the new agent user's username and ID, the\n available licenses associated with the Einstein Agent User profile, and the profile and permission sets assigned to\n the\n agent user.\n\nEXAMPLES\n Create an agent user with an auto-generated username; create the user in the org with alias \"myorg\":\n\n $ sf org create agent-user --target-org myorg\n\n Create an agent user by specifying a base username pattern; to make the username unique, the command appends a unique\n identifier:\n $ sf org create agent-user --base-username service-agent@corp.com --target-org myorg\n\n Create an agent user with an auto-generated username but the custom name \"Service Agent\"; create the user in your\n default org:\n $ sf org create agent-user --first-name Service --last-name Agent\n\nFLAG DESCRIPTIONS\n --base-username=\u003cvalue\u003e Base username pattern. A unique ID is appended to ensure global uniqueness of the usename.\n\n Specify a base username in email format, such as \"service-agent@corp.com\". The command then appends a 12-character\n globally unique ID (GUID) to the name before the \"@\" sign, which ensures that the username is globally unique across\n all\n Salesforce orgs and sandboxes.\n\n For example, if you specify \"service-agent@corp.com\", then the username might be\n \"service-agent.a1b2c3d4e5f6@corp.com\".\n\n If not specified, the command auto-generates the username using this pattern:\n \"agent.user.\u003cGUID\u003e@your-org-domain.com\".\n```\n\n_See code: [src/commands/org/create/agent-user.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/create/agent-user.ts)_\n\n## `sf org create sandbox`\n\nCreate a sandbox org.\n\n```\nUSAGE\n $ sf org create sandbox -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [-f \u003cvalue\u003e] [-s] [-a \u003cvalue\u003e] [-w \u003cminutes\u003e |\n --async] [-i \u003cseconds\u003e | ] [-n \u003cvalue\u003e] [--source-sandbox-name \u003cvalue\u003e | -l Developer|Developer_Pro|Partial|Full |\n --source-id \u003cvalue\u003e] [--no-prompt] [--no-track-source]\n\nFLAGS\n -a, --alias=\u003cvalue\u003e Alias for the sandbox org.\n -f, --definition-file=\u003cvalue\u003e Path to a sandbox definition file.\n -i, --poll-interval=\u003cseconds\u003e Number of seconds to wait between retries.\n -l, --license-type=\u003coption\u003e Type of sandbox license.\n \u003coptions: Developer|Developer_Pro|Partial|Full\u003e\n -n, --name=\u003cvalue\u003e Name of the sandbox org.\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the production org that contains the sandbox\n license.\n -s, --set-default Set the sandbox org as your default org.\n -w, --wait=\u003cminutes\u003e Number of minutes to wait for the sandbox org to be ready.\n --async Request the sandbox creation, but don't wait for it to complete.\n --no-prompt Don't prompt for confirmation about the sandbox configuration.\n --no-track-source Do not use source tracking for this sandbox.\n --source-id=\u003cvalue\u003e ID of the sandbox org to clone.\n --source-sandbox-name=\u003cvalue\u003e Name of the sandbox org to clone.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Create a sandbox org.\n\n There are two ways to create a sandbox org: specify a definition file that contains the sandbox options or use the\n --name and --license-type flags to specify the two required options. If you want to set an option other than name or\n license type, such as apexClassId, you must use a definition file.\n\n You can also use this command to clone an existing sandbox. Use the --source-sandbox-name flag to specify the existing\n sandbox name and the --name flag to the name of the new sandbox.\n\nALIASES\n $ sf env create sandbox\n\nEXAMPLES\n Create a sandbox org using a definition file and give it the alias \"MyDevSandbox\". The production org that contains\n the sandbox license has the alias \"prodOrg\".\n\n $ sf org create sandbox --definition-file config/dev-sandbox-def.json --alias MyDevSandbox --target-org prodOrg\n\n Create a sandbox org by directly specifying its name and type of license (Developer) instead of using a definition\n file. Set the sandbox org as your default.\n\n $ sf org create sandbox --name mysandbox --license-type Developer --alias MyDevSandbox --target-org prodOrg \\\n --set-default\n\n Clone the existing sandbox with name \"ExistingSandbox\" and name the new sandbox \"NewClonedSandbox\". Set the new\n sandbox as your default org. Wait for 30 minutes for the sandbox creation to complete.\n\n $ sf org create sandbox --source-sandbox-name ExistingSandbox --name NewClonedSandbox --target-org prodOrg \\\n --alias MyDevSandbox --set-default --wait 30\n\n Clone the existing sandbox with ID \"0GQB0000000TVobOAG\" and do not wait.\n\n $ sf org create sandbox --source-id 0GQB0000000TVobOAG --name SbxClone --target-org prodOrg --async\n\nFLAG DESCRIPTIONS\n -a, --alias=\u003cvalue\u003e Alias for the sandbox org.\n\n When you create a sandbox, the generated usernames are based on the usernames present in the production org. To\n ensure uniqueness, the new usernames are appended with the name of the sandbox. For example, the username\n \"user@example.com\" in the production org results in the username \"user@example.com.mysandbox\" in a sandbox named\n \"mysandbox\". When you set an alias for a sandbox org, it's assigned to the resulting username of the user running\n this command.\n\n -f, --definition-file=\u003cvalue\u003e Path to a sandbox definition file.\n\n The sandbox definition file is a blueprint for the sandbox. You can create different definition files for each\n sandbox type that you use in the development process. See\n \u003chttps://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_sandbox_definition.htm\u003e for all\n the options you can specify in the definition file.\n\n -n, --name=\u003cvalue\u003e Name of the sandbox org.\n\n The name must be a unique alphanumeric string (10 or fewer characters) to identify the sandbox. You can’t reuse a\n name while a sandbox is in the process of being deleted.\n\n -o, --target-org=\u003cvalue\u003e Username or alias of the production org that contains the sandbox license.\n\n When it creates the sandbox org, Salesforce copies the metadata, and optionally data, from your production org to\n the new sandbox org.\n\n -w, --wait=\u003cminutes\u003e Number of minutes to wait for the sandbox org to be ready.\n\n If the command continues to run after the wait period, the CLI returns control of the terminal to you and displays\n the \"sf org resume sandbox\" command you run to check the status of the create. The displayed command includes the\n job ID for the running sandbox creation.\n\n --async Request the sandbox creation, but don't wait for it to complete.\n\n The command immediately displays the job ID and returns control of the terminal to you. This way, you can continue\n to use the CLI. To check the status of the sandbox creation, run \"sf org resume sandbox\".\n\n --no-track-source Do not use source tracking for this sandbox.\n\n We recommend you enable source tracking in Developer and Developer Pro sandbox, which is why it's the default\n behavior. Source tracking allows you to track the changes you make to your metadata, both in your local project and\n in the sandbox, and to detect any conflicts between the two.\n\n To disable source tracking in the new sandbox, specify the --no-track-source flag. The main reason to disable source\n tracking is for performance. For example, while you probably want to deploy metadata and run Apex tests in your\n CI/CD jobs, you probably don't want to incur the costs of source tracking (checking for conflicts, polling the\n SourceMember object, various file system operations.) This is a good use case for disabling source tracking in the\n sandbox.\n\n --source-id=\u003cvalue\u003e ID of the sandbox org to clone.\n\n The value of --source-id must be an existing sandbox (SandboxInfo.Id). The existing sandbox, and the new sandbox\n specified with the --name flag, must both be associated with the production org (--target-org) that contains the\n sandbox licenses.\n\n You can specify either --source-sandbox-name or --source-id when cloning an existing sandbox, but not both.\n\n --source-sandbox-name=\u003cvalue\u003e Name of the sandbox org to clone.\n\n The value of --source-sandbox-name must be an existing sandbox. The existing sandbox, and the new sandbox specified\n with the --name flag, must both be associated with the production org (--target-org) that contains the sandbox\n licenses.\n\n You can specify either --source-sandbox-name or --source-id when cloning an existing sandbox, but not both.\n```\n\n_See code: [src/commands/org/create/sandbox.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/create/sandbox.ts)_\n\n## `sf org create scratch`\n\nCreate a scratch org.\n\n```\nUSAGE\n $ sf org create scratch -v \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [-a \u003cvalue\u003e] [--async] [-d] [-f \u003cvalue\u003e] [-c] [-e\n developer|enterprise|group|professional|partner-developer|partner-enterprise|partner-group|partner-professional | -s\n \u003cvalue\u003e | --source-org \u003cvalue\u003e] [-m] [-y \u003cdays\u003e] [-w \u003cminutes\u003e] [--api-version \u003cvalue\u003e] [-i \u003cvalue\u003e] [-t]\n [--username \u003cvalue\u003e] [--description \u003cvalue\u003e] [--name \u003cvalue\u003e] [--release preview|previous] [--admin-email \u003cvalue\u003e]\n\nFLAGS\n -a, --alias=\u003cvalue\u003e Alias for the scratch org.\n -d, --set-default Set the scratch org as your default org\n -f, --definition-file=\u003cvalue\u003e Path to a scratch org definition file.\n -i, --client-id=\u003cvalue\u003e Consumer key of the Dev Hub connected app.\n -t, --[no-]track-source Use source tracking for this scratch org. Set --no-track-source to disable source\n tracking.\n -v, --target-dev-hub=\u003cvalue\u003e (required) Username or alias of the Dev Hub org.\n -w, --wait=\u003cminutes\u003e Number of minutes to wait for the scratch org to be ready.\n -y, --duration-days=\u003cdays\u003e Number of days before the org expires.\n --api-version=\u003cvalue\u003e Override the api version used for api requests made by this command\n --async Request the org, but don't wait for it to complete.\n\nPACKAGING FLAGS\n -c, --no-ancestors Don't include second-generation managed package (2GP) ancestors in the scratch org.\n -m, --no-namespace Create the scratch org with no namespace, even if the Dev Hub has a namespace.\n\nDEFINITION FILE OVERRIDE FLAGS\n -e, --edition=\u003coption\u003e Salesforce edition of the scratch org. Overrides the value of the \"edition\" option in the\n definition file, if set.\n \u003coptions: developer|enterprise|group|professional|partner-developer|partner-enterprise|part\n ner-group|partner-professional\u003e\n -s, --snapshot=\u003cvalue\u003e Name of the snapshot to use when creating this scratch org. Overrides the value of the\n \"snapshot\" option in the defintion file, if set.\n --admin-email=\u003cvalue\u003e Email address that will be applied to the org's admin user. Overrides the value of the\n \"adminEmail\" option in the definition file, if set.\n --description=\u003cvalue\u003e Description of the scratch org in the Dev Hub. Overrides the value of the \"description\"\n option in the definition file, if set.\n --name=\u003cvalue\u003e Name of the org, such as \"Acme Company\". Overrides the value of the \"orgName\" option in the\n definition file, if set.\n --release=\u003coption\u003e Release of the scratch org as compared to the Dev Hub release.\n \u003coptions: preview|previous\u003e\n --source-org=\u003cvalue\u003e 15-character ID of the org shape that the new scratch org is based on. Overrides the value\n of the \"sourceOrg\" option in the definition file, if set.\n --username=\u003cvalue\u003e Username of the scratch org admin user. Overrides the value of the \"username\" option in the\n definition file, if set.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Create a scratch org.\n\n There are four ways to create a scratch org:\n\n * Specify a definition file that contains the scratch org options.\n * Use the --edition flag to specify the one required option; this method doesn't require a defintion file.\n * Use the --snapshot flag to create a scratch org from a snapshot. Snapshots are a point-in-time copy of a scratch\n org; you create a snapshot with the \"sf org create snapshot\" command.\n * Use the --source-org flag to create a scratch org from an org shape. Org shapes mimic the baseline setup of a source\n org without the extraneous data and metadata; you create an org shape with the \"sf org create shape\" command.\n\n The --edition, --snapshot, and --source-org flags are mutually exclusive, which means if you specify one, you can't\n also specify the others.\n\n For any of the methods, you can also use these flags; if you use them with --definition-file, they override their\n equivalent option in the scratch org definition file:\n\n * --description\n * --name (equivalent to the \"orgName\" option)\n * --username\n * --release\n * --admin-email (equivalent to the \"adminEmail\" option)\n\n If you want to set options such as org features or settings, you must use a definition file.\n\n You must specify a Dev Hub to create a scratch org, either with the --target-dev-hub flag or by setting your default\n Dev Hub with the target-dev-hub configuration variable.\n\nALIASES\n $ sf env create scratch\n\nEXAMPLES\n Create a Developer edition scratch org using your default Dev Hub and give the scratch org an alias:\n\n $ sf org create scratch --edition developer --alias my-scratch-org\n\n Create a scratch org with a definition file. Specify the Dev Hub using its alias, set the scratch org as your\n default, and specify that it expires in 3 days:\n\n $ sf org create scratch --target-dev-hub MyHub --definition-file config/project-scratch-def.json --set-default \\\n --duration-days 3\n\n Create a preview Enterprise edition scratch org; for use only during Salesforce release transition periods:\n\n $ sf org create scratch --edition enterprise --alias my-scratch-org --target-dev-hub MyHub --release preview\n\n Create a scratch org from a snapshot called \"NightlyBranch\"; be sure you specify the same Dev Hub org associated\n with the snapshot. We recommend you increase the --wait time because creating a scratch org from a snapshot can take\n a while:\n\n $ sf org create scratch --alias my-scratch-org --target-dev-hub MyHub --snapshot NightlyBranch --wait 10\n\nFLAG DESCRIPTIONS\n -a, --alias=\u003cvalue\u003e Alias for the scratch org.\n\n New scratch orgs include one administrator by default. The admin user's username is auto-generated and looks\n something like test-wvkpnfm5z113@example.com. When you set an alias for a new scratch org, it's assigned this\n username.\n\n -e, --edition=developer|enterprise|group|professional|partner-developer|partner-enterprise|partner-group|partner-professional\n\n Salesforce edition of the scratch org. Overrides the value of the \"edition\" option in the definition file, if set.\n\n The editions that begin with \"partner-\" are available only if the Dev Hub org is a Partner Business Org.\n\n -f, --definition-file=\u003cvalue\u003e Path to a scratch org definition file.\n\n The scratch org definition file is a blueprint for the scratch org. It mimics the shape of an org that you use in\n the development life cycle, such as acceptance testing, packaging, or production. See\n \u003chttps://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_scratch_orgs_def_file.htm\u003e for\n all the option you can specify in the definition file.\n\n -s, --snapshot=\u003cvalue\u003e\n\n Name of the snapshot to use when creating this scratch org. Overrides the value of the \"snapshot\" option in the\n defintion file, if set.\n\n To view the names of the available snapshots for a given Dev Hub org, run the \"sf org list snapshot\" command.\n\n -t, --[no-]track-source Use source tracking for this scratch org. Set --no-track-source to disable source tracking.\n\n We recommend you enable source tracking in scratch orgs, which is why it's the default behavior. Source tracking\n allows you to track the changes you make to your metadata, both in your local project and in the scratch org, and to\n detect any conflicts between the two.\n\n To disable source tracking in the new scratch org, specify the --no-track-source flag. The main reason to disable\n source tracking is for performance. For example, while you probably want to deploy metadata and run Apex tests in\n your CI/CD jobs, you probably don't want to incur the costs of source tracking (checking for conflicts, polling the\n SourceMember object, various file system operations.) This is a good use case for disabling source tracking in the\n scratch org.\n\n -v, --target-dev-hub=\u003cvalue\u003e Username or alias of the Dev Hub org.\n\n Overrides the value of the target-dev-hub configuration variable, if set.\n\n -w, --wait=\u003cminutes\u003e Number of minutes to wait for the scratch org to be ready.\n\n If the command continues to run after the wait period, the CLI returns control of the terminal to you and displays\n the job ID. To resume the scratch org creation, run the org resume scratch command and pass it the job ID.\n\n --async Request the org, but don't wait for it to complete.\n\n The command immediately displays the job ID and returns control of the terminal to you. This way, you can continue\n to use the CLI. To resume the scratch org creation, run \"sf org resume scratch\".\n\n --release=preview|previous Release of the scratch org as compared to the Dev Hub release.\n\n By default, scratch orgs are on the same release as the Dev Hub. During Salesforce release transition periods, you\n can override this default behavior and opt in or out of the new release.\n\n --source-org=\u003cvalue\u003e\n\n 15-character ID of the org shape that the new scratch org is based on. Overrides the value of the \"sourceOrg\" option\n in the definition file, if set.\n\n To view the names of the available org shapes for a given Dev Hub org, run the \"sf org list shape\" command.\n\n --username=\u003cvalue\u003e\n\n Username of the scratch org admin user. Overrides the value of the \"username\" option in the definition file, if set.\n\n The username must be unique within the entire scratch org and sandbox universe. You must add your own logic to\n ensure uniqueness.\n\n Omit this flag to have Salesforce generate a unique username for your org.\n```\n\n_See code: [src/commands/org/create/scratch.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/create/scratch.ts)_\n\n## `sf org delete sandbox`\n\nDelete a sandbox.\n\n```\nUSAGE\n $ sf org delete sandbox -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [-p]\n\nFLAGS\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n -p, --no-prompt Don't prompt the user to confirm the deletion.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Delete a sandbox.\n\n Salesforce CLI marks the org for deletion in the production org that contains the sandbox licenses and then deletes\n all local references to the org from your computer.\n Specify a sandbox with either the username you used when you logged into it, or the alias you gave the sandbox when\n you created it. Run \"sf org list\" to view all your orgs, including sandboxes, and their aliases.\n Both the sandbox and the associated production org must already be authenticated with the CLI to successfully delete\n the sandbox.\n\nALIASES\n $ sf env delete sandbox\n\nEXAMPLES\n Delete a sandbox with alias my-sandbox:\n\n $ sf org delete sandbox --target-org my-sandbox\n\n Specify a username instead of an alias:\n\n $ sf org delete sandbox --target-org myusername@example.com.qa\n\n Delete the sandbox without prompting to confirm:\n\n $ sf org delete sandbox --target-org my-sandbox --no-prompt\n```\n\n_See code: [src/commands/org/delete/sandbox.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/delete/sandbox.ts)_\n\n## `sf org delete scratch`\n\nDelete a scratch org.\n\n```\nUSAGE\n $ sf org delete scratch -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [-p]\n\nFLAGS\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n -p, --no-prompt Don't prompt the user to confirm the deletion.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Delete a scratch org.\n\n Salesforce CLI marks the org for deletion in the Dev Hub org and then deletes all local references to the org from\n your computer.\n Specify a scratch org with either the username or the alias you gave the scratch org when you created it. Run \"sf org\n list\" to view all your orgs, including scratch orgs, and their aliases.\n\nALIASES\n $ sf env delete scratch\n\nEXAMPLES\n Delete a scratch org with alias my-scratch-org:\n\n $ sf org delete scratch --target-org my-scratch-org\n\n Specify a username instead of an alias:\n\n $ sf org delete scratch --target-org test-123456-abcdefg@example.com\n\n Delete the scratch org without prompting to confirm :\n\n $ sf org delete scratch --target-org my-scratch-org --no-prompt\n```\n\n_See code: [src/commands/org/delete/scratch.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/delete/scratch.ts)_\n\n## `sf org disable tracking`\n\nPrevent Salesforce CLI from tracking changes in your source files between your project and an org.\n\n```\nUSAGE\n $ sf org disable tracking -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e]\n\nFLAGS\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Prevent Salesforce CLI from tracking changes in your source files between your project and an org.\n\n Disabling source tracking has no direct effect on the org, it affects only your local environment. Specifically,\n Salesforce CLI stores the setting in the org's local configuration file so that no source tracking operations are\n executed when working with the org.\n\nEXAMPLES\n Disable source tracking for an org with alias \"myscratch\":\n\n $ sf org disable tracking --target-org myscratch\n\n Disable source tracking for an org using a username:\n\n $ sf org disable tracking --target-org you@example.com\n\n Disable source tracking for your default org:\n\n $ sf org disable tracking\n```\n\n_See code: [src/commands/org/disable/tracking.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/disable/tracking.ts)_\n\n## `sf org display`\n\nDisplay information about an org.\n\n```\nUSAGE\n $ sf org display -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [--verbose]\n\nFLAGS\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n --api-version=\u003cvalue\u003e Override the api version used for api requests made by this command\n --verbose Display the sfdxAuthUrl property.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Display information about an org.\n\n Output includes your access token, client Id, connected status, org ID, instance URL, username, and alias, if\n applicable.\n\n Use --verbose to include the SFDX auth URL. WARNING: The SFDX auth URL contains sensitive information, such as a\n refresh token that can be used to access an org. Don't share or distribute this URL or token.\n\n Including --verbose displays the sfdxAuthUrl property only if you authenticated to the org using \"org login web\" (not\n \"org login jwt\").\n\nALIASES\n $ sf force org display\n\nEXAMPLES\n Display information about your default org:\n\n $ sf org display\n\n Display information, including the sfdxAuthUrl property, about the org with alias TestOrg1:\n\n $ sf org display --target-org TestOrg1 --verbose\n```\n\n_See code: [src/commands/org/display.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/display.ts)_\n\n## `sf org enable tracking`\n\nAllow Salesforce CLI to track changes in your source files between your project and an org.\n\n```\nUSAGE\n $ sf org enable tracking -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e]\n\nFLAGS\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Allow Salesforce CLI to track changes in your source files between your project and an org.\n\n Enabling source tracking has no direct effect on the org, it affects only your local environment. Specifically,\n Salesforce CLI stores the setting in the org's local configuration file so that source tracking operations are\n executed when working with the org.\n\n This command throws an error if the org doesn't support tracking. Examples of orgs that don't support source tracking\n include Developer Edition orgs, production orgs, Partial Copy sandboxes, and Full sandboxes.\n\nEXAMPLES\n Enable source tracking for an org with alias \"myscratch\":\n\n $ sf org enable tracking --target-org myscratch\n\n Enable source tracking for an org using a username:\n\n $ sf org enable tracking --target-org you@example.com\n\n Enable source tracking for your default org:\n\n $ sf org enable tracking\n```\n\n_See code: [src/commands/org/enable/tracking.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/enable/tracking.ts)_\n\n## `sf org list`\n\nList all orgs you’ve created or authenticated to.\n\n```\nUSAGE\n $ sf org list [--json] [--flags-dir \u003cvalue\u003e] [--verbose] [--all] [--clean] [-p] [--skip-connection-status]\n\nFLAGS\n -p, --no-prompt Don't prompt for confirmation.\n --all Include expired, deleted, and unknown-status scratch orgs.\n --clean Remove all local org authorizations for non-active scratch orgs. Use \"org logout\" to\n remove non-scratch orgs.\n --skip-connection-status Skip retrieving the connection status of non-scratch orgs.\n --verbose List more information about each org.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nALIASES\n $ sf force org list\n\nEXAMPLES\n List all orgs you've created or authenticated to:\n\n $ sf org list\n\n List all orgs, including expired, deleted, and unknown-status orgs; don't include the connection status:\n\n $ sf org list --skip-connection-status --all\n\n List orgs and remove local org authorization info about non-active scratch orgs:\n\n $ sf org list --clean\n```\n\n_See code: [src/commands/org/list.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/list.ts)_\n\n## `sf org list metadata`\n\nList the metadata components and properties of a specified type.\n\n```\nUSAGE\n $ sf org list metadata -o \u003cvalue\u003e -m \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-f \u003cvalue\u003e]\n [--folder \u003cvalue\u003e]\n\nFLAGS\n -f, --output-file=\u003cvalue\u003e Pathname of the file in which to write the results.\n -m, --metadata-type=\u003cvalue\u003e (required) Metadata type to be retrieved, such as CustomObject; metadata type names are\n case-sensitive.\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n --api-version=\u003cvalue\u003e API version to use; default is the most recent API version.\n --folder=\u003cvalue\u003e Folder associated with the component; required for components that use folders; folder\n names are case-sensitive.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n List the metadata components and properties of a specified type.\n\n Use this command to identify individual components in your manifest file or if you want a high-level view of\n particular metadata types in your org. For example, you can use this command to return a list of names of all the\n CustomObject or Layout components in your org, then use this information in a retrieve command that returns a subset\n of these components.\n\n The username that you use to connect to the org must have the Modify All Data or Modify Metadata Through Metadata API\n Functions permission.\n\nALIASES\n $ sf force mdapi listmetadata\n\nEXAMPLES\n List the CustomObject components, and their properties, in the org with alias \"my-dev-org\":\n\n $ sf org list metadata --metadata-type CustomObject --target-org my-dev-org\n\n List the CustomObject components in your default org, write the output to the specified file, and use API version\n 57.0:\n\n $ sf org list metadata --metadata-type CustomObject --api-version 57.0 --output-file /path/to/outputfilename.txt\n\n List the Dashboard components in your default org that are contained in the \"folderSales\" folder, write the output\n to the specified file, and use API version 57.0:\n\n $ sf org list metadata --metadata-type Dashboard --folder folderSales --api-version 57.0 --output-file \\\n /path/to/outputfilename.txt\n\nFLAG DESCRIPTIONS\n --api-version=\u003cvalue\u003e API version to use; default is the most recent API version.\n\n Override the api version used for api requests made by this command\n\n --folder=\u003cvalue\u003e\n\n Folder associated with the component; required for components that use folders; folder names are case-sensitive.\n\n Examples of metadata types that use folders are Dashboard, Document, EmailTemplate, and Report.\n```\n\n_See code: [src/commands/org/list/metadata.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/list/metadata.ts)_\n\n## `sf org list metadata-types`\n\nDisplay details about the metadata types that are enabled for your org.\n\n```\nUSAGE\n $ sf org list metadata-types -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-f \u003cvalue\u003e]\n\nFLAGS\n -f, --output-file=\u003cvalue\u003e Pathname of the file in which to write the results.\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n --api-version=\u003cvalue\u003e API version to use; default is the most recent API version.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Display details about the metadata types that are enabled for your org.\n\n The information includes Apex classes and triggers, custom objects, custom fields on standard objects, tab sets that\n define an app, and many other metadata types. Use this information to identify the syntax needed for a \u003cname\u003e element\n in a manifest file (package.xml).\n\n The username that you use to connect to the org must have the Modify All Data or Modify Metadata Through Metadata API\n Functions permission.\n\nALIASES\n $ sf force mdapi describemetadata\n\nEXAMPLES\n Display information about all known and enabled metadata types in the org with alias \"my-dev-org\" using API version\n 57.0:\n\n $ sf org list metadata-types --api-version 57.0 --target-org my-dev-org\n\n Display only the metadata types that aren't yet supported by Salesforce CLI in your default org and write the\n results to the specified file:\n\n $ sf org list metadata-types --output-file /path/to/outputfilename.txt --filter-known\n\nFLAG DESCRIPTIONS\n -f, --output-file=\u003cvalue\u003e Pathname of the file in which to write the results.\n\n Directing the output to a file makes it easier to extract relevant information for your package.xml manifest file.\n The default output destination is the terminal or command window console.\n\n --api-version=\u003cvalue\u003e API version to use; default is the most recent API version.\n\n Override the api version used for api requests made by this command\n```\n\n_See code: [src/commands/org/list/metadata-types.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/list/metadata-types.ts)_\n\n## `sf org open`\n\nOpen your default scratch org, or another specified org, in a browser.\n\n```\nUSAGE\n $ sf org open -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [--private | -r | -b\n chrome|edge|firefox] [-p \u003cvalue\u003e | -f \u003cvalue\u003e]\n\nFLAGS\n -b, --browser=\u003coption\u003e Browser where the org opens.\n \u003coptions: chrome|edge|firefox\u003e\n -f, --source-file=\u003cvalue\u003e Path to ApexPage, FlexiPage, Flow, or Agent metadata to open in the associated Builder.\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n -p, --path=\u003cvalue\u003e [env: FORCE_OPEN_URL] Navigation URL path to open a specific page.\n -r, --url-only Display navigation URL, but don’t launch browser.\n --api-version=\u003cvalue\u003e Override the api version used for api requests made by this command\n --private Open the org in the default browser using private (incognito) mode.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Open your default scratch org, or another specified org, in a browser.\n\n To open a specific page, specify the portion of the URL after \"https://mydomain.my.salesforce.com\" as the value for\n the --path flag. For example, specify \"--path lightning\" to open Lightning Experience, or specify \"--path\n /apex/YourPage\" to open a Visualforce page.\n\n Use the --source-file flag to open ApexPage, FlexiPage, Flow, or Agent metadata from your local project in the\n associated Builder within the Org.\n\n To generate a URL but not launch it in your browser, specify --url-only.\n\n To open in a specific browser, use the --browser flag. Supported browsers are \"chrome\", \"edge\", and \"firefox\". If you\n don't specify --browser, the org opens in your default browser.\n\nALIASES\n $ sf force org open\n $ sf force source open\n\nEXAMPLES\n Open your default org in your default browser:\n\n $ sf org open\n\n Open your default org in an incognito window of your default browser:\n\n $ sf org open --private\n\n Open the org with alias MyTestOrg1 in the Firefox browser:\n\n $ sf org open --target-org MyTestOrg1 --browser firefox\n\n Display the navigation URL for the Lightning Experience page for your default org, but don't open the page in a\n browser:\n\n $ sf org open --url-only --path lightning\n\n Open a local Lightning page in your default org's Lightning App Builder:\n\n $ sf org open --source-file force-app/main/default/flexipages/Hello.flexipage-meta.xml\n\n Open a local Flow in Flow Builder:\n\n $ sf org open --source-file force-app/main/default/flows/Hello.flow-meta.xml\n\n Open local Agent metadata (Bot) in Agent Builder:\n\n $ sf org open --source-file force-app/main/default/bots/Coral_Cloud_Agent/Coral_Cloud_Agent.bot-meta.xml\n```\n\n_See code: [src/commands/org/open.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/open.ts)_\n\n## `sf org open agent`\n\nOpen an agent in your org's Agentforce Builder UI in a browser.\n\n```\nUSAGE\n $ sf org open agent -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [-n \u003cvalue\u003e] [--private | -r\n | -b chrome|edge|firefox] [--authoring-bundle \u003cvalue\u003e] [--version \u003cvalue\u003e]\n\nFLAGS\n -b, --browser=\u003coption\u003e Browser where the org opens.\n \u003coptions: chrome|edge|firefox\u003e\n -n, --api-name=\u003cvalue\u003e API name, also known as developer name, of the agent you want to open in the org's\n Agentforce Builder UI.\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n -r, --url-only Display navigation URL, but don’t launch browser.\n --api-version=\u003cvalue\u003e Override the api version used for api requests made by this command\n --authoring-bundle=\u003cvalue\u003e API name of the agent's authoring bundle to open in Agentforce Builder.\n --private Open the agent in the default browser using private (incognito) mode.\n --version=\u003cvalue\u003e Version number of the agent to open in Agentforce Builder. If not specified, the\n highest version is opened by default.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Open an agent in your org's Agentforce Builder UI in a browser.\n\n Use the --api-name flag to open an agent using its API name in the Agentforce Builder UI of your org. Alternatively,\n use the --authoring-bundle flag to open an agent using the API name of its authoring bundle. The two API names are\n typically the same for the same agent. Optionally specify the --version flag to open a specific version of the agent.\n\n To generate the URL but not launch it in your browser, specify --url-only.\n\n To open Agentforce Builder in a specific browser, use the --browser flag. Supported browsers are \"chrome\", \"edge\", and\n \"firefox\". If you don't specify --browser, the org opens in your default browser.\n\nEXAMPLES\n Open the agent with API name Coral_Cloud_Agent in your default org using your default browser; opens the highest\n version:\n\n $ sf org open agent --api-name Coral_Cloud_Agent\n\n Open the agent in an incognito window of your default browser:\n\n $ sf org open agent --private --api-name Coral_Cloud_Agent:\n\n Open the agent in an org with alias MyTestOrg1 using the Firefox browser:\n\n $ sf org open agent --target-org MyTestOrg1 --browser firefox --api-name Coral_Cloud_Agent\n\n Open an agent in Agentforce Builder using its authoring bundle API name:\n\n $ sf org open agent --authoring-bundle Coral_Cloud_Agent\n\n Open a version 1 of an agent in Agentforce Builder:\n\n $ sf org open agent --authoring-bundle Coral_Cloud_Agent --version 1\n```\n\n_See code: [src/commands/org/open/agent.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/open/agent.ts)_\n\n## `sf org open authoring-bundle`\n\nOpen your org in Agentforce Studio, specifically in the list view showing the list of agents.\n\n```\nUSAGE\n $ sf org open authoring-bundle -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--api-version \u003cvalue\u003e] [--private | -r | -b\n chrome|edge|firefox]\n\nFLAGS\n -b, --browser=\u003coption\u003e Browser where the org opens.\n \u003coptions: chrome|edge|firefox\u003e\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the target org. Not required if the `target-org`\n configuration variable is already set.\n -r, --url-only Display navigation URL, but don't launch browser.\n --api-version=\u003cvalue\u003e Override the api version used for api requests made by this command\n --private Open the org in the default browser using private (incognito) mode.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Open your org in Agentforce Studio, specifically in the list view showing the list of agents.\n\n The list view shows the agents in your org that are implemented with Agent Script and an authoring bundle. Click on an\n agent name to open it in Agentforce Builder in a new browser window.\n\n To generate the URL but not launch it in your browser, specify --url-only.\n\nEXAMPLES\n Open the agents list view in your default org using your default browser:\n\n $ sf org open authoring-bundle\n\n Open the agents list view in an incognito window of your default browser:\n\n $ sf org open authoring-bundle --private\n\n Open the agents list view in an org with alias MyTestOrg1 using the Firefox browser:\n\n $ sf org open authoring-bundle --target-org MyTestOrg1 --browser firefox\n```\n\n_See code: [src/commands/org/open/authoring-bundle.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/open/authoring-bundle.ts)_\n\n## `sf org refresh sandbox`\n\nRefresh a sandbox org using the sandbox name.\n\n```\nUSAGE\n $ sf org refresh sandbox -o \u003cvalue\u003e [--json] [--flags-dir \u003cvalue\u003e] [--no-auto-activate] [-w \u003cminutes\u003e | --async] [-i\n \u003cseconds\u003e | ] [--source-sandbox-name \u003cvalue\u003e | --source-id \u003cvalue\u003e] [-n \u003cvalue\u003e] [-f \u003cvalue\u003e] [--no-prompt]\n\nFLAGS\n -f, --definition-file=\u003cvalue\u003e Path to a sandbox definition file for overriding its configuration when you refresh\n it.\n -i, --poll-interval=\u003cseconds\u003e Number of seconds to wait between status polling requests.\n -n, --name=\u003cvalue\u003e Name of the existing sandbox org in your production org that you want to refresh.\n -o, --target-org=\u003cvalue\u003e (required) Username or alias of the production org that contains the sandbox\n license.\n -w, --wait=\u003cminutes\u003e Number of minutes to poll for sandbox refresh status.\n --async Request the sandbox refresh, but don't wait for it to complete.\n --no-auto-activate Disable auto-activation of the sandbox after a successful refresh.\n --no-prompt Don't prompt for confirmation about the sandbox refresh.\n --source-id=\u003cvalue\u003e ID of the sandbox org that becomes the new source org for the refreshed sandbox.\n --source-sandbox-name=\u003cvalue\u003e Name of the sandbox org that becomes the new source org for the refreshed sandbox.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Refresh a sandbox org using the sandbox name.\n\n Refreshing a sandbox copies the metadata, and optionally data, from your source org to the refreshed sandbox org. You\n can optionally specify a definition file if you want to change the configuration of the refreshed sandbox, such as its\n license type or template ID. You can also use the --source-id or --source-sandbox-name flags to change the refreshed\n sandbox org's original source org to a new org; in this case, the refreshed sandbox org's metadata is updated with the\n new source org's metadata.\n\n You're not allowed to change the sandbox name when you refresh it with this command. If you want to change the sandbox\n name, first delete it with the \"org delete sandbox\" command. And then recreate it with the \"org create sandbox\"\n command and give it a new name.\n\nEXAMPLES\n Refresh the sandbox named \"devSbx1\". The production org that contains the sandbox license has the alias \"prodOrg\".\n\n $ sf org refresh sandbox --name devSbx1 --target-org prodOrg\n\n Refresh the sandbox named \"devSbx2\", and override the configuration of the refreshed sandbox with the properties in\n the specified defintion file. The default target org is the production org, so you don't need to specify the\n `--target-org` flag in this case.\n\n $ sf org refresh sandbox --name devSbx2 --definition-file devSbx2-config.json\n\n Refresh the sandbox using the name defined in the definition file. The production org that contains the sandbox\n license has the alias \"prodOrg\".\n\n $ sf org refresh sandbox --definition-file devSbx3-config.json --target-org prodOrg\n\n Refresh the sandbox named \"devSbx2\" by changing its original source org to be a sandbox called \"devSbx3\":\n\n $ sf org refresh sandbox --name devSbx2 --source-sandbox-name devSbx3 --target-org prodOrg\n\nFLAG DESCRIPTIONS\n -f, --definition-file=\u003cvalue\u003e Path to a sandbox definition file for overriding its configuration when you refresh it.\n\n The sandbox definition file is a blueprint for the sandbox; use the file to change the sandbox configuration during\n a refresh. If you don't want to change the sandbox configuration when you refresh it, then simply use the --name\n flag to specify the sandbox and don't use this flag. See\n \u003chttps://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_sandbox_definition.htm\u003e for all\n the options you can specify in the definition file.\n\n -w, --wait=\u003cminutes\u003e Number of minutes to poll for sandbox refresh status.\n\n If the command continues to run after the wait period, the CLI returns control of the terminal to you and displays\n the \"sf org resume sandbox\" command for you run to check the status of the refresh. The displayed command includes\n the job ID for the running sandbox refresh.\n\n --async Request the sandbox refresh, but don't wait for it to complete.\n\n The command immediately displays the job ID and returns control of the terminal to you. This way, you can continue\n to use the CLI. To check the status of the sandbox refresh, run \"sf org resume sandbox\".\n\n --no-auto-activate Disable auto-activation of the sandbox after a successful refresh.\n\n By default, a sandbox auto-activates after a refresh. Use this flag to control sandbox activation manually.\n\n --source-id=\u003cvalue\u003e ID of the sandbox org that becomes the new source org for the refreshed sandbox.\n\n The value of --source-id must be an existing sandbox. The new source sandbox, and the refreshed sandbox specified\n with the --name flag, must both be associated with the production org (--target-org) that contains the sandbox\n licenses.\n\n You can specify either --source-id or --source-sandbox-name when refreshing an existing sandbox, but not both.\n\n --source-sandbox-name=\u003cvalue\u003e Name of the sandbox org that becomes the new source org for the refreshed sandbox.\n\n The value of --source-sandbox-name must be an existing sandbox. The new source sandbox, and the refreshed sandbox\n specified with the --name flag, must both be associated with the production org (--target-org) that contains the\n sandbox licenses.\n\n You can specify either --source-sandbox-name or --source-id when refreshing an existing sandbox, but not both.\n```\n\n_See code: [src/commands/org/refresh/sandbox.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/refresh/sandbox.ts)_\n\n## `sf org resume sandbox`\n\nCheck the status of a sandbox creation, and log in to it if it's ready.\n\n```\nUSAGE\n $ sf org resume sandbox [--json] [--flags-dir \u003cvalue\u003e] [-w \u003cminutes\u003e] [-n \u003cvalue\u003e | -i \u003cvalue\u003e] [-l] [-o \u003cvalue\u003e]\n\nFLAGS\n -i, --job-id=\u003cvalue\u003e Job ID of the incomplete sandbox creation that you want to check the status of.\n -l, --use-most-recent Use the most recent sandbox create request.\n -n, --name=\u003cvalue\u003e Name of the sandbox org.\n -o, --target-org=\u003cvalue\u003e Username or alias of the production org that contains the sandbox license.\n -w, --wait=\u003cminutes\u003e [default: 0 minutes] Number of minutes to wait for the sandbox org to be ready.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Check the status of a sandbox creation, and log in to it if it's ready.\n\n Sandbox creation can take a long time. If the original \"sf org create sandbox\" command either times out, or you\n specified the --async flag, the command displays a job ID. Use this job ID to check whether the sandbox creation is\n complete, and if it is, the command then logs into it.\n\n You can also use the sandbox name to check the status or the --use-most-recent flag to use the job ID of the most\n recent sandbox creation.\n\nALIASES\n $ sf env resume sandbox\n\nEXAMPLES\n Check the status of a sandbox creation using its name and specify a production org with alias \"prodOrg\":\n\n $ sf org resume sandbox --name mysandbox --target-org prodOrg\n\n Check the status using the job ID:\n\n $ sf org resume sandbox --job-id 0GRxxxxxxxx\n\n Check the status of the most recent sandbox create request:\n\n $ sf org resume sandbox --use-most-recent\n\nFLAG DESCRIPTIONS\n -i, --job-id=\u003cvalue\u003e Job ID of the incomplete sandbox creation that you want to check the status of.\n\n The job ID is valid for 24 hours after you start the sandbox creation.\n\n -o, --target-org=\u003cvalue\u003e Username or alias of the production org that contains the sandbox license.\n\n When it creates the sandbox org, Salesforce copies the metadata, and optionally data, from your production org to\n the new sandbox org.\n\n -w, --wait=\u003cminutes\u003e Number of minutes to wait for the sandbox org to be ready.\n\n If the command continues to run after the wait period, the CLI returns control of the terminal window to you and\n returns the job ID. To resume checking the sandbox creation, rerun this command.\n```\n\n_See code: [src/commands/org/resume/sandbox.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/resume/sandbox.ts)_\n\n## `sf org resume scratch`\n\nResume the creation of an incomplete scratch org.\n\n```\nUSAGE\n $ sf org resume scratch [--json] [--flags-dir \u003cvalue\u003e] [-i \u003cvalue\u003e] [-r] [-w \u003cminutes\u003e]\n\nFLAGS\n -i, --job-id=\u003cvalue\u003e Job ID of the incomplete scratch org create that you want to resume.\n -r, --use-most-recent Use the job ID of the most recent incomplete scratch org.\n -w, --wait=\u003cminutes\u003e [default: 0 minutes] Number of minutes to wait for the scratch org to be ready.\n\nGLOBAL FLAGS\n --flags-dir=\u003cvalue\u003e Import flag values from a directory.\n --json Format output as json.\n\nDESCRIPTION\n Resume the creation of an incomplete scratch org.\n\n When the original \"sf org create scratch\" command either times out or is run with the --async flag, it displays a job\n ID.\n\n Run this command by either passing it a job ID or using the --use-most-recent flag to specify the most recent\n incomplete scratch org.\n\nALIASES\n $ sf env resume scratch\n\nEXAMPLES\n Resume a scratch org create with a job ID:\n\n $ sf org resume scratch --job-id 2SR3u0000008fBDGAY\n\n Resume your most recent incomplete scratch org:\n\n $ sf org resume scratch --use-most-recent\n\nFLAG DESCRIPTIONS\n -i, --job-id=\u003cvalue\u003e Job ID of the incomplete scratch org create that you want to resume.\n\n The job ID is the same as the record ID of the incomplete scratch org in the ScratchOrgInfo object of the Dev Hub.\n\n The job ID is valid for 24 hours after you start the scratch org creation.\n\n -w, --wait=\u003cminutes\u003e Number of minutes to wait for the scratch org to be ready.\n\n If the command continues to run after the wait period, the CLI returns control of the terminal window to you and\n returns the job ID. To resume checking the scratch creation, rerun this command.\n```\n\n_See code: [src/commands/org/resume/scratch.ts](https://github.com/salesforcecli/plugin-org/blob/5.11.5/src/commands/org/resume/scratch.ts)_\n\n\u003c!-- commandsstop --\u003e\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsalesforcecli%2Fplugin-org","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fsalesforcecli%2Fplugin-org","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fsalesforcecli%2Fplugin-org/lists"}