proxyman-download-setup

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Proxyman Download & Setup

Proxyman 下载与安装配置

Guide the user through installing and launching Proxyman. This skill is shell-first because Proxyman and its MCP tools may not be available yet.

引导用户完成Proxyman的安装与启动。本技能优先使用命令行，因为此时Proxyman及其MCP工具可能尚未可用。

Operating Rules

操作规则

Do not use Proxyman MCP tools until Proxyman is installed, launched, and MCP is configured.
Do not hardcode app versions. Use Proxyman's latest release redirects.
On Windows, prefer PowerShell. If the active shell is not PowerShell, wrap PowerShell snippets with
```
powershell.exe -Command '...'
```
.
Only install the macOS Helper Tool when system proxy automation is needed or the user asks for it.
Only install a root certificate when the user needs HTTPS decryption. Basic HTTP capture and app installation do not require certificate installation.
On Windows and Linux, launch Proxyman at least once before MCP setup so the app can expose or prepare the bundled MCP bridge.

仅在Proxyman安装、启动且MCP配置完成后，才可使用Proxyman MCP工具。
不要硬编码应用版本，使用Proxyman的最新版本重定向链接。
在Windows系统上优先使用PowerShell。若当前使用的不是PowerShell，需将PowerShell代码片段用
```
powershell.exe -Command '...'
```
包裹。
仅当需要系统代理自动化或用户明确要求时，才安装macOS辅助工具（Helper Tool）。
仅当用户需要HTTPS解密时，才安装根证书。基础的HTTP捕获和应用安装无需安装证书。
在Windows和Linux系统上，配置MCP前至少启动一次Proxyman，以便应用暴露或准备好捆绑的MCP桥接程序。

Phase 1: Check Existing Installation

阶段1：检查现有安装情况

macOS

bash

if [ -d "/Applications/Proxyman.app" ]; then
  VERSION=$(/usr/libexec/PlistBuddy -c "Print CFBundleShortVersionString" "/Applications/Proxyman.app/Contents/Info.plist" 2>/dev/null)
  echo "INSTALLED: ${VERSION:-unknown}"
elif mdfind 'kMDItemCFBundleIdentifier == "com.proxyman.NSProxy"' | grep -q "Proxyman.app"; then
  echo "INSTALLED: found via Spotlight"
else
  echo "NOT_INSTALLED"
fi

bash

if [ -d "/Applications/Proxyman.app" ]; then
  VERSION=$(/usr/libexec/PlistBuddy -c "Print CFBundleShortVersionString" "/Applications/Proxyman.app/Contents/Info.plist" 2>/dev/null)
  echo "INSTALLED: ${VERSION:-unknown}"
elif mdfind 'kMDItemCFBundleIdentifier == "com.proxyman.NSProxy"' | grep -q "Proxyman.app"; then
  echo "INSTALLED: found via Spotlight"
else
  echo "NOT_INSTALLED"
fi

Windows (PowerShell)

powershell

$installed = Get-ItemProperty `
  "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
  "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
  "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" `
  -ErrorAction SilentlyContinue |
  Where-Object { $_.DisplayName -like "*Proxyman*" }

if ($installed) {
  Write-Host "INSTALLED: $($installed.DisplayVersion)"
} else {
  Write-Host "NOT_INSTALLED"
}

powershell

$installed = Get-ItemProperty `
  "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
  "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*",
  "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" `
  -ErrorAction SilentlyContinue |
  Where-Object { $_.DisplayName -like "*Proxyman*" }

if ($installed) {
  Write-Host "INSTALLED: $($installed.DisplayVersion)"
} else {
  Write-Host "NOT_INSTALLED"
}

Linux

bash

if command -v proxyman >/dev/null 2>&1; then
  echo "INSTALLED: $(command -v proxyman)"
elif ls "$HOME"/Downloads/Proxyman*.AppImage "$HOME"/Downloads/proxyman*.AppImage >/dev/null 2>&1; then
  echo "INSTALLED: AppImage in Downloads"
else
  echo "NOT_INSTALLED"
fi

If Proxyman is already installed, launch it and continue to preparation. If the user needs the latest build, download using the platform redirect below.

bash

if command -v proxyman >/dev/null 2>&1; then
  echo "INSTALLED: $(command -v proxyman)"
elif ls "$HOME"/Downloads/Proxyman*.AppImage "$HOME"/Downloads/proxyman*.AppImage >/dev/null 2>&1; then
  echo "INSTALLED: AppImage in Downloads"
else
  echo "NOT_INSTALLED"
fi

若Proxyman已安装，启动它并继续后续准备步骤。若用户需要最新版本，可通过下方对应平台的重定向链接下载。

Phase 2: Download And Install

阶段2：下载与安装

macOS: Homebrew Preferred

macOS：优先使用Homebrew

If Homebrew is installed, use the cask:

bash

brew install --cask proxyman

If Homebrew is unavailable or the user prefers a direct download, use the latest DMG redirect:

bash

curl -L "https://proxyman.com/release/osx/Proxyman_latest.dmg" -o "$HOME/Downloads/Proxyman.dmg"
hdiutil attach "$HOME/Downloads/Proxyman.dmg" -nobrowse
cp -R "/Volumes/Proxyman/Proxyman.app" /Applications/
hdiutil detach "/Volumes/Proxyman"

If the volume name differs, list attached volumes and copy from the mounted Proxyman volume:

bash

ls /Volumes

若已安装Homebrew，使用cask安装：

bash

brew install --cask proxyman

若未安装Homebrew或用户偏好直接下载，使用最新DMG重定向链接：

bash

curl -L "https://proxyman.com/release/osx/Proxyman_latest.dmg" -o "$HOME/Downloads/Proxyman.dmg"
hdiutil attach "$HOME/Downloads/Proxyman.dmg" -nobrowse
cp -R "/Volumes/Proxyman/Proxyman.app" /Applications/
hdiutil detach "/Volumes/Proxyman"

若卷名称不同，列出已挂载的卷并从对应的Proxyman卷中复制：

bash

ls /Volumes

Windows

The Windows endpoint name ends in

.dmg

for legacy reasons, but it redirects to the latest Windows installer. The installer is an NSIS one-click installer and normally launches Proxyman after completion.

powershell

$installer = "$env:USERPROFILE\Downloads\ProxymanSetup.exe"
Invoke-WebRequest "https://proxyman.com/release/windows/Proxyman_latest.dmg" -OutFile $installer -MaximumRedirection 5
Start-Process $installer -ArgumentList "/S" -Wait

If silent installation fails, run the installer interactively:

powershell

Start-Process $installer -Wait

Windows端点名称以

.dmg

结尾是历史遗留问题，但会重定向到最新的Windows安装程序。该安装程序是NSIS一键式安装程序，通常会在安装完成后启动Proxyman。

powershell

$installer = "$env:USERPROFILE\Downloads\ProxymanSetup.exe"
Invoke-WebRequest "https://proxyman.com/release/windows/Proxyman_latest.dmg" -OutFile $installer -MaximumRedirection 5
Start-Process $installer -ArgumentList "/S" -Wait

若静默安装失败，以交互模式运行安装程序：

powershell

Start-Process $installer -Wait

Linux

Download the latest AppImage redirect, make it executable, and launch it:

bash

curl -L "https://proxyman.com/release/linux/proxyman_latest" -o "$HOME/Downloads/Proxyman.AppImage"
chmod +x "$HOME/Downloads/Proxyman.AppImage"
nohup "$HOME/Downloads/Proxyman.AppImage" >/dev/null 2>&1 &

The packaged Linux app prepares its MCP bridge on first launch. After Proxyman has opened, the stable bridge path should be:

bash

BRIDGE_PATH="${XDG_CONFIG_HOME:-$HOME/.config}/Proxyman/bin/mcp-server"
test -x "$BRIDGE_PATH" && echo "MCP_BRIDGE: $BRIDGE_PATH"

下载最新的AppImage重定向文件，赋予执行权限并启动：

bash

curl -L "https://proxyman.com/release/linux/proxyman_latest" -o "$HOME/Downloads/Proxyman.AppImage"
chmod +x "$HOME/Downloads/Proxyman.AppImage"
nohup "$HOME/Downloads/Proxyman.AppImage" >/dev/null 2>&1 &

打包的Linux应用会在首次启动时准备好MCP桥接程序。Proxyman启动后，稳定的桥接程序路径应为：

bash

BRIDGE_PATH="${XDG_CONFIG_HOME:-$HOME/.config}/Proxyman/bin/mcp-server"
test -x "$BRIDGE_PATH" && echo "MCP_BRIDGE: $BRIDGE_PATH"

Phase 3: Launch Proxyman

阶段3：启动Proxyman

macOS

bash

open -a "Proxyman"
sleep 10

bash

open -a "Proxyman"
sleep 10

Windows (PowerShell)

powershell

$candidates = @(
  "$env:LOCALAPPDATA\Programs\Proxyman\Proxyman.exe",
  "C:\Program Files\Proxyman\Proxyman.exe",
  "C:\Program Files (x86)\Proxyman\Proxyman.exe"
)
$proxymanExe = $candidates | Where-Object { Test-Path $_ } | Select-Object -First 1
if ($proxymanExe) {
  Start-Process $proxymanExe
  Start-Sleep 10
} else {
  Write-Host "Proxyman executable not found. Launch Proxyman from the Start menu, then continue."
}

After launch, the bundled MCP bridge should live next to the app executable. For the default per-user install:

powershell

$bridge = "$env:LOCALAPPDATA\Programs\Proxyman\mcp-server.exe"
if (Test-Path $bridge) { Write-Host "MCP_BRIDGE: $bridge" }

powershell

$candidates = @(
  "$env:LOCALAPPDATA\Programs\Proxyman\Proxyman.exe",
  "C:\Program Files\Proxyman\Proxyman.exe",
  "C:\Program Files (x86)\Proxyman\Proxyman.exe"
)
$proxymanExe = $candidates | Where-Object { Test-Path $_ } | Select-Object -First 1
if ($proxymanExe) {
  Start-Process $proxymanExe
  Start-Sleep 10
} else {
  Write-Host "未找到Proxyman可执行文件。请从开始菜单启动Proxyman，然后继续操作。"
}

启动后，捆绑的MCP桥接程序应位于应用可执行文件旁。对于默认的按用户安装方式：

powershell

$bridge = "$env:LOCALAPPDATA\Programs\Proxyman\mcp-server.exe"
if (Test-Path $bridge) { Write-Host "MCP_BRIDGE: $bridge" }

Linux

bash

if command -v proxyman >/dev/null 2>&1; then
  nohup proxyman >/dev/null 2>&1 &
else
  nohup "$HOME/Downloads/Proxyman.AppImage" >/dev/null 2>&1 &
fi
sleep 10

If the Linux MCP bridge path is missing after launch, ask the user to open Settings > MCP and enable MCP Server, then relaunch Proxyman so the AppImage can copy and

chmod

the bridge into the config folder.

bash

if command -v proxyman >/dev/null 2>&1; then
  nohup proxyman >/dev/null 2>&1 &
else
  nohup "$HOME/Downloads/Proxyman.AppImage" >/dev/null 2>&1 &
fi
sleep 10

若启动后Linux系统的MCP桥接程序路径缺失，请用户打开设置 > MCP并启用MCP Server，然后重新启动Proxyman，以便AppImage将桥接程序复制到配置文件夹并设置

chmod

权限。

Windows And Linux MCP Bridge Notes

Windows与Linux MCP桥接程序说明

Windows and Linux Proxyman builds use the same MCP model as macOS: an AI agent launches a bundled

mcp-server

process over stdio, and that bridge talks to the running local Proxyman app through an authenticated localhost handshake.

Use these bridge paths when moving on to

proxyman-mcp-setup

Platform	Bridge path
Windows default install	`%LOCALAPPDATA%\Programs\Proxyman\mcp-server.exe`
Windows custom install	`mcp-server.exe` in the same folder as `Proxyman.exe`
Linux AppImage	`${XDG_CONFIG_HOME:-$HOME/.config}/Proxyman/bin/mcp-server`

Do not configure agents to use

Proxyman.exe

or the

.AppImage

as the MCP command. The command must be the stdio bridge executable.

Windows和Linux版Proxyman采用与macOS相同的MCP模式：AI Agent通过标准输入输出启动捆绑的

mcp-server

进程，该桥接程序通过经过身份验证的本地主机握手与运行中的本地Proxyman应用通信。

进行

proxyman-mcp-setup

时，请使用以下桥接程序路径：

平台	桥接程序路径
Windows默认安装	`%LOCALAPPDATA%\Programs\Proxyman\mcp-server.exe`
Windows自定义安装	`Proxyman.exe` 同目录下的 `mcp-server.exe`
Linux AppImage	`${XDG_CONFIG_HOME:-$HOME/.config}/Proxyman/bin/mcp-server`

请勿将代理配置为使用

Proxyman.exe

或

.AppImage

作为MCP命令，必须使用标准输入输出桥接程序可执行文件。

Phase 4: Prepare Proxy Capture

阶段4：准备代理捕获

Proxyman can capture different targets in different ways. Ask what the user wants to capture before changing system state.

Desktop apps and browsers often use the system proxy.
CLI runtimes such as Node.js, Python, Ruby, and Go may need Proxyman Automatic Setup or Manual Setup.
Localhost traffic may need Reverse Proxy because many clients bypass the system proxy for localhost.
iOS apps behind VPNs may need Atlantis instead of classic proxy capture.

Proxyman可通过不同方式捕获不同目标的流量。在修改系统状态前，请询问用户想要捕获的目标类型：

桌面应用和浏览器通常使用系统代理。
Node.js、Python、Ruby、Go等CLI运行时可能需要Proxyman自动设置或手动设置。
本地主机流量可能需要反向代理（Reverse Proxy），因为许多客户端会绕过系统代理访问本地主机。
VPN后的iOS应用可能需要Atlantis而非传统代理捕获方式。

macOS Helper Tool

macOS辅助工具（Helper Tool）

The Helper Tool is macOS-only. Install it when the user wants Proxyman to override system proxy settings reliably across network interfaces, or when system proxy automation fails because privileged network settings are required.

Tell the user that macOS may show a visible password or approval dialog, then run:

bash

open -a "Proxyman" --args --install-privileged-components

If macOS shows an approval prompt in System Settings, ask the user to approve Proxyman's Helper Tool and retry the system proxy action.

辅助工具仅适用于macOS。当用户希望Proxyman可靠地跨网络接口覆盖系统代理设置，或因需要特权网络设置导致系统代理自动化失败时，安装该工具。

告知用户macOS可能会显示可见的密码或授权对话框，然后运行：

bash

open -a "Proxyman" --args --install-privileged-components

若macOS在系统设置中显示授权提示，请用户批准Proxyman的辅助工具，然后重试系统代理操作。

Root Certificate

根证书

Root certificate setup is required for HTTPS decryption, not for merely installing Proxyman.

Preferred sequence:

Finish app installation.
Configure MCP with
```
proxyman-mcp-setup
```
if the user wants agent automation.
Use
```
get_certificate_status
```
.
If HTTPS decryption is needed and the certificate is missing or untrusted, use
```
install_certificate
```
through MCP or Proxyman's Certificate menu.

Without MCP, guide the user to Proxyman's in-app Certificate menu and choose the setup path for the target platform.

On Windows, automatic certificate installation may show a UAC prompt and can use an elevated

certutil

flow. On Linux, automatic trust-store installation is designed for Ubuntu/Debian, Fedora/RHEL, openSUSE/SUSE, and Arch-family systems; unsupported distros may require manual trust-store commands from the Proxyman UI.

Some Proxyman builds expose

proxyman-cli

. Use it only after confirming it exists with

command -v proxyman-cli

Get-Command proxyman-cli

. For custom root certificates only, a CLI build that supports root import can use:

bash

proxyman-cli install-root-cert /path/to/custom-root.p12 --password "password" --trust

Do not use the custom root certificate CLI command for the default Proxyman-generated root CA.

根证书设置仅在需要HTTPS解密时才需进行，并非安装Proxyman的必要步骤。

推荐流程：

完成应用安装。
若用户需要Agent自动化，使用
```
proxyman-mcp-setup
```
配置MCP。
使用
```
get_certificate_status
```
检查证书状态。
若需要HTTPS解密且证书缺失或未受信任，通过MCP或Proxyman的证书菜单使用
```
install_certificate
```
安装证书。

若无MCP，引导用户进入Proxyman应用内的证书菜单，并选择对应目标平台的设置路径。

在Windows系统上，自动安装证书可能会显示UAC提示，可使用提升权限的

certutil

流程完成。在Linux系统上，自动信任存储安装适用于Ubuntu/Debian、Fedora/RHEL、openSUSE/SUSE和Arch系列系统；不支持的发行版可能需要从Proxyman界面执行手动信任存储命令。

部分Proxyman版本提供

proxyman-cli

。仅在通过

command -v proxyman-cli

或

Get-Command proxyman-cli

确认其存在后才可使用。对于自定义根证书，支持根证书导入的CLI版本可使用：

bash

proxyman-cli install-root-cert /path/to/custom-root.p12 --password "password" --trust

请勿对Proxyman生成的默认根CA使用自定义根证书CLI命令。

Phase 5: Suggest MCP Setup

阶段5：建议配置MCP

After Proxyman is installed and running, offer to configure MCP:

text

Proxyman is installed and running. The next step is to connect your AI agent to Proxyman MCP so it can inspect traffic, manage rules, install certificates when needed, and use Proxyman setup guidance. Use the proxyman-mcp-setup skill next.

Proxyman安装并运行后，建议配置MCP：

text

Proxyman已安装并运行。下一步是将您的AI Agent连接到Proxyman MCP，使其能够检查流量、管理规则、在需要时安装证书，并使用Proxyman设置向导。请接下来使用proxyman-mcp-setup技能。

Troubleshooting

故障排除

Issue	Action
macOS DMG volume name is different	Run `ls /Volumes` , find the Proxyman volume, and copy `Proxyman.app` from it.
macOS app will not open	Run `xattr -cr "/Applications/Proxyman.app"` and launch again.
Windows SmartScreen blocks installer	Ask the user to approve the installer from the visible Windows prompt.
Linux AppImage does not run	Ensure it is executable and that required AppImage/FUSE dependencies are installed.
System proxy cannot be enabled on macOS	Install or approve the Helper Tool, then retry.
HTTPS traffic is still opaque	Install and trust the root certificate, then enable SSL Proxying for the target host.

问题	解决方法
macOS DMG卷名称不同	运行 `ls /Volumes` ，找到Proxyman卷，从中复制 `Proxyman.app` 。
macOS应用无法打开	运行 `xattr -cr "/Applications/Proxyman.app"` 后重新启动。
Windows SmartScreen阻止安装程序	请用户从弹出的Windows提示中批准安装程序。
Linux AppImage无法运行	确保其已赋予执行权限，且已安装所需的AppImage/FUSE依赖。
macOS系统代理无法启用	安装或批准辅助工具后重试。
HTTPS流量仍无法解密	安装并信任根证书，然后为目标主机启用SSL代理。