> 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/quick-test.md).

# Running your experiment

Once you have created an experiment using empirica create.

## Running the app locally

Run the app on your local machine with one command:

```
empirica
```

This can take a few minutes.

This will start the app that you can access as a participant: <http://localhost:3000>

You can access the `admin panel` here: <http://localhost:3000/admin/>

## Loading the factors and treatments

Treatments and factors can be entered via the admin panel.

Empirica also enables "experiment as code" by which experimental treatments and factors can edited directly in [YAML](https://learnxinyminutes.com/docs/yaml/) at `.empirica/treatments.yaml`.

## Testing the app

To run a game, create a new `batch` with the games of treatments you want to use and click start on the batch.

Open a player tab by going to <http://localhost:3000>.

The player that you open with <http://localhost:3000> is cached on your browser. Whenever you start a game with this player, your local app will keep that information. To play again there are multiple things you can do:

* Click on the **Reset current session** button in the bottom right menu to reset this player, and create a new game for this player to join.
* Click on the **New Player** button in the bottom right menu to open a new tab with a different player (you will see tab with an id).

**The app will automatically ("hot") reload when save changes to the code.**


---

# 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/quick-test.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.