> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/developer-documentation/aeproject/docs/cli/init.md).

# Project Initialization

```
aeproject init [folder]
```

*Optionally* a `folder` can be specified for the project to be initialized in, otherwise the current directory is used.

Creates a new project structure with a few folders in which the developer can create **contracts** and **tests**, as well as installing needed dependencies.

## Update existing project

For upgrade from old AEproject versions check out [Migration from 3.x.x to 4.x.x](/developer-documentation/aeproject/docs/migration-from-3.x.x-to-4.x.x.md) and [Migration from 4.x.x to 5.x.x](/developer-documentation/aeproject/docs/migration-from-4.x.x-to-5.x.x.md).

```
aeproject init --update
```

Updates the project structure and needed artifacts to the latest version, as well as installing needed dependencies.

## Upcoming Hard-fork initialization

The additional parameter `--next` can be used to either initialize or update a project with changes for an upcoming hard-fork if available.


---

# 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.aeternity.com/developer-documentation/aeproject/docs/cli/init.md?ask=<question>&goal=<user_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.
