Proxyman CLI

Use the CLI installed with the user's Proxyman build. Never assume a command hierarchy or flags from static documentation.

Discover Version-Matched Syntax

If Proxyman MCP is connected:

Call get_proxyman_cli_help with an empty command path for top-level help.
Call it again with command names only, for example export-log or rules map-local create.
Never include flags, values, pipes, redirects, or shell syntax in command_path.
Use the returned syntax, then execute an authorized operational command through the agent host's shell. The MCP helper never performs the command. If the command's only supported secret input is an argument, as with the reviewed activate command, provide a placeholder command for the user to run instead.

If MCP is unavailable:

Resolve the actual executable without changing shell profiles.
Run that executable with --help.
Run nested --help until every required argument and option is known.
If the CLI is missing, route to app installation/update or the GUI; do not substitute guessed syntax.