// serial
Serial terminal for Windows 11
Open a COM port in a tab, set the baud rate, parity and flow control, and read the device like any other terminal. Telnet, raw TCP and SSH tabs sit in the same window.
A COM port terminal, in a tab
Shell'Naga lists the serial ports Windows has, from COM1 to COM256, plus virtual ports that Windows lists under another name. You pick one in a profile, set it up once and open it whenever you need it. The port opens in a tab, like an SSH session, and you can reconnect or close it from the same prompts.
- Baud rate from a list of common speeds (110 up to 1,500,000), or any speed from 50 to 12,000,000.
- Data bits (5 to 8), stop bits (1, 1.5 or 2) and parity (none, even, odd, mark or space).
- Flow control: none, hardware (RTS/CTS) or software (XON/XOFF).
- An option to send one byte per write, for slow devices.
Type, read and send the way the device expects
Devices disagree about line endings and character sets, so each serial profile has the settings to match.
- Input modes: normal, local echo, a command line mode where you edit a line before it goes out, and a hexadecimal command line for typing raw bytes.
- A hexadecimal view of what the device sends, instead of text.
- Line endings for input and output: keep, remove, CR, LF, CRLF, or add a CR to every LF or an LF to every CR.
- Text encodings: UTF-8, Windows-1252, ISO 8859-1, CP437 and CP850.
- Login scripts that wait for a prompt and answer it, for consoles that ask for a user and a password.
ZMODEM (rz and sz) works in serial tabs, with progress, and it asks before a transfer and never overwrites a file. In a serial tab, tmux -CC turns tmux windows into tabs and panes into native split panes.
Telnet and raw TCP for routers and lab gear
Telnet and raw TCP profiles use the same tab, the same line settings and the same scripts. Telnet starts negotiating only when the server does, so a profile pointed at a device that does not speak telnet is not corrupted by stray control bytes. Both are unencrypted, so Shell'Naga warns you before it dials and waits for your answer. You can also type telnet://host:port as a quick connection.
One window for serial, telnet and SSH
A serial console is rarely the only thing on your bench. The same window holds your SSH sessions with saved profiles and a password vault, an SFTP panel, and your local shells (WSL, PowerShell, Git Bash and cmd) in tabs and split panes. Profiles live in groups in a sidebar, so a console and the server it belongs to can sit together.
Coming from another tool? Serial and telnet profiles come in from a Tabby config, from MobaXterm sessions and from CSV files with a protocol column. Using PuTTY for serial today? See how Shell'Naga compares with PuTTY.
Light on the machine
Shell'Naga is one Rust program that draws on the GPU with Direct3D and DirectWrite. These numbers come from a release build on Windows 11.
What Shell'Naga does not do
- It does not analyze protocols or decode frames. It is a terminal, with a hexadecimal view, not a protocol analyzer.
- It needs Windows 11. Windows 10 is not supported.
Questions
How do I open a COM port in Shell'Naga?
Create a serial profile, pick the port from the list of ports Windows has, set the baud rate and the other line settings, and open it. The port appears in a tab.
What COM port settings can I change?
Baud rate, data bits, stop bits, parity and flow control (none, hardware or software), plus input and output modes, line endings and the text encoding.
Can I see the raw bytes from a serial device?
Yes. A hexadecimal view shows what the device sends as bytes, and a hexadecimal command line mode lets you type bytes of your own.
Is telnet safe to use in Shell'Naga?
Telnet and raw TCP are not encrypted, so Shell'Naga warns you before it connects and waits for your answer. Use SSH when the device supports it.