Termtastic: Handwritten Rust Terminal Client for Meshtastic Mesh Radios with Chat, Nodes and Traceroute
Meshtastic put text chat, position sharing and telemetry on cheap LoRa radios with no cell network and no internet required. Most operators drive their node from a phone app or a browser tab. Both are fine until the station is a field laptop, a Raspberry Pi with a small screen, or an SSH session into a hilltop box. Termtastic fills exactly that gap: a feature-rich handmade Meshtastic console client written in Rust that runs chat, nodes, telemetry, traceroutes and full device configuration right in your terminal.
TL;DR: Termtastic by acelot is a free GPL-3.0 Meshtastic console client handwritten in Rust with a dependency-free single binary for Linux, macOS and Windows. It connects to a Meshtastic radio over TCP, Bluetooth Low Energy or serial with auto-discovery, and gives you channel chat with replies and reactions, a sortable and filterable node list, per-node telemetry, position and traceroute views, a dashboard with station widgets, full radio settings, a connection manager, and a logs screen, all keyboard driven with local SQLite history and daily rolling logs. It works down to 70×21 screens and over SSH, and was named Tool of the Week by Terminal Trove.

What Termtastic Is
Termtastic is a free and open source terminal user interface for Meshtastic mesh radios that turns any laptop or Raspberry Pi into a full mesh station from the command line.
In practice that means one dependency-free single binary built on Ratatui, crossterm and Tokio, launched from your shell, talking to a node over TCP, BLE or serial, with tabs across the top for chat, nodes, dashboard, settings, connection and logs. The header shows battery, online versus total node count, and DB write, traceroute and RX indicators. Everything is keyboard driven with a footer hint line, messages persist in a local SQLite database, and logs mirror to daily rolling files. The project lives at github.com/acelot/termtastic with 98 stars, 4 forks and 215 commits on master, a vibecode-free badge meaning fully handwritten code, and README screenshots covering every tab. It’s an independent project by acelot and isn’t affiliated with Meshtastic LLC.
Why a Terminal Client for Meshtastic Matters
Meshtastic is why hams, EmComm groups and off grid experimenters carry LoRa radios for portable and backup comms. The phone app is great in a pocket. The web client is great on a desktop with a browser. Neither is great inside an SSH session, on a Pi with a tiny display, or on a net control laptop where the browser is already full of logging and mapping tabs.
A console client fits that gap: it runs over SSH, sips memory at around 20 KB, respects your terminal palette for daylight readability instead of forcing its own TrueColor scheme, uses plain ASCII chrome with minimal emoji, and keeps working on screens down to 70×21 characters where a browser would be a burden. Termtastic leans into exactly that with a keyboard-centric UI, local storage so history survives restarts, and TCP plus BLE plus serial transports so the same binary talks to a home node over WiFi, a pocket node over Bluetooth, or a wired node over USB.
Getting Termtastic on Linux, macOS and Windows
Prebuilt binaries ship for all three desktop platforms, or use a package manager where one exists:
- Manual download: grab the release asset for your OS from the releases page, then run it. Single binary, no installer, no dependencies.
- macOS Homebrew:
brew install acelot/tap/termtastic, updated automatically on every release. Unsigned manual builds need one dequarantine step:xattr -d com.apple.quarantine ./termtastic. On macOS Big Sur and later, grant Bluetooth permission to your terminal app under Security and Privacy before BLE discovery will work. - Arch Linux AUR:
termtastic,termtastic-binandtermtastic-gitpackages maintained by Ateles. See the AUR package listing. - Debian APT and Windows WinGet: still to be announced. Until then, manual releases are the path.
The project also earned Terminal Trove Tool of the Week, which is a good independent signal that the terminal community has kicked the tires. If you build from source instead, you get the standard Cargo flow with an optimized release profile using size optimization, link time optimization and stripped symbols.
Chat Tab: Channels, Direct Messages, Replies and Reactions
The chat tab splits into a scrollable channels list with Primary and Secondary plus direct conversations, each row showing the last message, and a messenger pane with full history.
What you get:
- Broadcast messages to channels plus direct messages to nodes, with replies threading back to the original
- Emoji reactions with a picker, detailed reaction view, and per message author node lookup
- SNR and RSSI readouts on direct nodes, hop counts plus routing path on relayed messages and reactions
- 200 character limit with live counter, purge channel chat action, short and long names plus timestamps on every row
- Multiline compose for longer field reports, emoji picker, and clipboard copy for moving traffic into logs
The README channels screenshot shows the list in action: a Primary channel with live traffic, a Secondary channel, and direct chats with per-node online counters in the header.
Nodes Tab: Sortable List, Filters, Search and Expanded Views
The nodes tab is where a growing mesh stays manageable. The scrollable list stores nodes in the local DB with short and long names, node ID, SNR and RSSI for direct hears, hop counts for routed nodes, humanized last heard times, and online versus total counters in the header.
Power tools for big nets:
- Sort by last heard, hop count, distance and more, fuzzy search by name, and filter by special tokens
- Start a direct conversation with the selected node and open its expanded view
- Delete stale entries to keep the list honest during long events
The expanded single node view puts detailed info, telemetry and position in one place, which beats flipping between three screens during a busy net.
Telemetry, Position and Traceroute: See the Path, Not Just the Packet
Three views answer three field questions: how is the node doing, where is it, and how did its packets reach me.
Telemetry shows stored readings per node loaded from the local DB at startup, including battery and sensor data. Position shows coordinates and location details for nodes that share them. Traceroute shows the extended hop by hop path with per-hop signal readings, stored in the DB with a one key copy for dropping the path straight into an incident log or net report. While a traceroute runs, the header TR indicator lights so you know one is in flight.
For net control and after action review this is the killer combination: daily rolling log files plus stored messages, reactions and traceroutes give you who heard whom and by what path, long after the net closes.
Dashboard Tab: Station Widgets at a Glance
A newer addition is the dashboard with widgets for node info, uptime, online nodes, clock, hops statistics, role statistics, hardware statistics, and device metrics. Park the client on this tab on the net control laptop and the health of the mesh is visible from across the room: how many nodes are online, what roles and hardware dominate the net, and how hop counts distribute. It’s the closest a terminal gets to a wall display, and it costs no extra software.
Settings Tab: Configure the Radio Without Leaving the Terminal
Settings covers general device configuration load and save plus the full radio tree:
- Radio: LoRa modem, channels, security keys
- Device: user callsign, device role, position, power, display, Bluetooth, network
- Module: MQTT, serial, external notification, store and forward, range test, telemetry, canned message, neighbor info, ambient lighting, detection sensor
- General: telemetry stored per node and reloaded at startup
For EmComm teams this means one operator can set callsign, position reporting, power policy and store and forward behavior from the same keyboard that sends the traffic. No phone to pass around, no browser tab to find.
Connection Tab: TCP, BLE and Serial with Auto Discovery
The connection tab lists TCP, BLE and serial devices, connects with stored TCP profiles, discovers paired BLE devices and serial ports automatically plus TCP nodes over mDNS, loads device config during connect into state, and reconnects with exponential backoff.
Practical notes: give each device a name in the client, wired serial is the most predictable for first setup, and BLE keeps a pocket node usable while the laptop stays in the bag. A radio accepts one Bluetooth connection at a time, so close the phone app before connecting the laptop. Standard system directories hold config, database and logs where each OS expects them.
Filters and Logs
A few smaller views round out daily use. Special token filters slice a 267 node list down to what matters during a net. The logs tab mirrors app logs with scroll, per record expand for long entries, and clipboard copy. Log files use a daily rolling strategy, so a week-long deployment is a tidy directory of dated files instead of one giant blob.
Under the Hood: Handwritten Rust on Ratatui and Tokio
The tech highlights state the philosophy plainly: fully handwritten code with no vibe-coding, dependency-free single binary distribution, fully async on Tokio channels so the UI never waits for the radio, small screen optimization, terminal color respect, keyboard-centric navigation, minimal emoji in chrome, automatic discovery across all three transports, standard system directories, and a small memory footprint.
| Layer | Library |
|---|---|
| TUI framework | Ratatui |
| TUI backend | crossterm |
| Inputs | ratatui-textarea |
| Lists | tui-widget-list |
| Meshtastic protocol | meshtastic Rust crate |
| Clipboard | arboard |
| BLE discovery | btleplug |
| TCP discovery | mdns-sd over mDNS |
| Logging | tracing with Tokio |
| Async runtime | Tokio channels |
| Config paths | confy plus etcetera |
| Errors | anyhow plus thiserror |
| Time | chrono |
| Emoji data | emojis crate |
| Local DB | rusqlite plus rusqlite_migration |
Compatibility is tested across Linux, macOS and Windows for BLE, serial and mDNS discovery plus clipboard. Every connection path in the matrix shows tested status on all three platforms.
Comparison: Termtastic and Other Ways to Drive Meshtastic
| Attribute | Termtastic TUI | Meshtastic phone app | Meshtastic web client |
|---|---|---|---|
| Runs over SSH or tiny screens | Yes, down to 70×21 | No | Needs a browser |
| Transports | TCP, BLE and serial with discovery | Mostly BLE plus WiFi | Mostly serial plus network |
| Chat plus reactions and replies | Yes, with routing and hop display | Yes, full featured | Yes |
| Node list at mesh scale | Yes, sort, fuzzy search and token filters | Basic list | Basic list |
| Telemetry, position and traceroute | Yes, stored in SQLite with copy | Yes | Partial |
| Station dashboard widgets | Yes, uptime, roles, hops, hardware | No | No |
| Radio and module settings | Yes, full tree in terminal | Yes | Yes |
| Local history and log files | Yes, SQLite plus daily rolling logs | On device | Limited |
| Install friction | Single binary, Brew tap, AUR | App store | Browser plus drivers |
| Best for | Laptop, Pi or SSH field station | Pocket carry | Desktop with browser |
The honest takeaway: keep the phone app for pocket carry, keep the web client for quick desktop checks, and put Termtastic on the machine that stays on during nets, logs everything locally, and works fine over a slow SSH link.
Practical Ham and Field Uses
- Net control laptop: TCP to a base node, channels list on screen, dashboard widgets showing online count and hop spread, filters trimming 200 plus nodes to the active net, traceroutes copied into the log.
- Hilltop Pi over SSH: serial to the local node, logs tab watching health, SQLite history surviving disconnects.
- Go kit with phone plus laptop: phone app released so BLE is free, laptop connects over BLE, DMs and channel traffic side by side with battery and RX indicators up top.
- After action review: daily rolling log files plus stored messages, reactions and traceroutes give you who heard whom and by what path.
- Club training night: one projected terminal showing chat, nodes and dashboard teaches new operators the whole mesh model without touching anyone phone.
Honest Limitations
- Under active development: the README warns things can change without notice. Pin a release binary for real events.
- Package managers still partial: Arch AUR and macOS Brew exist now, but Debian APT and Windows WinGet are still to be announced.
- Not yet implemented: ignore node, favorites, import configuration from a link, fixed GPS position, and set time from host. Check the README before promising these in a deployment plan.
- macOS needs two manual steps: dequarantine unsigned binaries with xattr, and grant Bluetooth permission to your terminal under Security and Privacy on Big Sur and later.
- Emoji rendering varies: foot terminal users may need grapheme width set to wcswidth, and Windows Terminal can’t draw some compound emoji tracked upstream.
- One Bluetooth owner at a time: disconnect the phone app before Termtastic claims the radio over BLE.
Why It Matters
Mesh interest keeps colliding with the same reality: the most useful station is the boring one that stays on, logs everything and works from whatever screen you have. A handwritten terminal client with local storage, three transports, full settings, dashboard widgets and traceroute history turns a laptop or Pi into exactly that station. For amateur radio it also lowers the barrier for operators who live in terminals already: no new GUI to learn, no browser tab to lose, just chat, nodes, dashboard, settings, connection and logs a few keystrokes apart.
Sources and Further Reading
- Termtastic homepage
- Termtastic GitHub repository
- Termtastic releases
- Termtastic on Terminal Trove
- Termtastic AUR packages
- Meshtastic official site
- Meshtastic Rust crate
- Ratatui TUI framework
- Ham2K Portable Logger guide on HamRadio.my
- MeshCore TAK Bridge guide on HamRadio.my
73 de 9M2PJU



Post Comment