cf98e74c11
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-attachments | ||
| agent-graph | ||
| anthropic-runtime-profile | ||
| codex-account | ||
| codex-model-catalog | ||
| codex-runtime-installer | ||
| codex-runtime-profile | ||
| localization | ||
| member-log-stream | ||
| member-work-sync | ||
| recent-projects | ||
| running-teams | ||
| runtime-provider-management | ||
| team-runtime-lanes | ||
| tmux-installer | ||
| workspace-trust | ||
| CLAUDE.md | ||
| README.md | ||
Features
This directory contains the canonical home for medium and large feature slices.
Before creating or refactoring a feature, read:
Reference examples:
recent-projects- full cross-process feature with contracts, core, main, preload, renderer, and focused testsagent-graph- thin feature withcore/domainand renderer integration onlycodex-model-catalogandteam-runtime-lanes- process-limited features that omit renderer or preload layers when they do not own those boundaries
Use src/features/<feature-name>/ by default when the work introduces:
- a new use case or business policy
- transport wiring
- more than one process boundary
- more than one adapter or provider
Feature-local docs should answer navigation questions:
- which shape the feature uses
- which entrypoints are public
- where new adapters, rules, bridges, or renderer surfaces belong
- what tests protect the behavior
- which local files are the best examples for future changes
Do not duplicate architecture rules in feature folders. Keep the standard centralized in ../../docs/FEATURE_ARCHITECTURE_STANDARD.md.
Rule of thumb:
recent-projectsis the full slice example with process-aware outer layersagent-graphis the thin slice example built aroundcore/plusrenderer/