## Stripe CLI Configuration

The Stripe CLI offers robust configuration options to tailor its behavior to your specific needs. The `config` command is your primary tool for managing these settings, allowing you to set, unset, list, and even edit your configuration file directly.

### `stripe config` Command

The `config` command enables manual management of CLI configuration options. It supports a variety of actions to control how the CLI operates.

**Command:** `stripe config`

#### Flags

*   `-e, --edit`: Opens the CLI's configuration file in your default text editor, allowing for direct manual edits.
*   `--list`: Displays all currently configured options, including any default values that are in effect.
*   `--set <key>=<value>`: Sets or updates the value for a specified configuration option.
*   `--unset <key>`: Removes a configuration option, deleting the corresponding key-value pair from the configuration file.

#### Global `--project-name` Flag

All `config` commands, like many other Stripe CLI commands, support the `--project-name` global flag. This flag is crucial for managing unique configurations for different projects. By specifying a project name, you can maintain separate settings for each of your Stripe integrations within a single configuration file. If `--project-name` is omitted, commands will apply to the default global configuration.

#### Examples

**Setting a Configuration Option:**

To enable colorized output in the CLI:

```sh
stripe config --set color on
```

**Unsetting a Configuration Option:**

To disable colorized output:

```sh
stripe config --unset color
```

**Listing Configured Options:**

To view all active configuration settings:

```sh
stripe config --list
```

This command might output something like:

```
color = "on" [default]
device_name = "st-stripe1"
live_mode_api_key = "rk_live_abc123"
live_mode_publishable_key = "pk_live_abc123"
test_mode_api_key = "rk_test_abc123"
test_mode_publishable_key = "pk_test_abc123"
```