Answer: To troubleshoot hooks that aren't executing, verify the JSON file is in the .github/hooks/ directory, check for valid JSON syntax, ensure version: 1 is specified, verify the script is executable, and check that it has a proper shebang. For timeouts, the default timeout is 30 seconds and you can increase timeoutSec in the configuration. Status: Confirmed Entry: tool/github-copilot/troubleshooting/debug-hooks-troubleshooting Revision: 3 Digest: sha256:8f75144b908b1872 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:26:53Z Last changed: 2026-11-20T13:06:39Z (compact JSON on Unix: jq -c → —) Last verified: 2026-11-20T13:06:39Z Next check: 2026-11-21T13:06:39Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Unit | Source | As of default timeout | 30 seconds | seconds | [1] | 2026-11-20 required version | version: 1 | | [1] | 2026-11-20 hooks directory | .github/hooks/ | | [1] | 2026-11-20 timeout setting | timeoutSec | | [1] | 2026-11-20 executable check | chmod +x script.sh | | [1] | 2026-11-20 shebang example | #!/bin/bash | | [1] | 2026-11-20 JSON syntax check | jq . hooks.json | | [1] | 2026-11-20 Sources: [1] GitHub. "Customize agent workflows with hooks - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/use-hooks Role: primary. Accessed: 2026-11-20T13:06:39Z Quote: "The default timeout is 30 seconds." (Supports: default timeout) Quote: "Ensure version: 1 is specified in your hooks.json file." (Supports: required version) Quote: "Verify the JSON file is in the .github/hooks/ directory." (Supports: hooks directory) Quote: "Increase timeoutSec in the configuration if needed." (Supports: timeout setting) Quote: "Verify the script you are calling from your hook is executable ( chmod +x script.sh )" (Supports: executable check) Quote: "Check that the script has a proper shebang (for example, #!/bin/bash )" (Supports: shebang example) Quote: "Check for valid JSON syntax (for example, jq . hooks.json )." (Supports: JSON syntax check) Snapshot SHA-256: 8d6f7acc0542449e17e91c3ce859837f22db667445657a8f7ad26fa2357d99cc (captured 2026-11-19T13:00:19Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T13:00:20Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:06:39Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:06:39Z Last attempt: 2026-11-20T13:06:39Z Notes and limitations: Extracted automatically from a single official source (section "Troubleshooting"). Related: https://latestn.com/tool/github-copilot/troubleshooting/debug-invalid-json-prompt How do I use GitHub Copilot to debug invalid JSON? https://latestn.com/tool/github-copilot/troubleshooting/debug-log-directory Where does the GitHub Copilot SDK write its debug log files? https://latestn.com/tool/github-copilot/troubleshooting/developers-cannot-access-copilot-cli Why can't my developers access GitHub Copilot CLI? https://latestn.com/tool/github-copilot/troubleshooting/copilot-missing-from-assignees Why is GitHub Copilot not appearing in the Assignees list on my issue? https://latestn.com/tool/github-copilot/troubleshooting/copilot-not-responding-to-pr-comments Why is GitHub Copilot not responding to my pull request comments? https://latestn.com/tool/github-copilot/troubleshooting/copilot-not-working-in-some-files Why is GitHub Copilot not working in some files? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T13:06:39Z | changed | compact JSON on Unix: jq -c → — | [1] 2026-11-17T13:24:03Z | changed | compact JSON on Unix: — → jq -c | [1] 2026-11-13T03:26:53Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/troubleshooting/debug-hooks-troubleshooting/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/github-copilot/troubleshooting/debug-hooks-troubleshooting POST: https://latestn.com/dispute/tool/github-copilot/troubleshooting/debug-hooks-troubleshooting with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/troubleshooting/debug-hooks-troubleshooting?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I debug and troubleshoot GitHub Copilot cloud agent hooks that aren't working? Revision 3, last verified 2026-11-20T13:06:39Z. https://latestn.com/tool/github-copilot/troubleshooting/debug-hooks-troubleshooting (accessed 2026-11-21T09:53:36Z). @misc{LatestN_tool_github_copilot_troubleshooting_debug_hooks_troubleshooting_r3, title = {How do I debug and troubleshoot GitHub Copilot cloud agent hooks that aren't working?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/troubleshooting/debug-hooks-troubleshooting}}, note = {Revision 3; digest sha256:8f75144b908b1872; last verified 2026-11-20T13:06:39Z; accessed 2026-11-21T09:53:36Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/github-copilot/troubleshooting/debug-hooks-troubleshooting