> 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 |

### Legal notice

*The Ledger Enterprise Multisig CLI is a technology feature that enables AI agents and developers to interact with Ledger Enterprise Multisig programmatically. It is not a financial service, brokerage, investment adviser, or custodian. Ledger does not hold, manage, or have access to user assets at any time.*\
\
*All requests initiated through this CLI are subject to the multi-signature approval policies and governance rules defined by the user's administrators. The user is solely responsible for the configuration of its approval policies, the credentials issued to signers, and the logic, prompts, financial parameters, and outcomes of any transaction proposed or initiated by an AI agent. Ledger exercises no control over, and bears no responsibility for, the accuracy, profitability, suitability, or intent of any AI agent operating through this CLI. The user acknowledges that it uses this feature at its own risk.*\
\
*Every transaction proposal requires the completion of the configured multi-signature approval process before execution. Ledger does not guarantee that automated or agent-initiated proposals will meet the approval thresholds required by the user’s governance policies.*\
\
*Where software signers are used in place of hardware device confirmation, the user acknowledges that transactions may be proposed and executed without on-device human confirmation. Software signers are provided for testing environments only and must not be used with mainnet assets.*\
\
*Due to the non-deterministic nature of AI models, instructions generated by AI agents may contain errors, inaccuracies, or unintended parameters. Users must ensure appropriate human oversight of agent-initiated workflows commensurate with the value and risk of the transactions involved.*\
\
*This CLI is provided "as is," in early development, without warranty of any kind. Features, APIs, and behaviours may change. Use of this CLI does not establish any contractual, advisory, or fiduciary relationship between the user or developer and Ledger SAS or its affiliates. To the maximum extent permitted by law, Ledger SAS and its affiliates shall not be liable for any direct, indirect, incidental, special, punitive, or consequential damages arising from use of this CLI, including but not limited to loss of digital assets, unauthorised access, smart contract exploits, or transaction malfunction.*

### Next steps

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