Custom command-line tools

The Tools menu on the main menu bar (and the Tools submenu on the server context menu) is built from a customizable list of tools grouped into categories. Each entry runs an external program with the selected computer or session details substituted into the parameters. Out of the box the list includes a curated set of admin shortcuts; you can edit those, remove them, or add your own, so the categories and counts on your machine may differ from the screenshot and the default list below.

Where the tools come from

The list is stored in the program's SQLite settings as a tree of categories and tools, seeded on first run from a shipped commands.sql file (and re-seeded on Reset to defaults). The Tools menu rebuilds itself when the list changes; no restart is needed.

Opening the manager

Choose Tools > Manage tools from the main menu. The Manage tools dialog opens with a category tree on the left and details on the right.

Editing the list

Buttons on the toolbar:

• Add category - prompts for a name; the new category appears at the bottom.
• Add item - opens the editor for a fresh entry inside the focused category.
• Edit - opens the editor on the selected entry.
• Remove - removes the selected category or tool after confirmation. Removing a category removes every tool inside it.
• Up / Down - move the selected entry up or down to reorder it.

Tools can be reordered within a category with the Up / Down buttons or by drag and drop, and moved between categories by drag and drop.

Tool editor

The Create tool / Edit tool dialog has these fields:

• Tool name - what the menu shows.
• Command type - the kind of action the entry runs. Standard external programs use the default type; built-in actions (see below) use their own types and hide the program-name and parameters fields.
• Program name - the executable to run. A ... button next to the field opens a file picker.
• Shell operation - which Windows ShellExecute verb to invoke (open by default; runas triggers a UAC elevation prompt; other verbs depend on what's registered for the file type).
• Parameters (optional) - command-line arguments. Supports variable substitution; see below.
• Working directory (optional) - the directory the process runs in. A ... button opens a folder picker.
• Icon - pick an icon from a built-in collection; the icon is shown next to the menu item.

Variable substitution in parameters

Parameters are substituted just before the process is launched. The placeholders use percent markers and are case-insensitive:

• %computer_name% - the selected computer name.
• %computer_ip% - the resolved IP address of the computer.
• %user_name% - the user account stored on the computer entry (or the selected user session, when launched from the User sessions tab).
• %user_password% - the password stored with that account, when one is set.
• %path% - the program-name or path field of the tool itself.
• %session_id% - the selected session ID, when launched against a session or a process row.

Unknown placeholders are left in place. Empty values render as an empty string.

Built-in actions

Two entries do not run an external process; they invoke an internal dialog. The editor hides the program-name and parameters fields for these:

• Send Message - opens the Send message dialog targeted at the current selection.
• Shutdown/Restart - opens the Reboot / shutdown dialog.

In the menu they look identical to any external tool. Internally they use the %shutdown% and %send_message% markers in the Program name field.

Import, export, reset

The Manage tools dialog's menu has commands to:

• Import tools - read a previously exported file. New entries are added without removing existing ones; categories that already exist are reused.
• Export tools - write every tool and category to a file. The export dialog offers JSON, XML, and plain text formats.
• Reset to defaults - delete everything and re-import the shipped defaults.

Default tools that ship

The seed commands.sql defines 12 categories with 127 entries in total. Most are PowerShell one-liners that target the selected computer through %computer_ip% or %computer_name%. A few launch MMC snap-ins, mstsc.exe, Windows Explorer, or the Sysinternals utilities. Two are the built-in Shutdown and Send Message actions described above.

The sections below list every default tool by name with a one-line description. Each entry can be edited or deleted from Manage tools.

Network Diagnostics

Administrative Tools

PowerShell Remote

System Monitoring

Remote Desktop Services

Security & Audit

System Tools

Network Shares

Sysinternals Suite

These entries assume the Sysinternals binaries (psexec.exe, psinfo.exe, etc.) are on the program's PATH. They will not work if Sysinternals is not installed; edit the tool to point at the executable's full path.

Advanced Diagnostics

Update Management

Performance Management

Requirements

These defaults assume the target computer is reachable over WMI / WinRM and that the connecting account has administrator rights on the target. Specifically:

• WMI namespaces root\cimv2, root\cimv2\TerminalServices, and root\StandardCimv2 (for Get-Net* cmdlets) must be reachable. Open the Windows Management Instrumentation (WMI) firewall group on the target.
• WinRM must be enabled for the PowerShell Remote category (Enable-PSRemoting -Force).
• The Sysinternals Suite category needs the binaries on the path or full paths supplied in the Program name field.
• For SMB-based shortcuts (\\<ip>\c$, Get-SmbShare, Get-SmbOpenFile) the File and Printer Sharing firewall group must be allowed and the account must have administrator rights on the target.

Where a tool fails, the PowerShell window stays open (every default uses -NoExit), so you can read the error text and adjust permissions or firewall rules.