You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows, opencode/OpenCode created or left a very large number of files under %LOCALAPPDATA%\Temp\opencode. This caused Windows User Profile Service (ProfSvc) to spend ~30 seconds during post-PIN logon scanning the user temp tree before the desktop appeared.
After cleaning %LOCALAPPDATA%\Temp\opencode, the same logon phase dropped from ~30 seconds to ~5 seconds.
Impact
This is not just disk usage. On Windows, a large temp tree can directly affect interactive logon time because ProfSvc scans the user temp directory during profile load.
Windows Event Log showed the delay in the Microsoft-Windows-User Profile Service/Operational log for the affected user profile. A separate clean test profile logged in immediately.
A dump of the ProfSvc svchost process during the delay showed it inside the temp-tree scan path:
This matches the observed behavior: once the temp tree was cleaned, the delay disappeared.
Environment
OS: Windows
OpenCode desktop: 1.14.40
Older OpenCode install metadata also present: 1.14.33
Temp path: %LOCALAPPDATA%\Temp\opencode
Expected Behavior
opencode should not leave unbounded temporary artifacts under %LOCALAPPDATA%\Temp\opencode.
Possible mitigations:
Clean old temp/session artifacts on startup or shutdown.
Use bounded cache retention by age and/or size.
Store durable cache under %LOCALAPPDATA%\OpenCode instead of %TEMP%.
Avoid creating very high file counts in Windows temp directories.
Provide a documented cleanup command.
Actual Behavior
The temp directory grew to 150k+ items within a relatively short install window and caused a reproducible Windows post-PIN logon delay.
Request
Please add automatic cleanup/retention for %LOCALAPPDATA%\Temp\opencode on Windows, or move non-temporary cache artifacts to a bounded cache directory.
Activity
github-actions commentedon May 12, 2026
This issue might be a duplicate of existing issues. Please check:
If the root cause is the same, it may be worth referencing or continuing the discussion there.
github-actions commentedon Jul 12, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.