> 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.md).

# ABTasty CLI v1.X.X

### NAME

abtasty-cli - manage AB Tasty's products resources and developer workflow

### SYNOPSIS

`abtasty-cli _COMMAND_ [--output-format = FORMAT, -f FORMAT] [--help, -h]`

### DESCRIPTION

The AB Tasty CLI manages authentication, developer workflow, and interactions with the Remote Control API.

For a quick introduction to the AB Tasty CLI, a list of commonly used commands, and how these commands are structured, see the [AB Tasty CLI cheat sheet](https://flagship-io.github.io/abtasty-cli/).

### GLOBAL FLAGS

`--output-format = _FORMAT_`

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

`--help`

Display detailed help.

### COMMANDS

{% hint style="warning" %}
🚧 Notice

Make sure you have the right scope in your client id, client secret and token, when you run any command related to web and feature experimentation resources such as project, campaign, flag etc...
{% endhint %}

🔗 [feature-experimentation](https://docs.abtasty.com/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/feature-experimentation.md)

Manage resources related to the feature experimentation product

🔗 [web-experimentation](https://docs.abtasty.com/server-side/command-line-interface/ab-tasty-cli-reference-v1xx/web-experimentation.md)

Manage resources related to the web experimentation product


---

# 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.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.
