OpenUsage can send its provider requests through a proxy.
- Types:
socks5://,http://,https:// - Config file:
~/.openusage/config.json - Default: off, so requests follow the macOS system proxy settings
- UI: none
{
"proxy": {
"enabled": true,
"url": "socks5://127.0.0.1:10808"
}
}-
Default ports: 1080 for
socks5, 80 forhttp, 443 forhttps. Withhttps, the connection to the proxy uses TLS. -
For a proxy sign-in, put it in the URL:
http://user:pass@proxy.example.com:8080. Percent-encode an@or:inside the user name or password. Any app you run can read the file. -
OpenUsage reads the file once per launch. Quit and reopen it after a change.
-
It logs
proxy onwith the scheme, host, and port, or aproxy offerror that says what to fix. An unreadable file leaves proxying off. Neither line shows the password. See Debugging:log show --last 1h --predicate 'subsystem == "OpenUsage" AND category == "config"'
Every provider request, sign-in token exchanges included, and requests to a CLIProxyAPI hub. These don't: