T3 Code
Built on Electron, T3 Code stores several layers of reusable browser-engine data on disk so its interface, embedded web content, and GPU-accelerated rendering start faster on later launches. Those files include HTTP disk cache entries in Cache_Data, V8 compiled JavaScript bytecode in Code Cache, Chromium GPUCache data, DawnGraphiteCache and DawnWebGPUCache shader and pipeline blobs, plus Shared Dictionary compression caches used for web responses. Kudu removes only those disposable caches when they become oversized or stale, while leaving T3 Code workspaces, sessions, settings, and account data untouched.
Why clean T3 Code?
- Stale V8 bytecode in Code Cache after a T3 Code or embedded web app update can force recompilation and cause an unusually slow first launch or delayed panel loading
- Corrupted Cache_Data entries can leave parts of the UI stuck on old assets, producing missing icons, broken styling, or pages that refuse to refresh correctly
- Chromium GPUCache data invalidated by a graphics driver update can trigger black panels, flickering text, or a sluggish redraw until the cache is rebuilt
- Outdated DawnGraphiteCache and DawnWebGPUCache shader blobs can cause stutter when opening GPU-accelerated views or make rendering fall back unexpectedly after a browser engine change
- An oversized Shared Dictionary cache can waste hundreds of megabytes on old compressed response dictionaries while offering no benefit for content T3 Code no longer requests
- Conflicting cached web resources from sign-in flows or extension-like embedded content can produce repeated loading spinners, partial blank screens, or assets that only recover after cache removal
Cache paths Kudu targets
Windows
%AppData%/t3code/Cache/Cache_Data |
%AppData%/t3code/Code Cache |
%AppData%/t3code/GPUCache |
%AppData%/t3code/DawnGraphiteCache |
%AppData%/t3code/DawnWebGPUCache |
%AppData%/t3code/Shared Dictionary/cache |
Common questions about T3 Code
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.