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

# CLI

The [steadybit CLI ](https://github.com/steadybit/cli)allows you to connect your repository to Steadybit and having a single source of truth for all your experiments. By enabling you to create / update and retrieve your experiment definitions you have the truth versionized at one place. Of course, you can also run your experiments from the command line interface.

This allows you to implement GitOps practices easily.

## Installation

Nothing more than a simple

```bash
npm install -g steadybit
```

Afterwards you have to create a profile and authenticate via an [access token](/integrate-with-steadybit/api.md#access-tokens). Check out our public GitHub repository [steadybit CLI](https://github.com/steadybit/cli#authorization) to learn more.

## Usage

The CLI is mostly self explaining. For a detailed documentation have a look at our public GitHub repository [steadybit CLI](https://github.com/steadybit/cli)


---

# 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://docs.steadybit.com/integrate-with-steadybit/cli.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.