Where keys live
Connected-provider credentials are managed locally by the desktop engine. They are distinct from the credentials used for your EDU account; storage is not uniformly the macOS Keychain.
EDU-provided model access and your own provider accounts are two separate ways to work. The platform catalog is shown first; the table below describes optional integrations.
Access through your EDU account, without a separate provider key. Account limits apply.
autotrust/turbo-1.0openai/gpt-6-lunaanthropic/claude-haiku-5.5deepseek/deepseek-v4-flashzai/glm-5.3-flashautotrust/jev-27b-vlConnected-provider credentials are managed locally by the desktop engine. They are distinct from the credentials used for your EDU account; storage is not uniformly the macOS Keychain.
Vendor coding plans have terms: quotas reset on a schedule and background use is often disallowed. Guru EDU follows them — plan models are not used for background jobs, and quota exhaustion is reported with the vendor's reset time instead of silently billing a paid balance.