# Virtual Machines

## 1. Logging in

You will receive an e-mail with log in credentials for Vscode-server and Chromium. We recommend logging into both and keeping the tabs open.&#x20;

## 2. Creating a directory for your project

When you open vscode-server you will be at the root directory by default. Navigate to Development and create a new directory here. This is how to create one.

```
root@dino360:~# cd ./Development/
root@dino360:~/Development# mkdir testproject
root@dino360:~/Development# cd testproject
root@dino360:~/Development/testproject# code .
```

then, click enter. The vs-code interface will refresh and you  should see your project name at the top in the search bar like this:

<figure><img src="/files/ufsjolOQcDiWuyYCrj1n" alt=""><figcaption></figcaption></figure>

Repeat these steps when creating a new project, so that you do not create multiple Bluetext projects in the same directory

## 3. View running services in Chromium

Once you have started running tools with Bluetext in Polytope, you can access them in Chromium. In the Polytope TUI, you will find a services section. Instead of clicking the adresses where they are being hosted, you must copy and paste them into chromium to view them.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bluetext.dev/getting-started-with-bluetext/virtual-machines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
