Use your Claude subscription

Kadmo agents run Claude Code. By default they run it on the Kadmo agent app, which calls Kadmo's models and pays per token from your Kadmo credit. When your plan includes own model providers, you can instead sign agents in with your own Claude subscription: Claude Code then runs on that Claude account, and the jobs spend nothing from your Kadmo credit. This page explains who can do this, where it lives in the app, the sign-in steps, and what changes for billing.

Who can use it

You need	Why
A plan with own model providers	The subscription app is one of the "direct" agent apps that carry your own account with a model provider (see Your own keys)
The admin role	Admins manage agent apps, and signing in happens on the agent's live desktop, which only admins open
A Claude account with a subscription	Claude Code signs in to it with /login. A dedicated Claude account for your agents keeps their usage and rate limits apart from people's own

Step 1: Put the agents on the subscription app

Open BYOK in the settings sidebar, then the Agent Apps tab. With own model providers in your plan, the list includes the built-in Claude Code (subscription) app ("Claude Code signed in with a Claude subscription (/login). No provider config needed."). You can also add your own with Add agent app and the provider Anthropic subscription.

Then decide which agents use it:

To move	Do this
Every agent without an app of its own	Pin the subscription app on each agent (below): an agent without an app runs on the account's provider, Kadmo or your own key, never on an agent app
One agent	On the agent's page, Configuration → Agent apps → Pinned app: pick the subscription app
New cloud agents	Pick it as the Agent app in the wizard's Software step

A single run can still name another app; the order is the run's app, then the agent's pinned app, then the account's provider.

Step 2: Sign each agent in once

Claude Code keeps its sign-in on the machine, so each agent signs in once and stays signed in across jobs and restarts. Until it does, its first job stops at Not logged in, and its card shows Claude Code · not signed in.

When online agents run a subscription app and some are not signed in, Agent Fleet shows the Sign in Agent Apps strip: "No agent is signed in to Claude Code (subscription) … yet — first jobs stop at Not logged in. Sign in once per agent on its Live desktop (~5 min); the credential stays on the machine." It walks you through five steps for the first agent that still needs it:

1. Run a job. Click Run a job at agent ▸. The strip starts the light Pull Workspace Repos job on that agent at once. Claude Code starts, then stops at Not logged in.
2. Connect. Click Open Live desktop ↗ to see the agent's screen.
3. Log in. Click into the terminal, type /login (Copy /login copies it) and choose option 1, the Claude subscription.
4. Authorize. Chrome on the agent opens claude.ai. Sign in with the Claude account and approve Claude Code.
5. Done. The job resumes, and the sign-in survives restarts.

The strip counts "N of M online agents signed in" and points at the next agent each time one finishes; after the first sign-in it shrinks to a single row with Open Live desktop · agent. When every online agent is signed in, it disappears. You can hide it with ✕ (remembered per account in your browser). The card chips and the Signed in on N of M agents count on the Agent Apps page show the same state.

What happens to credit and billing

	Kadmo app	Your Claude subscription
Who pays for the model	Your Kadmo credit, per token	Your Claude subscription
Kadmo credit held at a job's start	Yes, an estimate	None
Limits	Your credit and any budgets you set	The Claude account's own usage and rate limits

Each job is billed by the app it runs on, so a fleet can mix both: jobs on the Kadmo app keep spending credit, jobs on the subscription app do not. Your Kadmo plan itself is unchanged. More on credit in The Kadmo provider.

Switching back or signing out

• Back to Kadmo: pin the Kadmo app on the agent, or set its pinned app back to Account default (none pinned) so it runs on the account's provider. The next job runs on it; nothing on the agent needs to change.
• Sign an agent out: remove the Claude Code connection in the Claude account's settings on claude.ai. The agent asks for /login again on its next job on the subscription app.

Troubleshooting

Symptom	Fix
The Agent Apps tab says own keys come with another plan	Your plan does not include own model providers: Talk to us
No Sign in Agent Apps strip	It shows only to admins, only for online agents on a subscription app that are not signed in yet, and not after you dismissed it in this browser. Sign in from the agent's page instead
A card says "an admin has to sign in once on this agent's Live desktop"	Ask an account admin to do Step 2
The job does not start	The agent may be on hold: open it and click Resume now
The terminal still shows Not logged in	Run /login again in the terminal and finish the browser step

Related

• Agents: agent apps and effort tiers
• The Kadmo provider: credit, models and what your plan decides