> 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/getting-started/setup/windows-wsl-instructions-new.md).

# Windows WSL Instructions (new)

Updated version of WSL?

If you have not already done so, **install** [**Windows Subsystem for Linux (WLS)**](https://learn.microsoft.com/en-us/windows/wsl/) by opening your terminal and running:

```
wsl --install
```

Now you may be prompted to create a username and password. Make sure to write down your login credentials for the future!

Note: Copying and pasting may be disabled in the default settings of your WLS terminal. To remedy this, right-click the title bar and select 'Properties --> Options --> Use Ctrl+Shift+C/V as Copy/Paste.'

**Install Empirica** in your WSL terminal with the following command. You may be prompted to use the WSL password you just created.

```sh
curl https://install.empirica.dev | sh
```

🎉 Congrats, you've now installed Empirica! 🎉


---

# 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/getting-started/setup/windows-wsl-instructions-new.md?ask=<question>&goal=<user_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.