Automation with URLs
Other apps, scripts, and documents can open OliTerm sessions through two URL schemes.
oliterm://connect
oliterm://connect?to=user@host&port=2222&name=Label| Parameter | Meaning |
|---|---|
to | Required. The destination — user@host, a bare hostname, or even a full ssh user@host -p 2222 string; it’s parsed like the host editor’s quick-add field. |
port | Optional. Overrides the port (default 22). |
name | Optional. The label used when the host is added to the sidebar. |
From a script or terminal:
open "oliterm://connect?to=admin@server.example.com&name=web-1"ssh:// links
OliTerm also opens standard ssh://user@host:port links — for
example from documentation pages or inventory tools. OliTerm registers as an
ssh link handler without making itself the system default; choose your default
handler as usual in the system’s settings for link handling.
What happens when a link opens
- If the destination matches a saved host (same hostname and port — and same user, when the link specifies one), the session opens immediately in a new tab.
- If it’s unknown, OliTerm asks first: “Add and connect to …?” shows exactly which
user@hostthe link wants to reach. Add & Connect saves it to the sidebar and connects.
Note
The confirmation exists because any app or web page can invoke these URLs, and
opening a shell to an attacker-chosen machine shouldn’t ever be a silent
side effect of clicking a link. Only continue if you trust where the link came
from.
Launching OliTerm via a link goes straight to the requested session — the usual local window is skipped.