OpenAI
Direct API key
Limitcode supports direct APIs, account sign-in, existing CLI sessions, and local OpenAI-compatible runtimes. Each route has different billing, privacy, and account-risk boundaries.
Requests go from the plugin to the provider or gateway you select. Usage, rates, limits, and model availability remain with that service.
Direct API key
Direct API key
Google AI API key
Models enabled for your account
Direct OpenAI-compatible API
Direct OpenAI-compatible API
Groq, xAI, Together, and custom gateways
These integrations depend on provider-controlled accounts and service behavior. Availability, quotas, and compatibility can change independently of Limitcode.
Sign in with GitHub. Availability and model access depend on an eligible Copilot account or subscription.
Uses an OpenAI browser login and a local callback. Account eligibility, quotas, and endpoint behavior are controlled by OpenAI and may change.
Uses Google OAuth and Antigravity/Code Assist service behavior to access models available to the signed-in account.
CLI bridges require the provider's command-line tool to be installed and authenticated before Limitcode starts the task.
Uses an existing local `claude login` session.
Uses an existing local `codex login` session.
CLI-backed providers may run their own internal agent loop and tools, outside some Limitcode permission controls.
Local inference can remain on your machine when the endpoint and model are local. Tool calling depends on the endpoint and model implementation.
Default local OpenAI-compatible endpoint
Local server and models managed by LM Studio
Local or remote provider gateway
User-supplied OpenAI-compatible base URL
Prompts and any file context or tool results included in a request are sent to the selected provider or endpoint. Credentials are stored in Sublime Text settings, not an operating-system keychain. Review the provider's terms before connecting a work or primary personal account.
Return to Limitcode Pro →