Proxyman License Management

Proxyman License Management

Handle license tasks with minimal secret exposure and an explicit distinction between the current app, proxyman-cli, and the web License Manager.

Verify Current Official Guidance

Before giving entitlement, seat-count, renewal, supported-platform, or portal instructions:

1. Fetch https://docs.proxyman.com/llms.txt.
2. Fetch the current License and License Manager .md pages listed there.
3. Follow the License Manager access-link URL from the freshly fetched official page. Do not hardcode or guess the portal domain because official Proxyman domains and redirects can change.
4. Avoid hardcoding prices, device allowances, subscription terms, or trial terms; these can change.

Read license workflows for operation-specific checks.

Protect The License Key

Treat a Proxyman license key, purchase email, activation response, and License Manager access link as secrets.

• Never repeat the full key in chat, logs, screenshots, issue text, or final output.
• Never ask the user to paste the key into chat or an agent tool call.
• Ask the user to enter a key directly in Proxyman when GUI activation is possible.
• Prefer GUI activation for ordinary use because a CLI argument may remain in shell history or appear in process inspection.
• The reviewed CLI accepts the key only as a positional argument. Never execute that form with a real key through the agent host. Discover the installed help, provide a command shape containing <LICENSE_KEY>, and have the user substitute the key and run it directly in their own terminal.
• Only reconsider agent-side CLI activation if version-matched help explicitly exposes a non-argument secret input such as stdin, a file descriptor, or an interactive prompt, and the user authorizes that method.
• Do not save the key in a script, repository, skill, environment file, or shell profile.
• Do not access the user's mailbox unless an available email connector is explicitly authorized for that task.

Route The Request

Activate This Device

Preferred GUI path:

1. Open Proxyman's License/Activate screen.
2. Have the user paste the key directly into the app.
3. Activate and verify the app shows the expected licensed state and account email.

CLI path is currently supported on macOS builds that include proxyman-cli. Use the proxyman-cli skill and discover activate --help, but do not execute the reviewed positional-argument form through the agent host. Give the user a verified command shape with <LICENSE_KEY> so they can substitute the key and run it directly in their terminal. After the command succeeds, have the user restart Proxyman before verifying the licensed state. Do not quit the app on their behalf unless they explicitly authorize it.