Clean up the local Installation
Human verified
A human reviewed this page, but it may be out of date. Later edits may not have been reviewed.
Delete the Agent, then remove the disposable Installation when you finish the local quickstart. Use the saved operator session from installation setup. Removing the Installation deletes its k3d cluster, database and generated Kubernetes credentials.
Immediate teardown can leave previously issued GitHub tokens valid until they expire because the worker can no longer revoke them. Deleting the Installation does not revoke the service-account PAT.
Delete the Agent
Complete Delete Agent first. It uses the saved session and waits for HTTP 404; it does not require Git credential retirement.
Remove the Installation
After Agent deletion finishes, remove the disposable Installation from the same shell.
Use the launcher’s printed cleanup command. For the OpenShell profile, the equivalent below requires the saved state directory and the cluster name from its installation record. Run it from the matching release checkout, using the CLI that created the installation.
source /path/to/private/run/session.shCLEANUP_STATE=${OCC_DEVELOPMENT_STATE_DIRECTORY:?}CLEANUP_CLUSTER=$(jq -er .cluster "$CLEANUP_STATE/state.json"): "${CLEANUP_STATE:?Set the saved state directory}" "${CLEANUP_CLUSTER:?Set the recorded cluster name}"( set -euo pipefail # Check both records before deleting. A mismatch stops this block before dev down. test "$(jq -er .cluster "$CLEANUP_STATE/state.json")" = "$CLEANUP_CLUSTER" test "$(kubectl --kubeconfig "$CLEANUP_STATE/kubeconfig" config current-context)" = "k3d-$CLEANUP_CLUSTER" printf 'Removing selected installation %s (%s)\n' "$CLEANUP_CLUSTER" "$CLEANUP_STATE" env OCC_DEVELOPMENT_STATE_DIRECTORY="$CLEANUP_STATE" OCC_DEVELOPMENT_COMPUTE_DRIVER=kubernetes \ OCC_DEVELOPMENT_SANDBOX_DRIVER=openshell ./bin/occ dev down test ! -e "$CLEANUP_STATE")Expect Stopped Kubernetes development stack <cluster>. On failure, use the retained state and cleanup guidance. Remove only private token or header copies owned by the retired run. For a fresh install, use a new RUN_DIR and let the launcher create a new state directory.
Next steps
- Deploy on Kubernetes for an existing cluster.
- Browse Reference for CLI commands, API operations, permissions and configuration.
- Browse the product guides for Agent management and observability.