> For the complete documentation index, see [llms.txt](https://help.multisig.ledger.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.multisig.ledger.com/guides/cli-guides/cli-overview.md).

# CLI Overview

The Ledger Enterprise Multisig CLI (`lem`) is a command-line interface that lets you operate Safe multisig wallets directly from your shell. Query Safes, propose transactions, collect signatures, and execute on-chain using either a Ledger hardware device or a software signer.

`lem` covers the full Safe transaction lifecycle and produces structured JSON on stdout for every command, which makes it equally suitable for:

* **Human operators** automating recurring treasury operations or scripting incident response.
* **AI agents** that need a discoverable, predictable, machine-parseable surface for Ledger Multisig.

It is the same Ledger-secured multisig platform documented in the [API Overview](https://help.multisig.ledger.com/) and [Guides](https://help.multisig.ledger.com/guides), exposed through a different surface.

### What you can do

| Area               | Commands                                                                |
| ------------------ | ----------------------------------------------------------------------- |
| Signer setup       | `lem` connect, `lem` config show, `lem` config path                     |
| Query Safes        | `lem` safe scan, `lem` safe info, `lem` safe balances, `lem` safe nonce |
| Query transactions | `lem` tx list, `lem` tx show                                            |
| Sign & execute     | `lem` tx propose, `lem` tx sign, `lem` tx execute                       |

With these commands you can run the **entire** Safe transaction lifecycle, from proposal to on-chain execution, without ever leaving the shell. See **Proposing, signing & executing** for the end-to-end walkthrough.

### Architecture

`lem` is a thin wrapper around the same components used by the existing TypeScript and Python guides:

* The **Safe API Kit** for Transaction Service reads and proposals.
* The **Safe Protocol Kit** for transaction creation, signing, and on-chain execution.
* The **Ledger Device Management Kit** for hardware signing over USB.

All operations target Ledger's hosted Transaction Service, so any Safe or transaction you touch via `lem` appears in the [Ledger Enterprise Multisig UI](https://app.multisig.ledger.com/) and in API queries, and vice versa. The JSON output of every command is the same shape returned by the underlying SDK / REST API, so anything you can build with the SDKs you can build with the CLI.

### Supported networks

The CLI supports the same chains as the rest of the platform. See [Supported Networks](https://help.multisig.ledger.com/supported-networks). At the time of writing:

| Network                    | Chain ID |
| -------------------------- | -------- |
| Ethereum Mainnet           | 1        |
| Optimism                   | 10       |
| BSC                        | 56       |
| Base                       | 8453     |
| Arbitrum                   | 42161    |
| Ethereum Sepolia (testnet) | 11155111 |

### Next steps

* **Installation**
* **Quickstart**


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.multisig.ledger.com/guides/cli-guides/cli-overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.