Update CTK safely when watches are running

01

1. Download without stopping collection

When CTK offers a new version, use the update action to download it. The update badge shows progress and later offers Restart to update. Downloading does not stop active watches.

Keep the app open if you want collection to continue. A downloaded package is not installed merely because its progress reached 100 percent.

02

2. Understand a blocked restart

If watches are active, CTK explains that watching continues and asks you to stop them before restarting. A watch operation already in progress can also delay installation. Clicking repeatedly does not make a safe restart possible.

Review your connected repositories on Home and wait for pending start or stop operations to settle. The message is a guard around installation, not confirmation that the updater has already restarted the app.

03

3. Choose how to pause each workload

For Already running, Docker Compose, SSH and Kubernetes, Stop watching stops CTK collection rather than the externally managed workload. Their processes or containers continue under your existing tools.

Start with Toolkit is different: CTK launched that start script, and stopping its watch stops the launched process. Plan the interruption or move the workload into your usual external process management before an update when uninterrupted service matters.

04

4. Restart explicitly when ready

After stopping the active watches and allowing pending operations to finish, choose Restart to update again. The app closes to install the downloaded version and then opens again.

Your connected repositories, preferences and local history are intended to remain available. That persistence does not imply continuous monitoring while the application was closed, and old snapshots should still be read with their timestamps.

05

5. Verify the installed version and fresh collection

Open About to check the installed version. Return to Home, inspect the required repositories and start any watch that is not active. Confirm a fresh successful reading for the correct service instead of relying on the old snapshot.

If an update download fails, use Retry update when available. CTK reports the failure while existing watches remain independent of the failed download. A broken connector after reopening needs its own access check; it is not automatically an update installation failure.

06

What success looks like

The new version is installed, your existing workspace and history remain visible, and every watch you need has a fresh post-update observation. You understand and account for the period when CTK was not collecting.