CONNECT FROM YOUR OWN MACHINE

The in-browser terminal is a convenience. For the real experience, open a socket from your own terminal and type commands at the > prompt. It's on voyager1.v9n.us:4242.

Don't want to fight your OS? Open the bootcamp's GitHub Codespace — it's a Linux environment with nc and telnet already installed, running in your browser. Then follow the Linux section below.

macOS

Open Terminal and:

telnet voyager1.v9n.us 4242
# or
nc voyager1.v9n.us 4242

Type STATUS then Enter. Try other commands. Type QUIT to exit cleanly (or Ctrl-] then quit to force-close telnet).

Windows

Honestly: use the in-browser terminal or the bootcamp Codespace. Windows doesn't ship a usable nc or telnet, and the workarounds (PowerShell TCP clients, third-party netcat ports) are more trouble than they're worth for a short poking session.

If you already have WSL installed, jump into a Linux shell and follow the Linux instructions below:

wsl

Linux (or WSL, or the Codespace)

telnet voyager1.v9n.us 4242
# or
nc voyager1.v9n.us 4242

Missing both? On Debian / Ubuntu / WSL:

sudo apt install -y telnet netcat-openbsd

On Fedora / RHEL: sudo dnf install telnet nmap-ncat (use ncat in place of nc). On Arch: sudo pacman -S inetutils openbsd-netcat.

The protocol

• No HELP, no ?, no menu.
• Try STATUS first. Then DSN LINK, INST LIST, FDS MEM, LOG 20.
• Unknown command → ?CMD. Bad args → ?SYNTAX. Don't panic.
• Multi-line replies end with a line containing just . (SMTP-style).
• Full command grammar: commands.md.

Let Claude Code drive

Install the Claude Code Skill — it knows the protocol and the transport quirks, and echoes the exact shell command it used so you still learn while it drives. Instructions in the project README.

Curious what the skill actually tells Claude to do? See the skill's transports reference — it's the imperative version of this page, written for Claude rather than humans.