> For the complete documentation index, see [llms.txt](https://docs.world-creator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.world-creator.com/walkthrough/introduction/workspace.md).

# Workspace

The World Creator interface is clear, straightforward and easy to understand. It has been redesigned to provide the best workflow experience. You will undoubtedly find it very intuitive, especially compared to all previous versions of World Creator. Let's take a look at everything and understand how it works.

World Creator's 3D workspace is made up of the 3D viewport, where all the rendering takes place, the main panel (on the right), where everything is set up in relation to the desired terrain, and a toolbar (on the left of the main panel), which provides quick access to several built-in tools. There are also specific HUD elements such as the compass (top), a height meter (left) and the mouse pointer, which displays additional information as you hover over the terrain.

<figure><img src="/files/7y3HGhCrS4BJtZDrVMc6" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

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

```
GET https://docs.world-creator.com/walkthrough/introduction/workspace.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.