ahmetb/kubectx · error

'-d' needs arguments

Error message

'-d' needs arguments

What it means

Argument-validation error from parseArgs: the -d (delete) flag was passed with no context name while stdout is not interactive, so neither a target nor the fzf picker is available. -d requires at least one NAME argument (or an interactive terminal).

Source

Thrown at cmd/kubectx/flags.go:74

	if argv[0] == "--shell" || argv[0] == "-s" {
		if len(argv) == 1 {
			if cmdutil.IsInteractiveMode(os.Stdout) {
				return InteractiveShellOp{}
			}
			return UnsupportedOp{Err: fmt.Errorf("'%s' requires a context name argument (or fzf for interactive mode)", argv[0])}
		}
		if len(argv) == 2 {
			return ShellOp{Target: argv[1]}
		}
		return UnsupportedOp{Err: fmt.Errorf("'%s' accepts at most one context name argument", argv[0])}
	}

	if argv[0] == "-d" {
		if len(argv) == 1 {
			if cmdutil.IsInteractiveMode(os.Stdout) {
				return InteractiveDeleteOp{}
			} else {
				return UnsupportedOp{Err: fmt.Errorf("'-d' needs arguments")}
			}
		}
		return DeleteOp{Contexts: argv[1:]}
	}

	if len(argv) == 1 {
		v := argv[0]
		if v == "--help" || v == "-h" {
			return HelpOp{}
		}
		if v == "--version" || v == "-V" {
			return VersionOp{}
		}
		if v == "--current" || v == "-c" {
			return CurrentOp{}
		}
		if v == "--unset" || v == "-u" {
			return UnsetOp{}

View on GitHub (pinned to 12ad6fb22e)

Solutions

1. Delete explicitly: `kubectx -d <NAME> [<NAME>...]`
2. Use '.' to delete the current context
3. Run in an interactive terminal to get the fzf delete picker

When it happens

Trigger: Thrown at cmd/kubectx/flags.go:74 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of ahmetb/kubectx@12ad6fb22e (2026-09-02). Data as JSON: /api/errors/6d9c3b5e229ad3ee. Report an issue: GitHub.