Fix: Add crypto.randomUUID fallback for browser compatibility #34
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The crypto.randomUUID() API requires a secure context (HTTPS or specific localhost conditions). When running CodeNomad Server on 0.0.0.0:9898 or accessing via LAN/VPN, some browsers don't provide this API, causing attachment creation to fail with TypeError.
Added generateUUID() helper that uses crypto.randomUUID() when available, with a Math.random()-based UUID v4 fallback for compatibility.
Fixes file and agent attachment creation in the @ mention picker when running in headless server mode.