On this page
Developer CLI on Linux
These instructions are for Ubuntu 24.04 or Debian 13, on amd64 or arm64. These installations use apt, the operating system's software installer and updater. You do not need to build software or install developer tools.
1. Connect to the Linux machine
Use its terminal directly, or connect from Windows PowerShell using SSH if your administrator has enabled it. Replace your-user and server-address with the details you were given:
ssh your-user@server-addressOn the first connection, confirm the server fingerprint with your administrator before accepting it. After login, the following commands run on the Linux machine, not on your Windows PC.
sudo means “run this command with administrator privileges.” It may ask for your Linux account password. No characters appear while you type that password; this is normal. If the account is not allowed to use sudo, ask the Linux administrator to complete the installation.
Check the operating system and processor type:
cat /etc/os-release
dpkg --print-architectureExpect Ubuntu 24.04 or Debian 13, and amd64 or arm64. If these differ, ask your implementation team before continuing.
2. Add the CoCoCo software source
Run the following blocks in order. They add the official package source and its signing key. The key lets apt verify packages from this source.
sudo apt update
sudo apt install -y ca-certificates curl
sudo install -d -m 0755 /etc/apt/keyringssudo curl -fsSL \
https://install.tripleclabs.de/apt/tripleclabs.asc \
-o /etc/apt/keyrings/tripleclabs.asc
sudo chmod 0644 /etc/apt/keyrings/tripleclabs.ascsudo curl -fsSL \
https://install.tripleclabs.de/apt/tripleclabs.sources \
-o /etc/apt/sources.list.d/tripleclabs.sources
sudo apt updateA backslash at the end of a Linux command line means “continue on the next line.” Copy the complete block. Wait for each block to finish before starting the next. If a command fails, stop and resolve the error.
The last command must complete without a signature or certificate error. Never work around these errors by allowing unsigned packages. Use these steps once per machine, even if you need more than one product.
3. Install CoCoCo CLI
Add the beta source and the CLI-only package preference after adding the shared signing key and stable source.
sudo curl -fsSL https://install.tripleclabs.de/apt/cococo-cli.pref -o /etc/apt/preferences.d/cococo-cli
sudo curl -fsSL https://install.tripleclabs.de/apt/tripleclabs-beta.sources -o /etc/apt/sources.list.d/tripleclabs-beta.sources
sudo apt update
sudo apt install cococo-cliThe package is called cococo-cli, but its command is cococo. It installs /usr/bin/cococo. Run the following as your ordinary user, without sudo:
cococo --version
command -v cococo
cococo --helpExpect cococo 0.1.0-beta.12 and /usr/bin/cococo. There is no systemd service to start and no provisioning bundle to import. Ask your implementation team for the platform address, environment name and workspace setup instructions. Installing the CLI does not sign you in or change platform configuration.
If the path points to ~/.local/bin/cococo or /usr/local/bin/cococo, an older manual installation is taking precedence. Follow the migration guidance below before using it.