Delete the quickstart Agent
Human verified
A human reviewed this page, but it may be out of date. Later edits may not have been reviewed.
Use the saved operator session from Deploy your first Agent. These steps are identical on local k3d, Kubernetes and Amazon EKS. They delete the selected Agent's execution, workspace and version history; the installation remains available.
source /path/to/private/run/session.shrequest DELETE "$base/agents/$agent"The API accepts deletion with HTTP 202 and an Agent in deleting state. Repeat this read until it prints 404:
request_status GET "$base/agents/$agent"HTTP 200 means the Agent still exists; inspect it with request GET "$base/agents/$agent". Authentication errors and transport failures do not confirm deletion. For failed deletion, use Agent deletion recovery. If DELETE times out, read the Agent before retrying.
You do not need to stop the Agent separately, withdraw repository approvals, or wait for Git credential retirement before deleting it. Immediate installation teardown can leave issued GitHub tokens valid until expiry because its worker can no longer revoke them. Deletion does not revoke the service-account PAT.
Clean up the installation
After the Agent is gone, use the cleanup page for the platform already recorded in the session:
case "$PLATFORM" in local-k3d) printf '%s\n' '/guides/deploy/local-cleanup/' ;; kubernetes) printf '%s\n' '/guides/deploy/kubernetes-cleanup/' ;; eks) printf '%s\n' '/guides/deploy/eks-cleanup/' ;; *) printf 'Unknown session platform: %s\n' "$PLATFORM" >&2; exit 1 ;;esac