> For the complete documentation index, see [llms.txt](https://docs.saga.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saga.xyz/sagacli/configuring-sagacli-a-deep-dive.md).

# Configuring sagacli - A Deep Dive

`sagacli` is a powerful CLI tool that is intended to offer end-to-end management of your private keys, accounts and chainlets.

{% hint style="warning" %}
It is imperative that `sagacli` be configured correctly in order for you to get the most out of the tool, and avoid unnecessary errors.
{% endhint %}

To view the current config, type:

```
sagacli config
```

The table below provides an in-depth explanation of each configuration setting.

<table><thead><tr><th width="153">Setting</th><th width="426">Description</th><th>Example Values</th><th>Default Value</th></tr></thead><tbody><tr><td>loglevel</td><td>This setting determines the verbosity of logs produced. Possible values are <code>debug</code>, <code>trace</code>, <code>info</code> (default), <code>error</code> and <code>critical</code></td><td><code>trace</code></td><td><code>info</code></td></tr><tr><td>controller</td><td>Controller accepts gRPC requests from <code>sagacli</code> and acts as the gateway for processing commands. <em>Note</em>: This is a critical setting and must be set correctly in order for <code>sagacli</code> to function properly</td><td>controller.cassio-prod-sp1.sp1.sagarpc.io:19090</td><td>https://controller.sp1.sagarpc.io</td></tr><tr><td>output</td><td>This controls the formatting of output from <code>sagacli</code> commands. Possible values are <code>text</code> and <code>json</code></td><td><code>json</code></td><td><code>text</code></td></tr><tr><td>keyring-backend</td><td>This setting indicates the type of keyring <code>sagacli</code> will use for storing private keys</td><td><code>test</code></td><td><code>file</code></td></tr><tr><td>network-rpc</td><td>This setting specifies the endpoint for connecting to the Saga Platform Chain, which serves as the system of record for chainlets launched, as well as their current status. <em>Note</em>: This is a critical setting and must be set correctly in order for <code>sagacli</code> to function properly</td><td>tcp://spc.cassio-prod-sp1.sp1.sagarpc.io:26657</td><td>https://spc.sp1.sagarpc.io</td></tr><tr><td>from</td><td>This setting specifies the key to be used as the default key when signing transactions. You do not need to have this set in order to be able to use <code>sagacli</code> and having this set is a convenience feature</td><td><code>mykey1</code></td><td>none</td></tr><tr><td>platform-chain-id</td><td>This setting specifies the <code>chain-id</code> of the Saga Platform Chain. <em>Note</em>: This is a critical setting and must be set correctly in order for <code>sagacli</code> to function properly</td><td>spc-testnet-1</td><td>spc-testnet-1</td></tr><tr><td>denom</td><td>This setting specifies the token denomination symbol being used by the Saga Platform Chain. It is best to leave this to the default value</td><td><code>stake</code></td><td><code>tsaga</code></td></tr><tr><td>broadcast-mode</td><td><p>This controls the submission of transactions to the Saga Platform Chain and whether <code>sagacli</code> should wait for the transaction to be checked and committed in a block before the command returns. Possible values are <code>sync</code> and <code>async.</code> </p><p></p><p><strong>IMPORTANT</strong>: It is not recommended that this value be changed. If you do have a use-case for changing the default value, please contact the Saga team before making any changes</p></td><td><code>sync</code></td><td><code>sync</code></td></tr><tr><td>ledger</td><td>This setting enables the use of a connected ledger device for signing transactions. If you have an HD wallet or other such hardware device used to store your private keys, you can use this setting to force each transaction to be signed via the ledger device</td><td><code>true</code></td><td><code>false</code></td></tr></tbody></table>


---

# 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://docs.saga.xyz/sagacli/configuring-sagacli-a-deep-dive.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.