On this page

Updates and existing installations

Update an apt-managed Linux installation

Schedule a maintenance window. Package updates can restart running services. On the Linux host, refresh the available versions:

Terminal
sudo apt update

Run the command for the product installed on that host:

Terminal
sudo apt install --only-upgrade steiger
Terminal
sudo apt install --only-upgrade hybrid-bridge
# Or, for the CLI:
sudo apt install --only-upgrade cococo-cli

Check service and application connectivity afterwards using the installation checks above. These updates preserve generated configuration and state. Do not use the older shell installer to update a machine managed by apt.

If you receive “Could not get lock,” another package update may be running. Let it finish, then retry. Do not delete apt's lock files.

Update a Windows installation

Steiger: use the next MSI release approved for your site. Verify its checksum, run the installer during the maintenance window, then check SteigerAgent and steiger status. Existing machine configuration and state are retained. The published current-version pointer is steiger/latest.txt; your implementation team should confirm the version to deploy.

Hybrid Bridge: use the next MSI release approved for your site. Verify its checksum and run it during the agreed maintenance window. Existing configuration and certificates are retained; the installer starts the configured service. Check TripleCLabsController, cloud connectivity and an integration afterward. Do not claim another bundle merely to update. Removing the MSI stops and removes the service but retains generated configuration and data.

CoCoCo CLI: close running CLI/editor connections, verify and run the approved newer MSI as the same Windows user, then open a new terminal and check cococo --version. Uninstall through Installed apps; credentials and project files are retained. On either operating system, after updating the binary, run cococo upgrade in existing workspaces to refresh their authoring guidance, then restart editor/MCP connections. This command updates workspace guidance; it does not download a newer CLI binary.

Update or remove a macOS installation

Close running CLI commands and editor connections before updating the CLI. Schedule Bridge updates during a maintenance window. Run the upgrade command only for the products installed on this Mac:

Terminal
brew update
brew upgrade tripleclabs/tap/cococo-cli-beta
brew upgrade tripleclabs/tap/hybrid-bridge
brew services restart tripleclabs/tap/hybrid-bridge

Check command versions afterward, confirm Bridge connectivity and test an integration. For existing CLI workspaces, run cococo upgrade to refresh guidance and restart editor/MCP connections; this does not download a new CLI binary.

To remove Hybrid Bridge, stop its service first:

Terminal
brew services stop tripleclabs/tap/hybrid-bridge
brew uninstall tripleclabs/tap/hybrid-bridge

To remove the CLI, run brew uninstall tripleclabs/tap/cococo-cli-beta. Bridge configuration, certificates, state and logs survive uninstall. CLI credentials and project files also remain. Removal is not a backup or a reset.

Moving an older installation to apt, MSI or Homebrew

If Linux already has an installation created by a downloaded shell script, arrange a migration with your CoCoCo contact before running apt install. The package deliberately refuses installations whose older binaries or service definitions would conflict. That message protects the existing installation; do not delete the reported files as a workaround.

Older Steiger appliances may need an adoption upgrade before they can switch to apt. This can stop application services and must be planned for the site. Custom service definitions also need review.

On Windows, older script-installed Steiger and Hybrid Bridge services need a handover before the first MSI installation. The Bridge MSI refuses to take over an existing script-installed service automatically. Ask your implementation team for the migration procedure; do not delete configuration, certificates or state yourself.

For CoCoCo CLI, check Get-Command cococo -All on Windows or type -a cococo on Linux before and after installation. A manual copy in a user or local bin folder can hide the MSI/apt-installed copy. Ask IT to identify and move aside the old executable and its obsolete PATH entry. Keep workspaces and credentials. Never delete /usr/bin/cococo manually after apt owns it.

On macOS, an existing non-Homebrew Bridge installation is not migrated automatically. Ask your implementation team to review its service registration, configuration, identity and persistent state before switching. Never run two bridge instances with the same enrolled identity. Use which -a cococo and which -a hybrid-bridge to identify old manual executables; do not delete credentials or project data to resolve PATH conflicts.

Removal is not a backup or a reset

Before decommissioning a host, agree how to preserve application data, credentials and backups. Linux package removal, and even purge, retains generated configuration and state. Removing the software does not necessarily erase its data. Do not delete the folders in the reference table to troubleshoot a connection problem.