# Bring your own AI You can connect your own AI through a ChatGPT plan used by Codex, a provider API key, or a provider's supported account sign-in in Settings. These options are different: the Codex conversation connection is separate from the provider list, and an API key is billed by its provider. An account sign-in uses that provider's eligibility and limits; it does not make every model free or included. Use only the settings and connection methods exposed for your account. ## Use your ChatGPT plan 1. Install or open Codex and sign in with your ChatGPT account. 2. In Nock, open **Settings → Nock AI**. 3. Turn on **Use my ChatGPT plan (Codex)** and confirm that Nock shows Codex as connected. When enabled, Nock's voice agent can use the ChatGPT plan for conversation turns. Codex plan limits and availability apply. Nock Own requires this route or your own key for conversation and does not switch silently to Nock's managed model if it fails. The conversation can use supported Nock tools through Nock's own controls. Broader desktop, browser, file, or worker jobs can hand off to Nock's full agent when the account has the required access; your desktop AI selection and the model used for that action are separate. See [Computer use](/nock/computer-use). On Nock Own, connecting Codex for the conversation brain does not sign in Nock's full agent. To hand off work to that agent on your ChatGPT plan, connect it separately under **Your own AI → Full agent** with **Sign in with ChatGPT**. See [Nock Own](/nock/nock-own). ## Use a provider key 1. Open **Settings → Providers** and choose a supported provider. 2. Add its API key using Nock's key control. Never paste a key in a chat, routine, project file, or support request. 3. In **Settings → Nock AI** or the relevant feature setting, choose **Use your own keys** when that option is available. 4. Send a small test request and check which provider is selected. Your provider bills model calls made with its key. Provider access does not unlock a Nock plan feature that your account does not include or remove fair-use protections on Nock-hosted services. Cloud-computer hosting and resources remain separate from model-provider charges. ## Use a provider's sign-in method Search for the provider in **Settings → Providers**. If its row offers **Sign in**, choose it and follow the displayed account, browser, device-code, or pasted-code instructions. Use **Open sign-in page** or **Copy sign-in link** if the browser does not open. Only paste an authorization code into Nock's designated field when that method asks for it—not into a chat. Wait for confirmation, then check the refreshed connection and test a model with a small request. If authorization fails, the error offers **Refresh providers**; check the provider's page before starting another attempt. See [Models and providers](/nock/providers) for the full sign-in and recovery steps. The provider's methods can change, and a listed provider is not a guarantee of a subscription sign-in or account access. ## Choosing the route by feature The conversation brain, background worker, speech-to-text, spoken voice, and connected apps can have separate routes. A key connected for one purpose does not necessarily serve another. For example, a DeepSeek key can provide conversation or Polished cleanup; a speech key is used for cloud dictation only when the supported provider is selected; an own text-to-speech key can provide cloud voice where enabled. Check the feature's setting and Usage view before sending sensitive or high-volume work. See [Models and providers](/nock/providers), [Nock Own](/nock/nock-own), and [Privacy and data](/nock/privacy).