Behavior of GitHub Copilot When the Completions Feature Is Disabled (4382574)

A user reported that after disabling the Completions feature in GitHub Copilot settings within Toad, they were no longer able to receive any Copilot code suggestions. They attempted to manually trigger Copilot using the dash (-) prompt in the editor but did not receive any generated output. The user requested clarification on whether this behavior is expected and whether Copilot may still be invoked manually with completions disabled.

Per the development team, the term “completion” refers to the exact mechanism Copilot uses to generate ghost‑text suggestions in the editor. Therefore:

• Copilot’s suggestions are completions.
• Disabling completions directly disables Copilot entirely.

The manual dash (-) prompt uses the same completion engine.
When completions are turned off, the Copilot engine no longer responds to manual prompts or inline triggers.

Toad’s built‑in assist features are separate and not dependent on Copilot:

• Code Insight
• Parameter Assistance

These remain functional regardless of Copilot settings.

This behavior is expected.

• Disabling Completions disables all GitHub Copilot functionality in Toad, including:

  • Inline ghost‑text suggestions
  • Automatic code suggestions
  • Manual Copilot invocation (e.g., dash - prompt)

• Copilot cannot be used in any capacity unless Completions remain enabled.

• Toad’s native coding assist features will continue to function normally even while Copilot is disabled.

If the user wants to continue receiving Copilot‑generated code, the Completions setting must remain enabled.