The bundled entry point is a user-run CLI, and its credential flow requests a Patch API key through a browser-approved device login. The reported redirect is explained by the explicit PCH_API_URL or saved account origin configuration, not a fixed unofficial gateway.
Static reason
One or more suspicious static signals were detected.
Trigger
A user invokes the `pch` command; creating a login key requires running `pch login` and approving the device flow.
Impact
No malicious impact identified; credentials are used for the selected Patch API.
Mechanism
The CLI sends its Patch token to the selected API origin, which defaults to Patch production or staging and may be configured by the user. Login stores the returned key and any nondefault origin.
Evidence
~/.pch/config.json (or the path set by PCH_CONFIG)
Network endpoints5
patch.ggstaging.patch.gglocalhost:3000git.patch.gggit-staging.patch.gg