TransIT AI
Sign up

Features

Your old SSH client just got upgraded — now with an agentic AI that can investigate but can’t break things. Below is what’s in the v1 product.

SSH client

Multi-session tabs

  • One terminal pane per session; scrollback survives tab switches.
  • Click the tab strip to switch; right-click for rename, export, split, close.
  • Multiple sessions per device are allowed — labels disambiguate as vEX1, vEX1 (2), vEX1 (3), etc.
  • Closing a still-connected tab opens a confirm dialog; ended tabs close without prompting.

Three ways to connect

  • Right-click → Connect in the sidebar.
  • Double-click the device row.
  • Click to focus, then press Enter.

All three open a new tab and focus it.

Reconnect with Enter

After typing exit or logout, the tab stays in place with an amber “session ended” banner. Press Enter inside the pane to reconnect: the dead backend session is cleaned up best-effort, a fresh SSH session opens against the same device, and the new sessionId is swapped into the same tab slot. Custom labels and split anchors survive the swap.

Split-pane view

Right-click a tab → Split right with… to put another session side-by-side in the same tab. Closing the right pane unsplits.

Per-device terminal preferences

Each device record can opt into:

  • Syntax highlighting — keyword-based ANSI colouring of completed lines. Auto-bypasses while the device is in the alt screen (so vi, less, top render correctly).
  • Quick copy/paste — auto-copy on selection, right-click and middle-click paste. Multi-line pastes prompt for confirmation regardless.

Cmd/Ctrl+F opens an in-pane search overlay. Enter cycles forward, Shift+Enter back, Esc closes. Searches the terminal’s 10,000-line scrollback buffer.

Session export

Right-click a tab → Export scrollback…. The export pipeline re-runs the redaction filter on the raw bytes (so freshly-emitted secrets are stripped even if they weren’t filtered at display time) and offers age encryption with a recipient key. A leaked transcript doesn’t leak credentials.

Host-key handling (TOFU)

On first connect, Transit AI records the device’s SHA-256 host-key fingerprint and prompts for explicit user approval. On every subsequent connect, a different fingerprint is a hard error — the user cannot override in-app. This pins the device identity for the lifetime of the record in ~/.config/transit/known_hosts.toml.

Strict cipher floor with opt-in legacy

Strict modern allowlist by default — curve25519, AES-GCM, ed25519 host keys. For Cisco vIOS / CSR1000V 16.x and older Junos releases that default to SHA1 KEX or ssh-rsa host keys, a per-device opt-in dialog surfaces the offered algorithms and requires explicit “Connect anyway” — and optionally “remember for this device”.

Console-cable transport

USB-to-serial cables (FTDI / SiLabs / Prolific) auto-detect on macOS and surface in a dedicated sidebar section. The same agent driving an SSH session can drive a console session — the same four tools work identically on a serial connection.

Not every USB-to-serial cable has been tested with Transit AI, but this one has.

AI agent

Four abilities — exactly four

The AI has a fixed, four-item menu and can’t gain a fifth at runtime:

  1. List your open sessions — names only, no scrollback content.
  2. Read the recent output of a session — with credentials stripped first (see Redaction filter below).
  3. Propose a command for you to approve — the AI cannot run anything on its own; every proposal passes the per-vendor permit list and your explicit click.
  4. Ask you a clarifying question.

Adding a fifth ability requires an actual code change we ship — a prompt-injected or jailbroken model cannot invent one at runtime.

Per-vendor permit list

Every command the AI proposes is checked against a per-vendor permit list before you ever see an approval prompt. The list spells out which read-only commands the AI is allowed to suggest; anything not on it — configure, write, delete, shell escapes like start shell or tclsh — is rejected, and the AI is told it can’t run that command. See Vendor coverage for the per-vendor breakdown.

Approval click

Even commands the permit list allows require your explicit click. The approval dialog cannot be dismissed by Enter, Escape, or clicking outside. You can opt into an “always allow this pattern in this chat” shortcut, but only for commands the permit list already allows — the permit check still runs on every command, and a denied command stays denied regardless of any shortcut you’ve saved.

Redaction filter

Device output passes through Transit AI’s redaction layer before the AI sees it. PEM blocks, encrypted password lines (enable secret, username password 7, BGP MD5 keys, OSPF auth keys), AWS keys, JWTs, and other secret-shaped tokens are stripped and replaced with placeholders like [REDACTED:pem#1]. The #N ordinal is per-conversation: same number = same secret bytes, so the AI can reason about credential equivalence without ever seeing the value.

Bounded investigations

Each investigation is capped at 12 back-and-forth rounds, 50,000 tokens, or 120 seconds of wall clock — whichever happens first. Hitting any cap ends the investigation with a chat message saying which one fired. You can also stop a running investigation manually from the chat panel.

Identity & secrets

Sign-in through your browser

Transit AI signs you in by launching your system browser, then receiving your session back through a transit:// link. You stay signed in across restarts; sessions refresh quietly in the background.

Secrets in your OS keyring

SSH passwords live in your OS’s native keyring — macOS Keychain, Windows Credential Manager, Linux Secret Service, or your running SSH agent. The desktop binary holds no secret in process memory longer than needed to authenticate a session, and never serializes one to disk.

BYOK (Pro and Max)

Bring your own Anthropic or OpenAI key — Transit AI reads it from your OS keychain per request, passes it through to the AI provider, and forgets it. Keys are never stored or logged on our cloud. Available as a $100 one-time unlock on Pro and Max tiers; the unlock stays attached for the lifetime of your subscription. See Bring your own provider key for setup.

What Transit AI doesn’t do

  • No write operations on devices except through the per-vendor permit list AND your explicit click. Always both, never either.
  • No telemetry by default. If enabled, only operational metadata (token counts, latencies); never command bytes or prompt content.
  • No third-party analytics scripts. The marketing site (this site) serves no tracking scripts to its visitors.