Running commands
Stop retyping the same show commands. Store them as templates, bundle them into groups, and run them from any session or device with one click.
- Create templates in Commands: name, command, category, compatible device types and tags.
- Bundle several templates into a command group for a sequential diagnostics routine (e.g. show version → show interfaces status → show log).
- From any session use the “Run template” menu; from any device use the quick-run action.
- On network gear the command is typed into the interactive shell and completion is detected from the prompt; --More-- paging is continued automatically, so long outputs never get stuck.
- Before the first automated command on a switch or router, the app prepares the shell like Netmiko: disables CLI paging for the vendor, escalates from user EXEC (SW1>) to privileged mode (SW1#) when the device supports it, and answers interactive confirmations (“Destination filename”, “[confirm]”, “[y/n]”) automatically.
- CLI errors are caught early: “% Invalid input” or “% Access denied” fail the run with the device’s own message instead of silently succeeding with junk.
- The live result streams into the terminal, and a copy lands in History with exit code and duration.
Tip
Long outputs never get stuck: --More-- paging is continued automatically, and the command is considered done when the shell prompt returns.
Note
If a command times out, the app interrupts it (Ctrl+C) so the next command is never typed into a broken prompt — the shell is recovered for you.
Warning
Command groups run strictly sequentially on network gear — each command waits for the previous one to finish, so a “conf t” followed by an interface command works exactly as typed.
$ show versionCisco IOS XE Software, Version 17.9.4aSystem restarted at 02:14:33 UTC Tue Aug 11 2026SW1#