Uninstall and Purge CMX on Linux, macOS, and Windows

CMX ships a full-purge procedure for each supported platform. This page walks you through restoring your coding agents to their original configuration, stopping the CMX gateway, and removing every trace of CMX, including processes, auto-start services, credentials, configuration, session history, cached state, and both standalone and package-manager installs.

A full purge permanently deletes all local CMX data and preferences. It does not delete your Codex, OpenCode, or AI-provider accounts.

Before Removing CMX

Restore your coding agents’ original connection settings while the CMX executable and its routing backups are still available.

Restore agent connections

cmx harness disable

Restart Codex and OpenCode after this command. If CMX reports that no supported agent is configured, continue. If it reports that it refused to restore an edited configuration, stop and resolve that error before purging. Otherwise the coding agent may keep pointing at the removed local gateway.

Sign out and stop the gateway

cmx logout
cmx stop

Never add || true to cmx harness disable. A genuine restoration failure needs attention before CMX is deleted.

Complete Purge

Choose the tab for your operating system and run the commands as the same user that installed CMX.

Linux
Mac
Windows

Run as your normal desktop user:

cmx harness disable
cmx logout
cmx stop

systemctl --user disable --now cmx.service 2>/dev/null || true
rm -f "${XDG_CONFIG_HOME:-$HOME/.config}/systemd/user/cmx.service"
systemctl --user daemon-reload
systemctl --user reset-failed
pkill -x cmx 2>/dev/null || true

if command -v npm >/dev/null 2>&1; then
  npm uninstall --global @compressius/cmx || true
fi
if command -v pnpm >/dev/null 2>&1; then
  pnpm remove --global @compressius/cmx || true
fi

sudo rm -f /usr/local/bin/cmx /usr/bin/cmx
rm -f "$HOME/.local/bin/cmx"

rm -rf \
  "${XDG_CONFIG_HOME:-$HOME/.config}/cmx" \
  "${XDG_DATA_HOME:-$HOME/.local/share}/cmx" \
  "${XDG_STATE_HOME:-$HOME/.local/state}/cmx"

hash -r

Verify the purge:

if command -v cmx >/dev/null 2>&1; then
  echo "CMX is still installed at: $(command -v cmx)"
else
  echo "CMX executable removed"
fi

if systemctl --user list-unit-files cmx.service --no-legend 2>/dev/null | grep -q cmx; then
  echo "CMX systemd service still exists"
else
  echo "CMX systemd service removed"
fi

if pgrep -x cmx >/dev/null; then
  echo "A CMX process is still running"
else
  echo "No CMX process is running"
fi

First restore routing and stop CMX:

cmx harness disable
cmx logout
cmx stop

Then remove package-manager and standalone installs:

pkill -x cmx 2>/dev/null || true

if command -v npm >/dev/null 2>&1; then
  npm uninstall --global @compressius/cmx || true
fi
if command -v pnpm >/dev/null 2>&1; then
  pnpm remove --global @compressius/cmx || true
fi

sudo rm -f /usr/local/bin/cmx /opt/homebrew/bin/cmx
rm -f "$HOME/.local/bin/cmx"

rm -rf "$HOME/Library/Application Support/cmx"

hash -r

CMX does not install a macOS launchd service automatically. If you created one manually, unload and delete only the exact plist you created. Replace YOUR-CMX-SERVICE.plist with your real filename; do not delete unrelated LaunchAgent files.

launchctl bootout "gui/$(id -u)" "$HOME/Library/LaunchAgents/YOUR-CMX-SERVICE.plist" 2>/dev/null || true
rm -f "$HOME/Library/LaunchAgents/YOUR-CMX-SERVICE.plist"

Verify the purge:

if command -v cmx >/dev/null 2>&1; then
  echo "CMX is still installed at: $(command -v cmx)"
else
  echo "CMX executable removed"
fi

if pgrep -x cmx >/dev/null; then
  echo "A CMX process is still running"
else
  echo "No CMX process is running"
fi

Open PowerShell as the same Windows user that installed CMX. Restore coding-agent routing first, and stop if it reports a real restoration error:

cmx harness disable
cmx logout
cmx stop

Then remove processes, packages, files, PATH entry, and shortcut:

Get-Process -Name cmx -ErrorAction SilentlyContinue |
    Stop-Process -Force

if (Get-Command npm -ErrorAction SilentlyContinue) {
    npm uninstall --global @compressius/cmx
}
if (Get-Command pnpm -ErrorAction SilentlyContinue) {
    pnpm remove --global @compressius/cmx
}

$cmxInstallDir = Join-Path $env:LOCALAPPDATA 'CMX\bin'
$cmxLocalData  = Join-Path $env:LOCALAPPDATA 'cmx'
$cmxConfig     = Join-Path $env:APPDATA 'cmx'
$cmxShortcut   = Join-Path $env:APPDATA 'Microsoft\Windows\Start Menu\Programs\CMX.lnk'

Remove-Item -LiteralPath $cmxLocalData -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item -LiteralPath $cmxConfig    -Recurse -Force -ErrorAction SilentlyContinue
Remove-Item -LiteralPath $cmxShortcut  -Force -ErrorAction SilentlyContinue

$userPath = [Environment]::GetEnvironmentVariable('Path', 'User')
if ($userPath) {
    $cleanPath = (($userPath -split ';') | Where-Object {
        $_ -and $_.TrimEnd('\') -ine $cmxInstallDir.TrimEnd('\')
    }) -join ';'
    [Environment]::SetEnvironmentVariable('Path', $cleanPath, 'User')
}

Remove-Item Alias:cmx -ErrorAction SilentlyContinue

CMX does not install a Windows service or scheduled task automatically. If you created one manually, remove only the CMX entry you created.

For a service named cmx:

$service = Get-Service -Name cmx -ErrorAction SilentlyContinue
if ($service) {
    Stop-Service -Name cmx -Force -ErrorAction SilentlyContinue
    sc.exe delete cmx
}

For a scheduled task named CMX:

$task = Get-ScheduledTask -TaskName CMX -ErrorAction SilentlyContinue
if ($task) {
    Unregister-ScheduledTask -TaskName CMX -Confirm:$false
}

Close PowerShell and open a new window so the updated PATH takes effect.Verify the purge:

if (Get-Command cmx -ErrorAction SilentlyContinue) {
    Write-Host "CMX is still installed at:"
    Get-Command cmx | Select-Object -ExpandProperty Source
} else {
    Write-Host "CMX executable removed"
}

if (Get-Process -Name cmx -ErrorAction SilentlyContinue) {
    Write-Host "A CMX process is still running"
} else {
    Write-Host "No CMX process is running"
}

Reinstall CMX

curl -sSfL https://compressi.us/install.sh | sh

Invoke-WebRequest -UseBasicParsing 'https://compressi.us/install.ps1' -OutFile "$env:TEMP\cmx-install.ps1"
powershell -NoProfile -ExecutionPolicy Bypass -File "$env:TEMP\cmx-install.ps1"

npm install --global @compressius/cmx

pnpm add --global @compressius/cmx

After reinstalling, restart your coding agent and verify the full path:

cmx --version
cmx doctor
cmx harness verify
cmx status

Then send a real request through Codex or OpenCode and confirm CMX recorded it:

cmx stats

A healthy status endpoint or successful setup alone does not prove that coding-agent traffic is flowing through CMX. A real request followed by new activity in cmx stats is the relevant check.

Get Started

Setup & Configuration

Using CMX

CLI Reference

Help

Uninstall and Purge CMX on Linux, macOS, and Windows

Before Removing CMX

Complete Purge

Reinstall CMX

​Before Removing CMX

​Complete Purge

​Reinstall CMX

Before Removing CMX

Complete Purge

Reinstall CMX