TransIT AI

Sessions & terminal

Add a device

A device in Transit AI is a single host you want to SSH into. Adding a device records the connection details and the name of an auth profile to use. The auth profile (and the credential it references) must already exist — see Create an auth profile if you haven’t set one up yet.

Open the new-device dialog

Two ways:

  • Click the + icon in the sidebar header.
  • Right-click empty space in the device tree and pick New device….

To pre-fill the group field with an existing group path, right-click a group folder in the tree and pick New device in this group….

Fields

Field Required Notes
ID yes Stable identifier. Shown in the sidebar; used as the default tab label on connect. Example: vEX1.
Host yes DNS name or IP address. Example: 172.20.1.35 or core-sw1.lab.
Port yes SSH port. Default: 22.
Vendor yes Selects the per-vendor permit list for AI-proposed commands. See Vendor coverage.
Group no Slash-separated path for sidebar grouping. Example: Lab/Junos.
Auth profile yes Pick from the list of existing profiles. Click + New in the dropdown to create one inline.
Syntax highlighting no Toggle. Off by default. See Turn on syntax highlighting.
Quick copy/paste no Toggle. Off by default. See Turn on quick copy/paste.

Steps

  1. Open the new-device dialog (see above).
  2. Enter an ID, Host, and Port (or accept default 22).
  3. Pick the Vendor. This matters — it drives which commands the AI is allowed to propose.
  4. Optionally enter a Group path (e.g. Lab/Junos). Groups can be nested with /.
  5. Pick or create an Auth profile.
  6. Optionally enable Syntax highlighting and / or Quick copy/paste for this device.
  7. Click Save. The device appears in the sidebar tree.

What’s written to disk

The device is appended to your transit.toml inventory file under its group path. The file is rewritten atomically (write to a temp file, then rename) so an interrupted save can’t corrupt the inventory.

The auth profile reference is stored by name — the credential itself is fetched from the chosen backend at connect time and never copied into the inventory.

Next steps