Apps
GitHub Copilot Logs
GitHub Copilot stores diagnostic and telemetry-style extension logs under ~/.copilot/logs to record authentication handshakes, language server activity, request timing, chat panel events, completion pipeline errors, and model response failures. These plain-text log files accumulate during normal use so the extension can help troubleshoot sign-in problems, missing suggestions, and chat issues across IDE sessions. Kudu removes only GitHub Copilot log files older than one week, leaving chat sessions, edit sessions, credentials, and IDE data untouched.
Why clean GitHub Copilot Logs?
- Verbose extension logging from repeated completion requests and chat interactions can pile up into hundreds of megabytes, showing up as unexpected disk usage in your user profile
- Old authentication and network error logs keep records of transient sign-in failures long after the issue is fixed, making current troubleshooting harder because recent errors are buried in stale entries
- Language server and completion pipeline logs from older extension builds can preserve obsolete stack traces and warning patterns, so users reviewing logs may chase problems that no longer exist after an update
- Large multi-day log sets make manual inspection slower in editors and support bundles, with symptoms like sluggish searches, long file open times, and difficulty finding the newest failure event
- Repeated reconnect, timeout, and proxy-related log spam can grow quickly on unstable networks, causing the logs folder to expand far beyond what most users expect from an IDE assistant
- When Copilot features briefly fail and then recover, outdated diagnostic logs can create confusion by mixing resolved chat or completion errors with active ones, leading users to misread the current state of the extension
What gets cleaned
Cache paths Kudu targets
Windows
~/.copilot/logs |
Frequently asked
Common questions about GitHub Copilot Logs
Related cleaners
Free & open source
Download Kudu and reclaim your disk space.
Available on Windows, macOS, and Linux. No account required, no feature gates, no telemetry without consent. All cleaning targets are open source and community-auditable.