> 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/logging.md).

# Logging Options

These options allow you to control the level of detail and location for program logs.

## Log Levels

### -l, --log \[argument]

* **Possible choices:**
  * `OFF`: Disables log output to the log file.
  * `LOW`: Logs basic program flow and non-critical errors.
  * `NORMAL`: Logs most program activity and errors.
  * `DEBUG`: Logs all program activity and detailed debugging information.
  * `TRACE`: The most detailed log level.
* **Sets:** The verbosity level for the program's log file.
* **Default:** not set (the log level comes from the config file).

### -dc, --discord \[argument]

* **Possible choices:**
  * `OFF` (default): Disables log output to Discord.
  * `LOW`: Logs basic program flow and non-critical errors to Discord.
  * `NORMAL`: Logs most program activity and errors to Discord.
* **Sets:** The verbosity level for logs sent to the Discord channel (if configured).

### -p, --output \[argument]

* **Possible choices:**
  * `PROMPT`: Logs only critical information displayed on the program prompt.
  * `LOW`: Logs basic program flow and non-critical errors to the console.
  * `NORMAL` (default): Logs most program activity and errors to the console.
  * `DEBUG`: Logs all program activity and detailed debugging information to the console.
* **Sets:** The verbosity level for log messages displayed in the console window.

## Other Options

### **-nl, --no-live-screen** (also `--no-live`, `--no-rich`)

* **Controls**: Live displays via rich, these are used for Panels, Spinners, and progress bars
* **Defaults**: 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/logging.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.