A URL is unauthenticated. It can reach routing and window actions, but not targets, per-app rules or tunnel settings.
Grammar
proxymanager://v1/<domain>/<verb>?key=valuev1 is the URL host. The path maps a/b to a.b. A bare proxymanager://v1 opens the dashboard.
Examples
| URL | Effect |
|---|---|
proxymanager://v1/routing/toggle | flip routing |
proxymanager://v1/routing/enable | turn routing on |
proxymanager://v1/ui/open?pane=settings§ion=targets | open Settings → Targets |
proxymanager://v1/ui/open?pane=dashboard | open the dashboard |
proxymanager://v1/app/activate | bring the app to the front |
From a terminal
open "proxymanager://v1/routing/toggle"
open -g "proxymanager://v1/ui/open?pane=settings§ion=targets"-g keeps the app in the background. The URL is delivered as an Apple event, so it also works from a browser link after the system asks for confirmation, from a launcher, or from Shortcuts' Open URLs action.
Rules
- At most 2 048 characters and 20 arguments; duplicate arguments are rejected.
- No user, password, port or fragment in the URL.
- Only
routing.*,ui.openandapp.activateare reachable. Targets, presets and app rules need a transport with identity: Shortcuts or XPC. - There is no reply channel. Use XPC when the caller needs a result.
- When external control or the URL switch is off, the command is ignored and logged.
Why targets are not here
Adding a target changes where traffic goes. From an unauthenticated URL that would be an exfiltration primitive: any link could add a host that then travels through someone else's tunnel. Routing and window actions are reversible and visible in the menu bar, so they are the exception.