Build Docker Release License

A terminal UI for monitoring and configuring Meshtastic mesh networks. Connects to a Meshtastic node via HTTP and displays real-time packet traffic, node information, chat messages, and device configuration.

• Packets view - Live packet stream with detailed inspection (decoded payload, JSON, hex dump)
• Nodes view - Discovered nodes with signal quality, battery, position, hardware, favorites
• Chat view - Send and receive channel messages with emoji support and delivery status
• DM view - Direct messages with delivery status and resend support
• Config view - View and edit device configuration with batch mode
• Log view - Position, traceroute, and nodeinfo response history
• Node commands - Traceroute, position/telemetry/nodeinfo request, direct ping, DM
• ACK notifications - Visual feedback when nodes acknowledge your packets
• MeshView integration - Update node info from a MeshView server, view live MeshView traffic
• Persistent storage - SQLite database for nodes, messages, and packets
• Session support - Multiple named sessions for different radios

Grab the latest release for your platform from the Releases page.

chmod +x meshtastic-cli-darwin-arm64
./meshtastic-cli-darwin-arm64 192.168.1.100

Note: macOS binaries are not codesigned. You may need to right-click and select "Open" or run xattr -d com.apple.quarantine <binary> to bypass Gatekeeper.

docker volume create meshtastic-cli
docker run --rm -it -e TERM -v meshtastic-cli:/root/.config ghcr.io/statico/meshtastic-cli 192.168.1.100
# With MeshView integration (e.g., Baymesh)
docker run --rm -it -e TERM -v meshtastic-cli:/root/.config ghcr.io/statico/meshtastic-cli 192.168.1.100 --meshview https://meshview.bayme.sh

Requires Bun.

bun install
bun run dev 192.168.1.100

meshtastic-cli <address> [options]
Arguments:
 address Device address (required) - IP address, hostname, or serial port
Options:
 --session, -s Session name for database (default: default)
 --clear Clear the database for the session and exit
 --skip-config Skip loading device configuration on startup
 --skip-nodes Skip downloading node database (faster connect)
 --meshview, -m MeshView URL for packet/node links
 --fahrenheit, -F Display temperatures in Fahrenheit
 --port, -P HTTP port number (default: 4403 if no port in address)
 --tls, -T Use HTTPS instead of HTTP
 --insecure, -k Accept self-signed SSL certificates
 --pcap <file> Write packets to pcap file for analysis
 --help, -h Show help

Connect to a Meshtastic device (default port 4403):

meshtastic-cli 192.168.0.123

Connect to meshtasticd HTTP API (port 8080 with HTTPS):

meshtastic-cli 127.0.0.1 --port 8080 --tls --insecure

Note: meshtasticd servers need to have the webserver enabled. The webserver typically runs on port 8080 with HTTPS. Check your meshtasticd configuration to ensure the webserver is enabled.

Connect to a device on a custom port:

meshtastic-cli 192.168.1.100 --port 8080

Connect with HTTPS and accept self-signed certificate:

meshtastic-cli example.com --tls --insecure

Capture packets to pcap file for analysis:

meshtastic-cli 192.168.0.123 --pcap traffic.pcap

The pcap file can be analyzed with tools like Wireshark or tcpdump. Packets are written in pcap format with LINKTYPE_USER0 (147) containing the raw Meshtastic protobuf frames.

In Chat and DM views, messages show delivery status:

The [M] indicator also appears in the Packets view when a MeshView URL is configured. This confirms the packet was received by the MeshView aggregation server, which is useful for verifying mesh propagation.

Direct ping sends a traceroute request with hopLimit: 0, which means only nodes in direct radio range will receive and respond to the packet. This is useful for testing immediate connectivity to neighbors.

How it works:

• The request is sent with 0 hops, so only direct recipients can receive it
• No retransmissions occur (more lightweight than regular traceroute)
• Only nodes that can directly hear your transmission will respond

Caveats:

• The response may still be relayed through intermediate nodes (firmware limitation)
• You cannot definitively confirm bidirectional direct connectivity - you only know they heard YOU directly
• Less reliable than regular traceroute (single transmission, no retries)
• No response could mean: (a) not in direct range, or (b) packet was lost to interference

For full bidirectional direct-link testing with RSSI measurements, firmware changes would be needed. See meshtastic/firmware#8905 for ongoing discussion.

For proper emoji and Unicode character display, ensure your terminal uses Unicode-compliant width calculations:

• Ghostty - Uses Unicode widths by default (grapheme-width-method = unicode)
• Kitty - Uses Unicode widths by default
• iTerm2 - Enable in Preferences → Profiles → Text → "Unicode version 9+ widths"
• Terminal.app - May have issues with some emoji

There are still issues with some emoji and fixing them is a work in progress.

MIT