Apps
T3 Code Logs
T3 Code writes diagnostic log files under its userdata directory to record startup events, extension host activity, renderer and window errors, update checks, crash details, and other troubleshooting output. These rotating text logs accumulate as sessions, background processes, and repeated warnings generate more entries over time, especially after extension failures or noisy integrations. Kudu removes only T3 Code log files older than one week from ~/.t3/userdata/logs, without scanning attachments, secrets, runtime state, settings, accounts, or project files.
Why clean T3 Code Logs?
- Repeated extension host crashes or reconnect loops can flood the logs directory with per-session text files, and the visible symptom is T3 Code using far more disk space than expected even when your projects are small
- Renderer, update, and IPC warnings that repeat on every launch create weeks of stale diagnostics, so users often notice the logs folder growing continuously after a bug has already been fixed
- Large numbers of old log files make it harder to find the current session when troubleshooting, and the practical symptom is searching through outdated timestamps instead of the error you just reproduced
- Background tasks that restart frequently can leave behind many short-lived session logs, which shows up as a crowded userdata folder and slower manual inspection in Explorer
- After an extension or app update, old logs preserve obsolete stack traces and deprecation noise, leading users to chase errors that no longer apply while current behavior is otherwise normal
- On systems with limited SSD space, accumulated diagnostic history from months of launches can consume hundreds of megabytes or more, and the user notices low free space warnings rather than any benefit from keeping the old files
What gets cleaned
Cache paths Kudu targets
Windows
~/.t3/userdata/logs |
Frequently asked
Common questions about T3 Code 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.