ConductorOne Docs

Install and authorize Cone

Follow these instructions to install and sign into Cone, the ConductorOne CLI.

Supported operating systems

ConductorOne provides cone binaries for popular operating systems including macOS, Windows, and Linux on the x86 and ARM platforms. If your platform is not listed, please contact us or build from source.

Install Cone

To install cone, use one of the following two methods:

$ brew install conductorone/cone/cone

Authorize Cone

To authorize cone:

  1. Run cone login <tenant-name or tenant-url>, passing in the name (such as or URL (such as of your ConductorOne instance.

  2. A new browser window opens with an authorization message and code. Review the authorization code against the code shown in your terminal and click Authorize. Once you see the Cone has been authorized message, it’s safe to close this browser tab.

  3. Cone generates an API key for you, and then creates a config file at $HOME/<user name>/.conductorone/config.yaml to store and access your credentials and user-specific data.

That’s it! You’re ready to start using cone. Check out the Cone command reference for an overview of all available commands, subcommands, and flags.

Generating a new API key

If needed, you can view your API key and its client-id, or regenerate a new key, client-id, and client-secret. Go to your username in the ConductorOne app and click API keys. You’ll see an API key named “Created by Cone”.

Working with the configuration file

The configuration file generated by cone during the authorization process file is in YAML format and is primarily used for storing profile details. Here’s an example configuration file:

    client-id: <Your-Client-ID-Goes-Here>
    client-secret: <Your-Client-Secret-Goes-Here>

You can add multiple profiles to the configuration file by adding another key to the profiles map, and cone will use this profile when the $CONE_PROFILE environment variable or --profile command line flag are passed to the tool.