# ISC Commands (CLI) Users can access the ISC API from within their development container which includes the following commands. * `isc ping` can be used to confirm that the User is properly authenticated with the ISC. * `isc experiments` can be used to print a report to the terminal of the User's historic and current experiments. * `isc train ///.isc` can be used to launch experiments to train on the ISC. * `isc cancel ` can be used to cancel an [active experiment](/basic-concepts/launching-experiments.md#experiment-tracking). Any member of an Organisation can cancel any experiment launched by any other member of the Organisation if the designated Project for that experiment belongs to that Organisation. * `isc container restart` can be used to commit your latest changes to your container image and restart the container. This is often necessary prior to [launching experiments](/basic-concepts/launching-experiments.md) with `compute_mode="cycle"` in order to keep the commit time less than 2 minutes. Restarting the container is faster than stopping and then starting the container and results in fewer data movement charges. * `isc container stop` can be used to commit your latest changes to your container image and stop the container. * `--sqaush` or `-s` is an optional additional argument to `isc container restart` or `isc container stop` which will cause your container image to perform a squash during the restart or stop. This can be helpful for reducing the total size of the container image layers and reduce data movement charges. Squashing can take several minutes longer than just restarting or stopping. * `--no-save` is an optional additional argument to `isc container restart` or `isc container stop` which will block the ISC from backing up your container to the cloud as part of this action. Backing up to the cloud is the default behaviour, but restarting or stopping containers without backing up to the cloud is faster. * If the user calls for `isc container restart --no-save` then the container is restarted - committing latest changes to the container image on the cluster - without backing up the container to the cloud, but all changes made within the container since last start are preserved. * If the user calls for `isc container stop --no-save` then the container is stopped without backing up the container to the cloud. All changes made within the container since last start will be lost. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.strongcompute.com/basic-concepts/isc-commands-cli.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.