The Coder CLI is automatically injected and authenticated inside of all Coder workspaces.
You can also use the CLI on your local machine. To do so, you'll need to download, install, and authenticate the CLI with Coder.
The version numbering for CLI releases mirrors the version numbering for Coder releases. Download the CLI release whose version number matches your Coder version number.
brew install cdr/coder/coder-cli
Download releases from GitHub:
coderbinary and copy it to a location you've added to your
coder-cli-windows.zip) and download the file
Make sure that your user's
PATHenvironment variable contains the location you chose in step 3.
Once you've installed the CLI, authenticate the client with your Coder account.
coder login [https://coder.domain.com]
If you're logged into Coder via your web browser, the process will open a new browser window that displays a session token. Copy the token, and paste it into the terminal prompt.
To support cases where the browser-based authentication flow isn't appropriate,
such as in CI/CD pipelines, the Coder CLI can also be authenticated with the
CODER_URL environment variables.
Generate a static authentication token with the following command:
coder tokens create my-token
To update the CLI to the version corresponding to your current Coder deployment, run (you will be asked to confirm all changes before they're performed):
coder update command accepts the following arguments:
--coder: specify the Coder instance the CLI should use to query the version
--version: specify the version that the CLI should download and upgrade to
--force: omit prompts asking for change confirmations
Note: Coder CLI will not update if it is located under