Capture and diff configs

Capture saves a command’s output as a named snapshot; diff compares two captures side by side. It’s how you catch config drift — the same show running-config before and after a change, or one device against another. The output is redacted before it’s written to disk.

Open the Captures dialog

Capture and diff live in the command palette — not a menu or a right-click:

1. Press Cmd+K (macOS) or Ctrl+K (Windows/Linux) to open the command palette.
2. Type diff, compare, capture, or drift.
3. Select “Compare captures / diff output…”. The Captures dialog opens.

Capture a command’s output

1. In the dialog, pick a live session from the dropdown.
2. Type the command (it defaults to show running-config).
3. Click Capture. Transit runs it in that session, redacts the output, and saves it as a capture stamped with the device and time.

Capturing is human input — it runs the command exactly as if you typed it, so it is not gated by the AI permit list. (That gate applies only to commands the AI agent proposes.)

Diff two captures

1. In the Compare row, pick an Old (A) capture and a New (B) capture from the two dropdowns.
2. Click Compare. A line-by-line diff renders — additions in green, removals in red, with a +N / −N count. Identical captures are labelled as such.

Because you pick any two captures, you can diff:

• The same device over time — capture show run, make a change, capture again, then diff the two.
• Two different devices — capture the same command on each and diff to find where their configs diverge.

Save and run a command collection

A collection is a named set of commands you run in one sweep — an “L3 health check”, say — capturing each command’s output for review or diffing.

1. In the Captures dialog, find the Collections section.
2. Give the collection a name and enter one command per line.
3. Click Save.
4. With a session selected, click Run next to the collection. Each command runs in turn and its output is captured.

Like capturing, a collection is human input — the same commands you’d type yourself, sequenced with output capture.

Where captures are stored

Captures are saved under your OS config directory:

• macOS — ~/Library/Application Support/Transit/captures/
• Windows — %APPDATA%\Transit\captures\
• Linux — ~/.config/Transit/captures/

The dialog footer shows the exact path. Each capture is a redacted .json file; remove any from the list with its Delete link.