Token2Shell supports URI protocol schemes such as "ssh://" and "telnet://" for starting a session from external sources (ex. web browser, command line and etc.).

For example, when you enter the following from the Command Prompt, Token2Shell is launched (if it’s not already running) and an SSH session is started for connecting to the host "" with a user name "myid".

start ssh://myid@

The following URI schemes are supported and they correspond to the connection types supported in Token2Shell.

Connection TypeURI Scheme
SSH ssh
TELNET telnet
TCP Direct tcp
Docker docker
  • docker://{container-name}{/?tty=exec-bin-path}
    (ex. docker://web/?tty=/bin/bash)
  • If you omit the container name, Docker Console is opened.
Address Book entryt2ab
  • Must use 3 slashes for defining the path for the entry instead of usual 2 slashes
    (ex. t2ab:///folder path/entry-name)
  • If a URI ends with a slash (ex. t2ab:///folder-name/), it’ll be interpreted as a folder path and the Address Book side-panel is opened.
Serial t2serial
  • t2serial://PortNameOrNumber:{settings}
  • {settings} is in the following format:
    BaudRate{, DataBits{, Parity{, StopBits{, FlowControl}}}}
    Parity: none, odd, even, mark, space
    StopBits: 1, 1.5, 2
    FlowControl: rtscts, rtscts+xonxoff, xonxoff
    Available options are equivalent to the SerialHandshake options for Windows 10:
    ◾ rtscts: SerialHandshake.RequestToSend
    ◾ rtscts+xonxoff: SerialHandshake.RequestToSendXOnXOff
    ◾ xonxoff: SerialHandshake.XOnXOff
  • When you need to use a standard URL format, you can encode the settings as the following:


Bluetooth t2btrf
  • t2btrf://DeviceName[DeviceId]:ServiceId
  • When you need to use a standard URL format, you can encode the settings as the following: