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
{{ message }}
Repository navigation
Web interface: Attaching files is broken in insecure contexts #11452
I'm using Opencode web installed on a server of mine inside the home network. When trying to attach a file, I get an error in the console for crypto.randomUUID being undefined, and the file isn't uploaded. crypto.randomUUID is indeed undefined, because running not on "localhost" and over HTTP is considered insecure. However, the rest of opencode works just fine, and this is only about creating a unique ID for the attachment.
Plugins
No response
OpenCode version
No response
Steps to reproduce
Run opencode web
Connect from another computer on the same network
Try to attach a file
Screenshot and/or share link
No response
Operating System
No response
Terminal
No response
Reacted by Darcy Glennen, ricky-sb, Marcos Segovia and Paweł Neubauer
These issues suggest a broader problem with how the web interface handles file operations and insecure contexts. Feel free to ignore if your specific case requires a different approach.
Activity
github-actions commentedon Jan 31, 2026
This issue might be a duplicate of existing issues. Please check:
These issues suggest a broader problem with how the web interface handles file operations and insecure contexts. Feel free to ignore if your specific case requires a different approach.
fix: add fallback for when crypto.randomUUID is unavailable
fix: add fallback for when crypto.randomUUID is unavailable
fix: add fallback for when crypto.randomUUID is unavailable
fix: add fallback for when crypto.randomUUID is unavailable
fix: add fallback for when crypto.randomUUID is unavailable
fix: add fallback for when crypto.randomUUID is unavailable
fix: add fallback for when crypto.randomUUID is unavailable