Introduction

APT-style yes or no prompts are popular because users already understand the convention. A suffix like [Y/n] communicates both the accepted answers and the default action when the user simply presses Enter. If you want that behavior in your own CLI, the important parts are prompt format, safe defaults, and a non-interactive escape hatch for scripts.

Reproduce the Familiar Prompt Behavior

The usual terminal conventions are simple:

• '[Y/n] means yes is the default'
• '[y/N] means no is the default'
• Enter accepts the default
• invalid input triggers another prompt

That small amount of structure gives users a lot of confidence because they can predict exactly what the program will do.

A Minimal Python Implementation

The core logic is just a loop around input.

1def confirm(prompt: str, default: bool = False) -> bool:
2    suffix = " [Y/n] " if default else " [y/N] "
3
4    while True:
5        answer = input(prompt + suffix).strip().lower()
6
7        if answer == "":
8            return default
9        if answer in ("y", "yes"):
10            return True
11        if answer in ("n", "no"):
12            return False
13
14        print("Please answer yes or no.")
15
16
17if confirm("Proceed with installation?", default=True):
18    print("Continuing")
19else:
20    print("Cancelled")

This is enough to mimic the behavior users expect from tools such as APT: explicit defaults, retry on bad input, and short accepted answers.

A Bash Version for Shell Scripts

The same pattern works in shell scripts if you return status code 0 for yes and 1 for no.

1confirm() {
2  local prompt="$1"
3  local default_yes="$2"
4  local reply
5
6  while true; do
7    if [ "$default_yes" = "yes" ]; then
8      printf "%s [Y/n] " "$prompt"
9    else
10      printf "%s [y/N] " "$prompt"
11    fi
12
13    read -r reply
14    reply=$(printf "%s" "$reply" | tr '[:upper:]' '[:lower:]')
15
16    if [ -z "$reply" ]; then
17      [ "$default_yes" = "yes" ] && return 0 || return 1
18    fi
19
20    case "$reply" in
21      y|yes) return 0 ;;
22      n|no) return 1 ;;
23      *) echo "Please answer yes or no." ;;
24    esac
25  done
26}

This integrates naturally with shell conditionals:

if confirm "Remove cached packages?" "no"; then
  echo "Cleaning"
fi

Design the Prompt Around Safety

The real question is not only how to parse input. It is whether the default should be yes or no.

Use default yes when the action is expected and low-risk, such as confirming an install the user explicitly requested. Use default no when the action is destructive, expensive, or difficult to undo.

The prompt text should also state the effect clearly. Continue? is vague. Install 8 packages and use 140 MB of disk space? is much better because the user knows what they are approving.

Support Non-Interactive Use

APT-style prompts are good for humans but bad for automation unless you provide an override such as --yes. That matters in CI, remote execution, containers, and batch jobs where stdin may not be interactive.

1import argparse
2import sys
3
4parser = argparse.ArgumentParser()
5parser.add_argument("--yes", action="store_true")
6args = parser.parse_args()
7
8if not sys.stdin.isatty() and not args.yes:
9    raise RuntimeError("Confirmation required; rerun with --yes in non-interactive mode")

This prevents the program from hanging forever waiting for input that will never come.

Common Pitfalls

The biggest mistake is choosing an unsafe default. A [Y/n] prompt for data deletion or destructive system changes trains users to confirm dangerous actions too easily.

Another issue is accepting ambiguous input. It is better to reject unexpected values and reprompt than to guess what ok, sure, or random whitespace should mean.

Blocking on stdin in automation is another common failure mode. A friendly prompt in a terminal becomes a broken deployment step if there is no --yes or similar non-interactive path.

Finally, do not treat confirmation as a substitute for clear command design. If an action is dangerous, the command syntax, help text, and prompt wording should all reinforce that fact.

Summary

• APT-style prompts rely on clear suffixes such as [Y/n] and [y/N].
• Pressing Enter should select the default answer explicitly shown in the prompt.
• Validate input strictly and reprompt on invalid answers.
• Pair interactive prompts with a non-interactive override such as --yes.
• Choose defaults based on actual operational risk, not just convenience.