> For the complete documentation index, see [llms.txt](https://cloakedkeys.gitbook.io/ofsc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cloakedkeys.gitbook.io/ofsc/command-reference/shared-options/common-option-groups/advanced-args.md).

# Advanced Program Options

These options allow you to fine-tune the program's behavior for specific situations. Use them with caution, as they might override default settings or introduce unexpected behavior.

## Caching and API Calls

### -nc, --no-cache

* **Disables:** Reading from and writing to the program's cache.
* **Effect:** Disables all uses of cache including\
  For example cache is used to store keys and file sizes\
  \
  Also forces the program to make fresh sequential API calls for data, even if it's available in the cache. This can be useful for ensuring you have the latest information but can be slower than using the cache
* **Default:** `False` (cache is enabled)

### -nca, --no-api-cache

* **Effect:** Forces the program to make sequential API calls for data, even if it's cached within the current program session. This is different from `--no-cache` which is for all uses of the cache library beyond just OF API request
* **Default:** `False` (API cache is enabled for the current session)

***

## Configuration Overrides

### -k, --key-mode \[argument]

* **Overrides:** The key mode setting specified in the configuration file.
* **Possible values:**
  * cdrm
  * manual
* **Requires Argument:** You must specify the desired key mode after the option (e.g., `-k manual`).
* **Not available in:** `metadata` and `db`

### -pk, --private-key \[argument]

* **Overrides:** The `private-key` setting in the configuration file.
* **Sets:** The path to the private key file used by the `manual` key mode.

### -ci, --client-id \[argument]

* **Overrides:** The `client-id` setting in the configuration file.
* **Sets:** The path to the client id file used by the `manual` key mode.

### -dr, --dynamic-rules \[argument]

* **Overrides:** The `dynamic-rules` setting in the configuration file.
* **Used for:** Signing API requests.
* **Default:** none (the config file's `dynamic-mode-default` is used)
* **Also:** `--dynamic-rule`
* **Possible values:**
  * digitalcriminals (short names: `dc`, `digital`, `digitals`, `digitalcriminal`)
  * datawhores
  * xagler
  * rafa
  * generic
  * manual
* **Requires Argument:** You must specify a value for dynamic rules (e.g., `-dr digitalcriminals`)
* **Note:** Possible values may change based on removal of sources, frequency of updates of sources

***

## Additional Options

### -up, --update-profile

* **Retrieves:** Up-to-date profile information directly from the API, bypassing the cache.
* **Cache Update:** Profile information is typically cached for about a day. Use this option if you need the absolute latest data.

### -al, --auth-fail (also `--auth-quit`)

* quit on authentication failure rather then prompting
* **Default:** False


---

# 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://cloakedkeys.gitbook.io/ofsc/command-reference/shared-options/common-option-groups/advanced-args.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.