OpenSaaS.sh Wasp workflow with WSL and Cursor
Does anyone know the best way to set up the Cursor environment to work properly with Wasp and WSL? I'm using the OpenSaaS.sh template with wasp. Currently I'm opening the project by right clicking on the folder in the WSL File Explorer, then selecting "Open with Cursor". Sometimes it works and sometimes it doesn't (WSL crashes and I have to restart). I have the WSL Cursor extension installed. If this is the wrong place to ask I apologize. I just figured we might have some OpenSaaS.sh people in here 😉
4 Replies
Hi @Enigma. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
Based on the available knowledge sources, there is no specific documentation or official guidance for setting up the Cursor editor with Wasp and WSL, especially in the context of the OpenSaaS.sh template. However, there are some important general recommendations for working with Wasp, WSL, and editors that are highly relevant to your situation:
1. Project Location Matters:
For hot reloading and file change detection to work reliably with Wasp on WSL2, your project files must be located on the Linux file system (e.g., under
See official docs and related Discord discussion. 2. Editor Integration:
While there is no mention of Cursor specifically, the general advice is that you do not need to run your editor from within WSL as long as your files are on the Linux file system. However, some users have reported better stability and fewer issues when using editors that are WSL-aware (like VSCode with the WSL extension).
See Github issue discussion. 3. WSL Crashes:
If WSL is crashing when you open the project with Cursor, this is likely a WSL or Cursor integration issue rather than a Wasp or OpenSaaS.sh-specific problem. Ensuring your files are on the Linux file system and that you are using the latest versions of WSL, Cursor, and their respective extensions may help. 4. OpenSaaS.sh Template:
The OpenSaaS.sh template does not have special requirements beyond the above. The main thing is to follow the general Wasp + WSL best practices.
See template docs. Summary of Best Practices: - Always keep your Wasp project on the Linux file system in WSL2. - Use WSL-aware editors or ensure your editor is properly configured for WSL. - If you encounter issues, try opening the project from within the WSL terminal using the editor's CLI (e.g.,
For hot reloading and file change detection to work reliably with Wasp on WSL2, your project files must be located on the Linux file system (e.g., under
/home/<your-user>/), not on the Windows file system (e.g., /mnt/c/). This is a well-known WSL2 limitation that affects all tools, not just Wasp. If your project is on the Windows file system, Wasp will not detect file changes, and you may experience issues with live reload and possibly with editor integration as well.See official docs and related Discord discussion. 2. Editor Integration:
While there is no mention of Cursor specifically, the general advice is that you do not need to run your editor from within WSL as long as your files are on the Linux file system. However, some users have reported better stability and fewer issues when using editors that are WSL-aware (like VSCode with the WSL extension).
See Github issue discussion. 3. WSL Crashes:
If WSL is crashing when you open the project with Cursor, this is likely a WSL or Cursor integration issue rather than a Wasp or OpenSaaS.sh-specific problem. Ensuring your files are on the Linux file system and that you are using the latest versions of WSL, Cursor, and their respective extensions may help. 4. OpenSaaS.sh Template:
The OpenSaaS.sh template does not have special requirements beyond the above. The main thing is to follow the general Wasp + WSL best practices.
See template docs. Summary of Best Practices: - Always keep your Wasp project on the Linux file system in WSL2. - Use WSL-aware editors or ensure your editor is properly configured for WSL. - If you encounter issues, try opening the project from within the WSL terminal using the editor's CLI (e.g.,
cursor . if supported).
- If problems persist, consider using VSCode with the WSL extension, as it is the most tested and supported setup for Wasp.
If you need more detailed troubleshooting for Cursor specifically, the knowledge sources do not provide enough information, and you may want to reach out to the Cursor or WSL communities for further help.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Enigma, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?If anyone knows, it's @Vinny (@Wasp)
Maybe also @genyus
This is unfortunately related to two things I know very little about - LLMs and WSL 🙃
I’m pretty familiar with Cursor, but not with WSL, unfortunately.
@Enigma this guide might be helpful, though: https://scottspence.com/posts/cursor-setup-for-wsl
Scott Spence
Cursor Setup for WSL - Scott Spence
The WSL Cursor setup, debugging your setup before you even code! I
initially tried Cursor around 18 months ago when I saw something from
Cat...
thank you!