> For the complete documentation index, see [llms.txt](https://metalbear.com/mirrord/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metalbear.com/mirrord/docs/getting-started/installing-mirrord/cli/global-configuration.md).

# Global Configuration

Set and remove user-wide mirrord CLI defaults

mirrord stores user-wide configuration in `~/.mirrord/mirrord.json`. Use it for a preference you want to keep across projects, rather than adding the same setting to every project's config file. The CLI creates the file as an empty JSON object when it is missing.

{% hint style="warning" %}
**Currently, only `operator` is used as a global default when starting a session.** The commands below can store other valid mirrord configuration fields, but those fields do not yet affect sessions through the global file. Set them in a [project configuration file](/mirrord/docs/getting-started/installing-mirrord/cli.md#configuration) instead.
{% endhint %}

### Set a default

Run `mirrord config set <PATH> <VALUE>` to save a value in the global file. For example, to require the mirrord Operator by default:

```bash
mirrord config set operator true
```

Use `false` to disable it by default:

```bash
mirrord config set operator false
```

If mirrord successfully starts a session using the Operator, it also remembers `operator: true` in this file for future sessions. An explicit project config value (including `false`) or the `MIRRORD_OPERATOR_ENABLE` environment variable takes precedence over the global default.

`PATH` is a dot-separated config field name, such as `operator` or `agent.image`. `VALUE` is parsed as JSON when possible (for example, `true`, `42`, or a JSON object); otherwise it is stored as a string. To force a string that looks like JSON, include JSON double quotes in the value, for example `mirrord config set agent.image '"true"'`. Fields and values must match the [mirrord configuration schema](https://metalbear.com/mirrord/docs/config). Setting a field within an array by index is not supported.

### Remove a default

Run `mirrord config unset <PATH>` to remove a value from the global file:

```bash
mirrord config unset operator
```

Removing `operator` restores the usual behavior: mirrord tries the Operator first and can continue without it if unavailable. Unsetting a field that is not present returns an error. Both commands reject invalid config changes rather than saving an invalid file.

You can inspect or edit `~/.mirrord/mirrord.json` directly as JSON. The `set` and `unset` commands require an existing file to be valid, untemplated JSON; a templated config file can be read during session setup but cannot be updated by these commands.


---

# 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://metalbear.com/mirrord/docs/getting-started/installing-mirrord/cli/global-configuration.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.