Skip to main content

Providers

Open Central Settings → Providers to manage the six supported local coding providers. The page reports installation, version, binary path, authentication, account email, and subscription details when available. You can re-check providers, enable or disable them, and hide, show, or reorder models.
  • Claude Code: install with npm install -g @anthropic-ai/claude-code; sign in with claude login.
  • Codex CLI: install with npm install -g @openai/codex; sign in with codex login.
  • Cursor Agent: install with curl https://cursor.com/install -fsS | bash; sign in with cursor-agent login.
  • Grok CLI: install with curl -fsSL https://x.ai/cli/install.sh | bash; sign in with grok agent --reauth.
  • OpenCode: install with npm install -g opencode-ai; sign in with opencode auth login.
  • Antigravity CLI: install with curl -fsSL https://antigravity.google/cli/install.sh | bash; sign in by running agy.
Provider and model visibility controls what appears in chat model pickers and provider-specific skill lists.

Provider usage

Open Central Settings → Usage to see available provider quota windows and reset times. Aiola combines provider-specific live and local sources:
  • Claude OAuth quota data plus local Claude session and statistics snapshots
  • Codex live usage from the authenticated ChatGPT usage endpoint
  • Cursor period usage, plan, credits, balance, and request usage using local Cursor authentication
  • Grok live web quota data
  • OpenCode Go costs from its local usage database
  • Antigravity quota buckets from the local CLI’s loopback service
The combined provider response is cached for 20 seconds. Use Refresh to bypass that response cache and request current data; some provider-specific safety caches or backoffs can still apply.

Analytics usage

When hosted Analytics is configured, the Usage page adds an Analytics events card. All websites shows current-cycle events against the monthly quota and its reset date. Each site below it shows its event count and share of the cycle total. Use Refresh to update both provider and Analytics usage. If the monthly event limit is exceeded, Analytics dashboards lock until an upgrade or the next reset. Collection continues in the background and no data is lost.