> For the complete documentation index, see [llms.txt](https://help.imagine.art/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.imagine.art/imagine-computer/build/projects-and-workspaces.md).

# Projects and Workspaces

Build projects live in a shared Computer workspace. Each site you generate becomes its own project, with a live thumbnail shown on your Projects page.

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

From Projects, you can filter by All Projects, Starred, or Deployed, search for a specific project, or jump back into a recent one. Create a new project directly from this screen, or open an existing one to continue working on it.

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

Each project has its own settings, including its name, subdomain, owner, creation date, and how many credits it has used. From here you can rename or delete a project, or unpublish it if it has already been published.<br>


---

# 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://help.imagine.art/imagine-computer/build/projects-and-workspaces.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.