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

# Installation

The CFConfig CLI lives on ForgeBox and can be installed into CommandBox with the following command:

```
CommandBox> install commandbox-cfconfig
```

If you do not have CommandBox installed, have no fear! CommandBox is a single binary that will run on Mac, Linux, or Windows. Please visit our CommandBox docs and you'll have it installed in a jiffy.

<https://commandbox.ortusbooks.com/setup/installation>

## Requirements

The only requirement for the CFConfig CLI is [CommandBox](https://commandbox.ortusbooks.com/setup/installation) 3.6.0 or higher.

## Updating CFConfig

CFConfig is under active development and changing on a regular basis. To make sure you have the latest version installed, you can simply `cd` into the CFML home directory of your CommandBox install and use the regular package `update` command. This will pull in minor and patch updates but not major version changes.

```
update --system
```

If you have a pre-release version of CFConfig or need to upgrade to a new major version, use this command:

```
install commandbox-cfconfig --force
```


---

# 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://cfconfig.ortusbooks.com/using-the-cli/installation.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.
