Welcome to the Hiero CLI Tool, a powerful and intuitive command-line interface designed to streamline your interactions with the Hedera network. Whether you're a developer needing to set up test environments, automate network-related tasks, or explore the extensive capabilities of the Hedera mainnet and testnet, this tool is your one-stop solution.

The Hiero CLI Tool elegantly addresses the complexities associated with distributed ledger technologies. It simplifies the process of executing actions such as creating new accounts, sending transactions, managing tokens, and associating with existing tokens directly from the CLI. This high level of functionality and ease of use significantly reduces the barrier to entry for developers working on Hedera-based projects.

A key advantage of the Hiero CLI Tool is its potential to enhance your workflow. It's not just about performing individual tasks; it's about integrating these tasks into a larger, more efficient development process. With plans for future integration into Continuous Integration/Continuous Deployment (CI/CD) pipelines, this tool promises to be a versatile asset in the automation and management of Hedera network operations.

🎯 Feature requests can be submitted on the Hiero CLI repository as an issue. Please check the issues before submitting a new one and tag it with the Feature Request label.

• Quick Start
• Manual Setup (For Developers)
  • Prerequisites
  • Installation
• Video Guide
• Plugins
• Configuration & State Storage
  • State directory location
  • Script mode
• Getting Help
• Support
• Code of Conduct
• Contributing
• License

The easiest way to get started with Hedera CLI is to install it globally via npm:

npm install -g @hiero-ledger/hiero-cli

Once installed, you can use the CLI with the hcli command:

# Check available commands
hcli --help

# Example: Check account balance
hcli account balance --account-id 0.0.123456

# Example: Transfer HBAR
hcli hbar transfer --to 0.0.123456 --amount 10

First-time setup (Initialization): When you run any command that requires an operator (like transferring HBAR or creating tokens) in interactive mode, the CLI will automatically launch an initialization wizard to guide you through configuring the operator account, private key, and settings. In script mode (non-interactive), an error will be thrown instead, requiring you to use hcli network set-operator to configure the operator first.

If you want to contribute to the development of the Hedera CLI or run it from source, follow these instructions.

Before proceeding with the installation and setup of the Hiero CLI Tool, ensure the following prerequisites are met:

The Hiero CLI Tool requires Node.js (version LTS 16.20.2 or higher). You can check your current version by running node -v in your terminal. If you do not have Node.js installed, you can download it from Node.js official website.

You will need an account on the Hedera network to interact with the ledger. Follow these steps to set up your account:

• Visit the Hedera Portal and create a new account.
• During the account creation process, you will receive a DER encoded private key and an account ID. These credentials are essential for authenticating and performing operations using the Hiero CLI Tool.

Make sure to securely store your DER encoded private key and account ID, as they are crucial for accessing and managing your Hedera account.

The Hiero CLI Tool repository is hosted on GitHub. You need to have Git installed to clone the repository. You can check your current version by running git --version in your terminal. If you do not have Git installed, you can download it from Git official website.

Make sure to clone the repository. You can do this by running the following command in your terminal:

git clone https://github.com/hiero-ledger/hiero-cli.git

Navigate to the repository folder and install the necessary packages using npm. This sets up everything you need to get started with the Hiero CLI Tool.

cd hiero-cli
npm install

Compile the package to ensure all components are ready for use.

npm run build

The Hiero CLI initializes automatically when you run any command. The CLI loads default plugins and registers their commands. No manual setup is required.

When you first run the CLI, it will:

• Load all default plugins from dist/plugins/
• Initialize the Core API with the selected output format
• Register all plugin commands
• Use testnet as the default network

Note: There is a test plugin available that is required for running integration tests.

You can verify the installation by checking available commands:

node dist/hiero-cli.js --help

To interact with Hedera networks, you need to configure operator credentials for each network you want to use. Use the network plugin's set-operator command:

# Set operator for testnet using account name (if already imported)
node dist/hiero-cli.js network set-operator --operator my-testnet-account --network testnet

# Set operator for testnet using account-id:private-key pair
node dist/hiero-cli.js network set-operator --operator 0.0.123456:302e020100300506032b657004220420... --network testnet

# Set operator for mainnet
node dist/hiero-cli.js network set-operator --operator 0.0.123456:302e020100300506032b657004220420... --network mainnet

The operator credentials are stored in the CLI's state management system. Make sure that each operator account contains at least 1 Hbar for transaction fees.

💡 Note on Initialization: When running the CLI interactively, if an operator is not configured and you attempt to run a command that requires it, the CLI will automatically launch an interactive setup wizard that guides you through configuring the operator, private key, and related settings. In script mode (non-interactive), if the operator is not configured, an error will be thrown instead.

The CLI uses testnet as the default network. You can switch to other networks using the network plugin:

# Switch to mainnet
node dist/hiero-cli.js network use --network mainnet

# Switch to previewnet
node dist/hiero-cli.js network use --network previewnet

# Switch to localnet
node dist/hiero-cli.js network use --network localnet

To avoid typing the full command each time, you can set an alias in your shell profile. Replace the path with the absolute path to your hiero-cli installation.

Add the following line to your ~/.bashrc, ~/.bash_profile, or ~/.zshrc:

alias hcli="node /path/to/hiero-cli/dist/hiero-cli.js"

Then reload your shell:

# For bash
source ~/.bashrc
# or
source ~/.bash_profile

# For zsh
source ~/.zshrc

Add the following line to your PowerShell profile. First, open PowerShell and check if your profile exists:

# Check if profile exists
Test-Path $PROFILE

# If it doesn't exist, create it
New-Item -ItemType File -Path $PROFILE -Force

Then add the following function to your profile:

function hcli {
    node C:\path\to\hiero-cli\dist\hiero-cli.js @args
}

Then reload your PowerShell:

. $PROFILE

Now you can use hcli with arguments just like on Unix systems.

The Hiero CLI tool can be used to interact with a local Hedera network. This is useful for testing and development purposes. To connect the CLI tool with your local Hedera network, you need to set up a local Hedera network. You can follow the instructions in the Hedera documentation to set up a local Hedera network.

By default, the src/core/services/network/network.config.ts file contains the default configuration for the localnet. The default configuration is:

{
  "localNodeAddress": "127.0.0.1:50211",
  "localNodeAccountId": "0.0.3",
  "localNodeMirrorAddressGRPC": "127.0.0.1:5600",
  "rpcUrl": "http://localhost:7546",
  "mirrorNodeUrl": "http://localhost:5551/api/v1"
}

To use the localnet, set the operator credentials using the network plugin:

hcli network set-operator --operator 0.0.2:302e020100300506032b65700123456789132178e72057a1d7528025956fe39b0b847f200ab59b2fdd367017f3087137 --network localnet

Then switch to the localnet:

hcli network use --network localnet

The Hiero CLI is built on a plugin architecture. The following default plugins are loaded automatically:

• Account Plugin - Create, import, manage accounts, and view balances
• Token Plugin - Create, associate, and transfer tokens
• Network Plugin - Switch networks, manage operator credentials, and check network health
• HBAR Plugin - Transfer HBAR between accounts
• Credentials Plugin - Manage operator credentials and keys
• Plugin Management Plugin - Add, remove, enable/disable, and inspect plugins
• Topic Plugin - Create topics and manage topic messages
• Config Plugin - Inspect and update CLI configuration values

Each plugin has its own README with detailed documentation about available commands, usage examples, and architecture details. Click on the plugin name above to learn more.

The CLI externalizes both its immutable base configuration and mutable runtime state. No editable JSON lives in src/state/ anymore.

By default, the CLI stores plugin state in your home directory:

• Default location: ~/.hiero-cli/state/ (in the current working directory)

Each plugin (or state namespace) uses its own JSON file inside this directory. These files are managed by the CLI; you typically should not edit them manually.

The CLI supports two storage methods for private keys:

• local - Keys are stored as plain text in the state directory (suitable for development and testing)
• local_encrypted - Keys are encrypted using AES-256-GCM before storage (recommended for production use)

Configure the default key storage method using the config command:

# Set to plain text storage (development/testing)
hcli config set -o default_key_manager -v local

# Set to encrypted storage (production)
hcli config set -o default_key_manager -v local_encrypted

You can override the default key manager for specific operations by providing the --key-manager flag:

# Import account with encrypted key storage
hcli account import --id 0.0.123456 --key <private-key> --name myaccount --key-manager local_encrypted

# Set operator with plain text storage
hcli network set-operator --operator 0.0.123456:302e... --network testnet --key-manager local

This allows you to use different storage methods for different keys based on your security requirements.

If you encounter issues not covered here, please:

1. Check the GitHub issues for similar problems
2. Create a new issue with debug output included and with a clear description

If you have a question on how to use the product, please see our support guide.

This project is governed by the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code of conduct.

Contributions are welcome! Please check out the CONTRIBUTING.md file for guidelines.

Apache License 2.0