> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation/feature-experimentation-project.md).

# project

## abtasty-cli feature-experimentation project create

#### NAME

`abtasty-cli feature-experimentation project create` - Create a project

#### SYNOPSIS

`abtasty-cli feature-experimentation project create [-n NAME | --name = NAME]`

#### DESCRIPTION

Create a project in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation project create -n NAME
```

```shell
abtasty-cli feature-experimentation project create -n "My project name"
```

#### REQUIRED FLAGS

`--name = _PROJECT_NAME_`

The name of the project you want to create

***

## abtasty-cli feature-experimentation project list

#### NAME

`abtasty-cli feature-experimentation project list` - List all projects

#### SYNOPSIS

`abtasty-cli feature-experimentation project list [--output-format = OUTPUT_FORMAT [table|json|json-pretty]]`

#### DESCRIPTION

List all projects in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation project list
```

#### FLAGS

`--output-format = _OUTPUT_FORMAT_`

The output format for printing command output resources. The default is table. The supported formats are: json-pretty, table, json.

***

## abtasty-cli feature-experimentation project get

#### NAME

`abtasty-cli feature-experimentation project get` - Get a project

#### SYNOPSIS

`abtasty-cli feature-experimentation project get [-i PROJECT_ID | --id = PROJECT_ID]`

#### DESCRIPTION

Get a project in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation project get -i PROJECT_ID
```

#### REQUIRED FLAGS

`--id = _PROJECT_ID_`

The id of the project you want to display

#### FLAGS

`--output-format _OUTPUT_FORMAT_`

The output format for printing command output resources. The default is table. The supported formats are: json-pretty, table, json.

***

## abtasty-cli feature-experimentation project edit

#### NAME

`abtasty-cli feature-experimentation project edit` - Edit a project

#### SYNOPSIS

`abtasty-cli feature-experimentation project edit [-i PROJECT_ID | --id = PROJECT_ID] [-n NAME | --name = NAME]`

#### DESCRIPTION

Edit a project in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation project edit -i PROJECT_ID -n NEW_NAME
```

#### REQUIRED FLAGS

`--id = _PROJECT_ID_`

The id of the project you want to edit

`--name = _PROJECT_NAME_`

The name you want to set for the project

***

## abtasty-cli feature-experimentation project delete

#### NAME

`abtasty-cli feature-experimentation project delete` - Delete a project

#### SYNOPSIS

`abtasty-cli feature-experimentation project delete [-i PROJECT_ID | --id = PROJECT_ID]`

#### DESCRIPTION

Delete a project in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation project delete -i PROJECT_ID
```

#### REQUIRED FLAGS

`--id = _PROJECT_ID_`

The id of the project you want to delete

***

## abtasty-cli feature-experimentation project switch

#### NAME

`abtasty-cli feature-experimentation project switch` - Switch a project status

#### SYNOPSIS

`abtasty-cli feature-experimentation project switch [-i PROJECT_ID | --id = PROJECT_ID] \[-s STATUS | --status = STATUS [active, paused, interrupted]]`

#### DESCRIPTION

Switch a project status in your account

#### EXAMPLES

```shell
abtasty-cli feature-experimentation project switch -i PROJECT_ID -s STATUS
```

#### REQUIRED FLAGS

`--id = _PROJECT_ID_`

The id of the project you want to switch state

`--status = _STATUS_`

The status you want to set to the project. Only 3 values are possible: active, paused, and interrupted


---

# 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.abtasty.com/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation/feature-experimentation-project.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.
