Skip to content
LoopCodeLabLoopCodeLab Docs

Connecting keys

LoopCodeLab runs on your own accounts. You bring your own AI provider keys and service credentials, connect them in Settings, and LoopCodeLab stores them encrypted for your account with AES-256-GCM. There is no shared middleman billing, so every build spends against your own providers and you decide exactly what is connected.

Minimum setup: connect and test one coding agent. GitHub, media, Firebase, Apple, and Windows credentials can wait until a build needs those deliveries.

Secure connection flow from a provider credential through encrypted account storage to only the selected build service
Connect → encrypt → test → use only for the selected provider and build.

Two ways to connect

Section titled “Two ways to connect”

Most coding agents accept either of two connection methods:

  • An API key. Paste the key from your provider and LoopCodeLab uses it for planning, building, or review.
  • A terminal or browser sign-in. Some agents connect through a subscription sign-in instead, such as a Claude, ChatGPT, Qwen, Kimi, or Grok plan. Settings shows the method each provider supports.

Every credential has a Test button. Use it to confirm a credential is valid before you rely on it, so a dead key never surprises you in the middle of a build.

Safe setup checklist

Section titled “Safe setup checklist”
  1. Create the credential in the provider’s own dashboard.
  2. Grant only the permissions listed in the relevant guide.
  3. Save it in LoopCodeLab Settings and run Test.
  4. Rotate or reconnect it when it expires or is exposed.
  5. Never paste a secret into a build prompt, support message, or screenshot.

Where to connect each type

Section titled “Where to connect each type”
Coding agent keysConnect Claude, Codex, Qwen, Kimi, Grok, and the other build agents.
Media & research keysImage, video, audio, and research providers for media builds.
GitHub tokenLet LoopCodeLab create a repository and push your build.
Google Play & FirebaseShip a mobile app and wire up a backend.
Apple & iOSSubmit an iOS build to App Store Connect.
Windows desktop & StorePackage a web app as a Windows installer or Store submission.