mirror of
https://github.com/hanzoai/dev.git
synced 2026-10-25 03:32:32 +00:00
zeekay
383f8e92a9
The default provider is hanzo, yet the first screen offered a ChatGPT plan and the only device flow spoke OpenAI's proprietary /api/accounts/deviceauth. This ports the RFC 8628 device grant into code-rs — the workspace that ships; the earlier attempt landed in the vendored mirror, where it ran for nobody. Routing keys off model_provider_id, not a new flag: the config already carries the one notion of provider. openai keeps device_code_auth.rs untouched, and every branded string is provider-conditional, so that path renders exactly what it did before. The client is hanzo-cli. hanzo-app answers "client authentication failed" — it is confidential, and a CLI cannot hold a secret. Sibling brands need a public <org>-cli client provisioned before the issuer override is useful. One row, not two: the Hanzo browser loopback is not provisioned (invalid redirect_uri), and a row promising hanzo.id that opened auth.openai.com would be a lie. The device grant covers headless anyway.