rtcom

Rust Terminal Communication — a modern, safe, cross-platform serial terminal for embedded and hardware engineers. Written in Rust, aiming for feature parity with tio while adding a native Windows backend, a first-class library API, and a pluggable architecture for future protocol decoding, scripting, and network sharing.

What's new in v0.2 (Preview)

rtcom v0.2 switches from the v0.1 line-based stdout renderer to a full ratatui-backed TUI:

• Configuration menu at ^A m — minicom-style dialog tree for serial settings, line-endings, modem lines, profile save/load, and screen options.
• Profile persistence via ~/.config/rtcom/default.toml (XDG standard). rtcom -c <path> to override; rtcom ... --save to write the effective configuration on startup.
• Apply live vs. save — every configuration dialog distinguishes F2 (apply to the live session) from F10 (apply + persist to profile), matching the minicom UX.
• Proper VT100 emulation in the serial pane — remote apps that use cursor positioning (ncurses UIs, Zephyr shell, etc.) render correctly.

Breaking change: v0.2 requires a proper TTY. Piping rtcom output through a non-TTY consumer (rtcom /dev/ttyUSB0 | grep ...) no longer works. Use tio's capture feature or rtcom --log (planned for v0.3) instead.

See docs/tui.md for the full keybinding reference.

Features (v0.1)

• Async serial I/O built on tokio-serial (Linux / macOS / BSD).
• UUCP-style lock files so two rtcom instances cannot race the same device.
• Interactive command key (^A by default, configurable via --escape) with: ?/h help, ^Q/^X quit (picocom convention), c show config, t/g toggle DTR/RTS, \ send break, b<rate><Enter> change baud rate.
• Picocom-style startup-time modem-line control: --lower-dtr / --raise-dtr / --lower-rts / --raise-rts. The classic "open the port without resetting the Arduino-style MCU" recipe is --lower-dtr --lower-rts.
• CR/LF mappers (--omap / --imap / --emap) following picocom's crlf / lfcr / igncr / ignlf rule names.
• Clean shutdown on SIGINT / SIGTERM / SIGHUP (termios restored, lock file removed, exit code 128 + signum).
• Structured diagnostics via tracing (honours RUST_LOG; -v / -vv / -vvv raises the default level).
• End-to-end tests via socat-allocated pseudo-terminals — the full pipeline is regression-guarded.

Quick start

# Connect to a USB-serial dongle at 115200 8N1 (default)
rtcom /dev/ttyUSB0

# Change baud + parity + enable LF->CRLF on send
rtcom /dev/ttyUSB0 -b 9600 -p even --omap crlf

# Load a custom profile and persist CLI overrides back to it
rtcom /dev/ttyUSB0 -b 921600 -c ~/.config/rtcom/board-x.toml --save

# Print the full option list
rtcom --help

Press ^A m to open the configuration menu, ^A ^Q (or ^A ^X) to quit. See docs/tui.md for the full keybinding reference.

Installation

From crates.io

cargo install rtcom-cli --locked

--locked pins the dependency versions shipped in Cargo.lock, which keeps the MSRV contract (Rust 1.85) honest.

From source

git clone https://github.com/TrekMax/rtcom
cd rtcom
cargo install --path crates/rtcom-cli --locked

On Linux you'll need libudev-dev (or the equivalent package on your distro) for the underlying serialport crate.

Pre-built binaries

Each tagged release publishes pre-built binaries for the major platforms — grab one from GitHub Releases:

Each release also ships a checksums-sha256.txt so you can verify the download.

Distribution packages

Homebrew tap, AUR, and winget packages are planned for v0.2+. In the meantime, cargo install or the GitHub Releases tarball is the canonical path.

Command keys

Once a session is running, the escape key (default ^A = Ctrl-A; override with --escape '^T' etc.) puts the parser into command mode. The next byte is matched against this table; unknown keys silently return to default mode.

Menu navigation (v0.2)

Inside a dialog opened via ^A m:

See docs/tui.md for the full TUI reference.

vs. picocom / tio

🚧 = on the roadmap.

Workspace layout

Architecture

Event-driven, single-task Session wired through a tokio::broadcast bus. See docs/architecture.svg and the CLAUDE.md design document for the full rationale.

Contributing

The development plan is maintained in CLAUDE.md; §8 covers the TDD + commit-per-phase workflow the project enforces, §9 the coding conventions. Bug reports and PRs welcome — please open an issue to discuss larger changes before sending code.

Running the full test suite locally:

cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace --all-features

License

Apache-2.0. See LICENSE.