> For the complete documentation index, see [llms.txt](https://docs.empirica.ly/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.empirica.ly/resources/code-editors.md). # Code Editors There are multiple code editors that you could use in when creating your Empirica apps. Here we share some information about Editors/IDEs we use and recommend. ## VS Code Visual Studio Code (VS Code) is a cross-platform editor from Microsoft. It has a plethora of features, built-in tools, and plugins to help your write and debug your Empirica code. And it is particularly easy to install, launch, and use. To get started, head over to , download the installer, and follow the instructions. That's it's you're ready to go. {% hint style="info" %} #### On Windows with WSL You first need to install it on your normal Windows machine as instructed above. Then you need to get this extension install on your VS Code: Once this is done, you can easily launch VS Code from the command line in your WSL with: ``` code ``` Or if you want to open the directory you are currently in with VS Code you can use: ``` code . ``` {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.empirica.ly/resources/code-editors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.