Answer: The SDK-managed out-of-process runtime writes redacted process--.log files under the Copilot home's logs directory by default in copilot-cli mode. A custom log location can be specified with --log-dir. Status: Confirmed Entry: tool/github-copilot/troubleshooting/debug-log-directory Revision: 2 Digest: sha256:93f7ae1890285734 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:29:22Z Last changed: 2026-11-17T13:28:19Z (custom log location option: — → --log-dir) Last verified: 2026-11-20T13:09:53Z Next check: 2026-11-21T13:09:53Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of default log directory | Copilot home's logs directory | [1] | 2026-11-20 log file name pattern | process--.log | [1] | 2026-11-20 custom log location option | --log-dir | [1] | 2026-11-20 Sources: [1] GitHub. "Debugging guide - GitHub Docs". https://docs.github.com/en/copilot/how-tos/copilot-sdk/troubleshooting/debugging Role: primary. Accessed: 2026-11-20T13:09:53Z Quote: "writes redacted process--.log files under the Copilot home's logs directory by default in copilot-cli mode" (Supports: default log directory) Quote: "writes redacted process--.log files" (Supports: log file name pattern) Quote: "You can specify a custom log location with --log-dir" (Supports: custom log location option) Snapshot SHA-256: fd5ea1683b0ee84103cf7cd9b1f2c106b20fcc799ffef476cd31eb1852230944 (captured 2026-11-18T13:05:16Z) 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-18T13:05:16Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:09:53Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:09:53Z Last attempt: 2026-11-20T13:09:53Z Notes and limitations: Extracted automatically from a single official source (section "Log directory"). Related: 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/diagnose-ci-failures-pass-locally How can GitHub Copilot help me diagnose CI test failures that pass locally but fail in CI? https://latestn.com/tool/github-copilot/troubleshooting/diagnose-ci-test-failures How do I diagnose CI test failures using GitHub Copilot? 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/github-copilot/troubleshooting/debug-hooks-troubleshooting How do I debug and troubleshoot GitHub Copilot cloud agent hooks that aren't working? 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/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T13:28:19Z | changed | custom log location option: — → --log-dir | [1] 2026-11-17T13:28:19Z | changed | log file name pattern: — → process--.log | [1] 2026-11-17T13:28:19Z | changed | default log directory: — → Copilot home's logs directory | [1] 2026-11-17T13:28:19Z | changed | Custom log location option: --log-dir → — | [1] 2026-11-17T13:28:19Z | changed | Log file name pattern: process--.log → — | [1] 2026-11-17T13:28:19Z | changed | Default log directory: Copilot home's logs directory → — | [1] 2026-11-13T03:29:22Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/github-copilot/troubleshooting/debug-log-directory/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-log-directory POST: https://latestn.com/dispute/tool/github-copilot/troubleshooting/debug-log-directory with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/github-copilot/troubleshooting/debug-log-directory?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Where does the GitHub Copilot SDK write its debug log files? Revision 2, last verified 2026-11-20T13:09:53Z. https://latestn.com/tool/github-copilot/troubleshooting/debug-log-directory (accessed 2026-11-21T09:52:35Z). @misc{LatestN_tool_github_copilot_troubleshooting_debug_log_directory_r2, title = {Where does the GitHub Copilot SDK write its debug log files?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/github-copilot/troubleshooting/debug-log-directory}}, note = {Revision 2; digest sha256:93f7ae1890285734; last verified 2026-11-20T13:09:53Z; accessed 2026-11-21T09:52:35Z} } 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-log-directory