> For the complete documentation index, see [llms.txt](https://docs.bluetext.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluetext.dev/troubleshooting/common-issues.md).

# Common Issues

## Incorrect Configuration

If Polytope and Bluetext are not set up correctly, your configuration or output files will look different from the expected structure. The examples below illustrate common signs of incorrect setup, so you can quickly identify and fix any issues before proceeding.

An indicator that there is an issue either with the Polytope setup or Bluetext repository file is that cline will start to generate code, but the polytope UI will remain empty. 

A valid setup includes a **modules** folder. If your project appears without it, Polytope and/or Bluetext are not configured correctly. The image below demonstrates the expected project structure when the setup is successful.

<div data-full-width="true"><figure><img src="/files/1TPukoVRiyVlzklHQ9Hw" alt="" width="563"><figcaption></figcaption></figure></div>

An example of the file structure resulting from an incorrect configuration may look similar to the following:&#x20;

<figure><img src="/files/3HB33DO6gkSb164yCnMi" alt=""><figcaption></figcaption></figure>

Most of the time, scripts will not be executed when using Bluetext. If Bluetext is configured correctly, the coding agent will primarily use tool calls to interact with the running application. If it is not configured correctly, you might see the coding agent attempt to execute commands directly on your machine. The only commands you should see running locally are curl commands.

The sole purpose of running curl commands directly on your machine is to test whether your services are reachable from outside the containers.