On Windows 10 without Developer Mode, the OpenCode runtime fails to create a symlink from shared-cache/config-node_modules to the profile's node_modules directory. The EPERM error blocks the entire OpenCode provider catalog, leaving it unavailable. Changes: - New openCodeWindowsNodeModulesJunction module that pre-creates a Windows directory junction (no Developer Mode required) before the runtime call when an EPERM symlink error is detected - On Windows, loadView and loadProviderDirectory now detect EPERM symlink errors, extract the profile ID, create the junction, and retry the runtime command once before falling back to the error response - Updated diagnostic hints to accurately reflect that the runtime does not yet include junction fallback, and that the next runtime update will include it - Added unit tests for the junction module and retry behavior |
||
|---|---|---|
| .. | ||
| agent-graph | ||
| features | ||
| fixtures | ||
| main | ||
| mocks | ||
| preload | ||
| renderer | ||
| scripts | ||
| shared | ||
| setup.ts | ||