Copilot Send button disabled: check the setting
If Copilot accepts text but the Send button does nothing, check whether chat.useCustomizationsInParentRepositories is enabled. Turning it off restored sending in a specific VS Code user report. Treat that as a targeted workaround, not a fix for every disabled button; if it does not match, check access and collect diagnostics rather than repeatedly clicking Send.
Updated and sources checked: October 9, 2026.
Check whether the symptom matches the report
The March 21, 2026 report names VS Code 1.112.0, GitHub Copilot Chat 0.40.0 and Windows 10. Text entry worked, but clicking Send produced no response, spinner or visible error. The workspace had many customization files in parent repositories. See VS Code inert Send button report 303727.
The reporter found that setting chat.useCustomizationsInParentRepositories to false restored sending immediately. This is a user-reported result, not a guarantee for other versions or causes. A closed issue alone does not establish that the installed release contains a fix.
Understand what the setting changes
chat.useCustomizationsInParentRepositories controls discovery of instructions, prompts, agents, skills and hooks in parent repositories. Its documented default is false. Disabling it changes that discovery scope, so parent customizations may no longer be available. See VS Code AI settings reference.
Test the setting in the affected workspace
Open the Command Palette with Ctrl+Shift+P on Windows or Linux, or Cmd+Shift+P on macOS. Run Preferences: Open Workspace Settings (JSON). Workspace settings apply to this project and override user settings; a single-folder workspace stores them in .vscode/settings.json. See VS Code user and workspace settings guide.
For the reported workaround, add or update the following entry inside the existing JSON object. Preserve other settings and record the previous value. Retry a small prompt; if this does not help, restore that value instead of broadening the change.
"chat.useCustomizationsInParentRepositories": falseCheck access and capture an unresolved failure
Run Code: Check for Updates. Confirm the signed-in GitHub account has Copilot access, and inspect the Copilot status dashboard in the Status Bar for an allowance or temporary rate limit. Reproduce in a new chat with the same prompt, model and tools. See VS Code AI troubleshooting guide.
For customization discovery, open the Chat view context menu > Diagnostics. For connection failures, run GitHub Copilot: Chat Diagnostics from the Command Palette.
For logs, run Developer: Set Log Level, set GitHub Copilot and GitHub Copilot Chat to Trace, reproduce, then run Output: Show Output Channels and choose either extension. Restore the previous log levels afterwards. Redact credentials, prompts and source code before sharing.
Report the reproduction, not an assumed cause
Check the existing Copilot issue tracker for a matching report. Include the editor and extension versions, the setting value before and after the test, whether text entry still works, and the relevant diagnostic output. Do not describe a parent-customization bug unless the comparison actually reproduces it. See GitHub Copilot extension issue tracker.