TransIT AI

Getting Started

This walkthrough takes you from the marketing page to your first AI-assisted SSH session in about five minutes.

1. Sign up

Visit the pricing page and pick a plan. The three tiers differ in how big a monthly AI budget you get; the desktop app and the security model are identical on all three. You can change tiers later from your account page, so don’t overthink the first pick.

Click Get started on the tier you want, then create an account through our hosted identity flow. Email + password works; so do GitHub, Google, and Microsoft if you’d rather single-sign-on.

2. Pay

After sign-up you land on the plan picker — your selected tier is already highlighted. Click Continue to checkout and you’ll be handed to our payment processor’s hosted checkout. Enter card details + billing address; tax is calculated automatically based on the address you enter.

The address you provide is saved to your customer record so you don’t have to re-enter it for future plan changes or BYOK purchases. We never see your card number — it lives entirely on the payment processor’s side.

3. Download

Once payment confirms, you land on a welcome page with a download button: Download Transit AI for macOS. Apple Silicon required (M1 or later); macOS 12 Monterey or newer.

Windows and Linux builds are tracked but not yet released. If that’s what you need, watch the blog for the announcement.

4. Install + launch

Open the downloaded .dmg, drag Transit AI to your Applications folder, double-click to launch. The first launch may prompt for Gatekeeper approval — that’s standard for any notarized macOS app.

You’ll see the welcome screen with a Sign in button. Click it.

5. Sign in

Sign-in opens your system browser pointed at our authentication flow. Because you signed up via the same identity provider in step 1, the browser recognizes you — one click to confirm and you’re back in the desktop app.

If something goes wrong here, the browser will tell you why. The most common cause is a stale auth session in another browser tab; closing that tab and retrying clears it.

6. Add your first device

The sidebar on the left is where your devices live. Click the + icon and fill in:

  • A name for the device (anything you want)
  • Hostname or IP address
  • SSH port (defaults to 22)
  • Username
  • An authentication method — password, key file, or 1Password/macOS SSH agent

Save. The device appears in the sidebar.

7. Connect + the trust-on-first-use prompt

Click the device to open an SSH session. If this is the first time connecting to that host, you’ll see a host-key confirmation dialog showing the SHA-256 fingerprint of the host’s key. Compare it against the value you trust (the device’s own show ssh host-keys output, your team’s documentation, etc.) and confirm.

That fingerprint is now pinned on your machine. The next time you connect, no prompt — but if the fingerprint ever changes, the connect hard-fails. No “trust again?” prompt by design; a changed fingerprint is either a re-keyed device (you’ll know because you did it) or a man-in-the-middle attempt.

8. Run a command

A terminal pane opens. It behaves like a normal SSH terminal — Tab completes, arrow keys recall history, Ctrl-C interrupts. Try a quick read: show version on Cisco IOS, show system information on Junos, show version on EOS or PAN-OS.

9. Open the chat panel and ask the AI

Toggle the chat panel on the right. The AI sees your open sessions, can read recent scrollback (with secrets filtered before they reach the model), and can propose commands for you to approve.

Try asking something like “What interfaces are up on this device?” The AI will look at scrollback, decide whether it has enough info, and either answer directly or propose a command (e.g., show interfaces brief). You’ll see an approval dialog with the exact command before anything runs.

Both the per-vendor permit list and your click are required for any command to execute. The AI cannot talk its way past either.

Where to go from here

  • Features — the rest of what’s in the app
  • Security model — how the agent firewall, permit list, and redaction work
  • Vendor coverage — which CLIs are first-class and what the per-vendor permit list allows
  • Billing & usage — how the AI budget works, what happens at your limit, BYOK
  • How-tos — practical workflows: bring your own key, split panes, find your IDs
  • FAQ — pre-purchase and operational questions