Example:

An engineering team using multiple GKE clusters may reasonably have these desires:

1. Common tooling used across the team which needs to rely on predictable cluster naming conventions, eg: gke_project_zone_cluster-01
2. Ability to reference these clusters by friendlier shorternames such as cluster-01, cluster-02, and so on.

Currently kubectx supports renaming clusters which would address #2. However, renaming clusters would break use case #1.

Providing an easy mechanism for copying contexts would allow for a straightforward way for the team to address both desires. By not renaming and keeping the full GKE name the team can distribute common tooling that relies on the full context name. And copying to a friendlier name makes it easier for the team to operate against multiple clusters, eg: kubectl get pods --context cluster-01 or kubectx cluster-01

Implementing "copy" functionality would satisfy both desires.