Browse Source
Remote and server-hosted deployments cannot rely on the browser user's desktop tools being available inside the Node server process. Directory browsing now checks for native picker commands first and falls back to a configurable server-side workflows directory instead of surfacing command-not-found errors. Constraint: The browse endpoint runs on the server, not on the Windows client browser Constraint: Test servers may not have osascript, zenity, kdialog, PowerShell, or an interactive desktop session Rejected: Keep propagating native picker failures to the modal | successful server deployments without desktop tools showed red command errors Confidence: high Scope-risk: narrow Directive: For true client-local folder selection, use a separate File System Access API flow instead of this server filesystem endpoint Tested: npx vitest run src/app/api/browse-directory/__tests__/route.test.ts src/components/__tests__/ProjectSetupModal.test.tsx Tested: npm run build Not-tested: Interactive Windows Server desktop picker sessionhandoff-20260429-1057
1 changed files with 68 additions and 30 deletions
Loading…
Reference in new issue