Skip to content
phynite-lab
Phynite DocumentationDownload

AI provider connections on your computer

Local AI uses the provider CLI you choose. It is independent from Phynite Cloud login and does not use a hosted Phynite AI service.

Complete guide

Connect an account

Open full resolution

Signed-out demo: complete the official provider flow on your computer. No account or quota is simulated.

Signed-out demo: complete the official provider flow on your computer. No account or quota is simulated.
Codex provider icon
Connect through the provider CLI you already use.
Antigravity provider icon
Provider authentication stays with the official local CLI.
  1. Install and authenticate the official provider CLI on this computer.
  2. Open Settings → AI provider accounts and choose Codex or Antigravity.
  3. Complete authentication through the provider’s own flow. An existing supported CLI login can be reused without importing its cookie or session files.
  4. Keep the application open while model discovery and the capability probe run. The page selects only models that pass the supported text, streaming, and tool checks.

Provider, model, and limits

The local app uses the single signed-in profile managed by the official provider CLI. A failed or rate-limited request never silently changes provider or account.

Usage cards show only telemetry reported by the provider: model group, session or weekly percentage, window, and reset time when available. A missing report stays unavailable; the app never invents token counts, balances, or reset dates.

Model availability can change with the provider entitlement. Cloud model settings do not control local provider accounts.

Security and unsupported states

  • Provider credentials stay in the provider-managed CLI or local credential store and are kept out of browser storage, logs, project archives, and Cloud Sync. The local app does not accept a gateway URL or gateway token.
  • The local bridge runs on loopback with shell, MCP, plugin, browser, and unverified network actions disabled. Canvas changes still require the existing approval and validation flow.
  • If authentication, discovery, streaming, or tool verification fails, the provider remains visibly disconnected or unavailable until you fix it. There is no automatic provider fallback.
  • AI provider access is separate from scientific runtime installation and separate from Phynite Cloud login.

Related topics

Your privacy

Cookie preferences

Choose whether Phynite may use optional analytics in this browser. You can change this anytime.

Waiting for your choice

This choice applies to this browser, including your workspace.

Read the privacy notice