feat(auth): pause providers with a KDL `disabled` rule; pause Google Antigravity by H4vC · Pull Request #18622 · can1357/oh-my-pi

· GitHub

2 min read Original article ↗

What

Antigravity sign-ins from omp were getting people's Google accounts restricted, so this pauses the provider through a KDL disabled rule instead of signing anyone out: nothing can reach it any more, and the code and stored logins stay in place for when it is safe again.

Adds a disabled "<reason>" auth rule (rules/auth/<id>.kdl). A paused provider is left out of every login list, AuthStorage.oauth.login refuses it, the credential pool caches none of its stored rows (they stay on disk untouched), every key source (runtime, models.yml, stored, broker, env) resolves nothing, and the request funnel (streamDispatch) and generateImage throw ProviderDisabledError with the reason even when a key is passed directly. Credential health checks skip it. Google Antigravity is paused with that rule; its code stays, and deleting the one line turns it back on with stored logins intact.

Why

Pausing via policy keeps the code and users' logins, needs no sign-out migration, and covers paths a login-list flag would not (extension/SDK login, models.yml/runtime keys, old auth-broker servers).

Testing

  • New packages/ai/test/provider-disabled.test.ts: stored and runtime keys resolve nothing, request-time lookup throws ProviderDisabledError, a request with a directly passed key fails naming the reason, login is refused, and the stored key returns unchanged once re-enabled.
  • Compiler test: the reason compiles; a blank reason is rejected.
  • Real CLI: omp login google-antigravity is refused; the login list drops Antigravity and keeps Gemini CLI.
  • Antigravity transport/ranking/discovery/image tests run with the provider marked enabled (code kept for re-enable); two tests that used Antigravity only as an example provider now use google / google-gemini-cli.
  • Remaining local failures are pre-existing: completion-retention, cursor-proxy-env and cursor-transport-error reproduce on a clean HEAD checkout; usage-cli trips on the local pi-natives version warning.

  • bun check passes
  • Tested locally
  • CHANGELOG updated with the required attribution (if user-facing; internal issue fixes use issue links, external contributions add the PR link and contributor credit after creation)