Configuring Default Editor and Execution Confirmation in GitHub Copilot CLI

GH-300 By islever Editorial Last updated

Use GitHub Copilot CLI Manage privacy settings and exclusions

Short answer

BC GitHub Copilot in the CLI allows configuration of the default editor and the default execution confirmation settings.

Question

GitHub Copilot in the Command Line Interface (CLI) can be used to configure the following settings: Each correct answer presents part of the solution. (Choose two.)
  1. Usage analytics
  2. The default editor Correct Answer
  3. The default execution confirmation Correct Answer
  4. GitHub CLI subcommands

Key Takeaways

The question tests knowledge of local CLI configuration options versus global account settings, specifically highlighting execution confirmation and editor selection.

Learn how to configure the default editor and execution confirmation settings in GitHub Copilot CLI using the gh copilot config command.

Common mistake: Candidates often confuse usage analytics (an account-level setting) with local CLI configuration options like execution confirmation.

Expert Analysis

Execution Confirmation is a Core Copilot CLI Setting

GitHub Copilot in the CLI (gh copilot) provides specific configuration commands to control how generated shell commands are handled. A critical safety feature is execution confirmation. Users can configure whether the CLI requires explicit approval before executing suggested commands (Option C). This setting is directly managed via gh copilot config and is central to the tool's operation, ensuring developers review AI-generated actions.

Default Editor Configuration

Another key configurable parameter is the default editor (Option B). When Copilot CLI generates suggestions that require editing or reviewing content (such as commit messages or file changes), it needs to know which text editor to launch. This is configured through the same settings interface, allowing users to specify their preferred editor environment.

Why Other Options Are Incorrect

Usage analytics (Option A) are typically managed at the GitHub account or organization level, not within the local gh copilot configuration scope. While related to privacy, they are not set via the CLI's interactive config command for execution behavior. Similarly, GitHub CLI subcommands (Option D) are part of the parent gh tool's architecture and are not "configured" by Copilot; they are inherent to the CLI itself.

Operational Consequence

Misidentifying these settings can lead to confusion between local IDE/CLI preferences and global account policies. Getting this wrong might cause a candidate to overlook critical security controls like execution confirmation, which is vital for safe AI-assisted development.

Exam Strategy

When answering questions about GitHub Copilot CLI configuration, distinguish between local user preferences (like editors and confirmations) and global account policies (like analytics). Focus on commands accessible via gh copilot config.

Frequently Asked Questions

How do I configure execution confirmation in GitHub Copilot CLI?

You can configure execution confirmation using the gh copilot config command, which allows you to choose whether to require approval before executing suggested commands.

Is usage analytics configured in the GitHub Copilot CLI?

No, usage analytics are typically managed at the GitHub account or organization level, not through the local gh copilot CLI configuration.

More GH-300 FAQ →

Community Votes

C
50%
A
25%
B
25%

50% of anonymous learners picked answer C. Votes are pick records left by other test-takers — they are not the verified answer.

Discussion 12 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 12

  1. omath 👍 2
    The correct answers are: B. The default editor ✅ C. The default execution confirmation ✅ Explanation: B. Default editor → In the GitHub Copilot CLI, you can configure which editor opens when reviewing or editing suggestions. C. Default execution confirmation → You can set whether Copilot suggestions should be executed immediately or require confirmation first.
  2. cayenne06 👍 2
    A. Usage analytics C. The default execution confirmation GitHub Copilot in the CLI lets you configure optional usage analytics and the default confirmation behavior before executing suggested commands.
  3. Acrious 👍 2
    B and C, you don't configure usage this way and subcommands is just a silly way to trick you.
  4. 7036da3 👍 2
    A and C
  5. SibuAbraham 👍 1
    The correct options are A. Usage analytics and C. The default execution confirmation. Running the configuration command (gh copilot config) within the GitHub Copilot CLI allows you to manage the following settings: • Usage analytics: You can choose to opt-in or opt-out of sharing usage analytics to help improve the tool. • The default execution confirmation: You can configure whether the CLI requires a confirmation prompt before executing a suggested command or if it should run it immediately.
Show 7 more comments
  1. majora15 👍 1
    GitHub Copilot in the CLI provides configuration options for how it interacts with you and executes commands: B. The default editor — Correct. You can configure which editor Copilot CLI uses when you need to edit or review generated content. C. The default execution confirmation — Correct. You can configure how Copilot handles confirmation before executing suggested shell commands.
  2. NikhilG 👍 1
    correct options A and C [Answered by copilot] A. Usage analytics You can enable or disable the collection of usage analytics. C. The default execution confirmation You can configure whether GitHub Copilot in the CLI asks for confirmation before executing a suggested command. The default editor and GitHub CLI subcommands are not configured through these Copilot CLI settings.
  3. TFOTHYL 👍 1
    B. The default editor C. The default execution confirmation GitHub Copilot CLI supports configuration of user preferences, including the default editor used for editing content and settings related to execution confirmations/approvals for commands and tools. GitHub's CLI configuration documentation describes settings for editor behavior and command approval workflows.
  4. dario_airoldi 👍 1
    A. Usage analytics — correct: gh copilot config C. The default execution confirmation B. The default editor — incorrect: This is a setting of the parent GitHub CLI (not gh copilot cli)
  5. 395d135 👍 1
    Usage analytics are managed at the GitHub account or organization level — not configured via Copilot CLI settings.
  6. 4729 👍 1
    B has nothing to do with copilot its cli native
  7. barbacromata 👍 1
    copilot say

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Troubleshooting GitHub Copilot Code Suggestions Failures

S-grade

GitHub Copilot Plan for Azure DevOps Without Enterprise License

S-grade

Improving GitHub Copilot Prompts with Success Criteria and Source Context

A-grade

Understanding Role Prompting in GitHub Copilot

A-grade

← Back to GH-300 Study Guide