Bring Your Own AI Subscription

You don’t have to run on ClusterCode’s platform AI credits. Bring your own AI credentials — either an API key or your AI subscription (your Claude or Codex OAuth login) — and your Runs, Schedules, and multi-agent orchestration will draw on your account.

Connecting your credentials

Add your credentials in Settings:

• An API key (e.g. an Anthropic or OpenAI key), or
• Your AI subscription — the OAuth login for an official CLI (Claude Code, Codex).

Once connected, Nova uses them automatically when it runs your jobs.

How it’s used — the credential cascade

When a job needs AI, ClusterCode resolves credentials in a defined order:

1. Your connected subscription / OAuth login is preferred first.
2. Your connected API key is used next.
3. Platform AI credits are the fallback when you haven’t connected anything.

So your own subscription or key is spent instead of (or before) the platform AI credits — the same cascade the Nova / AI-credits note describes. This lets you put your existing AI plan to work and keep your platform credits for everything else.

How your credentials are stored today

Credentials you connect are stored per user and encrypted at rest. They are never shared across users — your key or subscription authenticates only your own jobs. This applies to both Cloud workers and your own BYOM workers.

Coming soon — fully local, zero-storage passthrough

We’re building a path where, on your own BYOM worker, your existing local CLI login will be used directly — so the token will never leave your machine and will never be stored in our database at all. That fully zero-storage local-passthrough model is a planned capability, not yet available. Until it ships, connected credentials are stored encrypted at rest as described above.

Related

• AI Credits — platform credits and the billing cascade
• Nova — the automation agent that runs your jobs
• Workers — Cloud vs your own (BYOM) machines
• Runs · Schedules