> For the complete documentation index, see [llms.txt](https://docs.tensorleap.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tensorleap.ai/user-interface/project.md).
# Project
A project defines the scope of the models and model versions for your use case.
## Create a Project
{% hint style="info" %}
It is recommended to create a project while pushing a [model](/tensorleap-integration/uploading-with-cli/cli-assets-upload.md#uploading-a-model) or [project](/tensorleap-integration/uploading-with-cli/cli-assets-upload.md#uploading-both-a-code-and-model) using the CLI
{% endhint %}
You can create a project after logging on to your account.
To create a project:
1. Click the side menu on the top left.
2. Click **New Project**.
3. On the **New Project** window, enter a name for your project.
4. Enter a description for the project.
5. Click **Create**.
## Open a Project
To open and start working on your project, you can either:
* Locate your project in **Recent Projects** and click it:
Opening a project from Recent Projects
{% hint style="info" %}
When you save your project for the first time, Tensorleap treats it as the master branch, with subsequent revisions being new branches. You can create different branches when saving a new version of a project. For more information, see [Versions](/user-interface/project/versions.md).
{% endhint %}
---
# 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.tensorleap.ai/user-interface/project.md?ask=&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.
