Skip to main content
Version: v2.0

Use your own Claude or ChatGPT subscription

On a self-hosted deployment, an agent can use your existing harness login instead of a model API key. Mount the login in the runner, then select it on the agent.

Connect a Claude plan with a token

To run agents on a Claude Pro or Max plan, paste a token from claude setup-token instead. It needs no mount, and it works on Agenta Cloud and on self-hosted deployments. See Connect a Claude subscription.

This needs a self-hosted deployment

A mounted login authenticates the harness through a login file mounted into your runner, which only exists on a deployment you run yourself. See the self-hosting quick start.

1. Mount your login into the runner​

Log in to the harness on your machine, then mount the login into the runner container. Follow Use your own subscription for the file paths, mount configuration, and permission check.

Which login you need depends on the harness the agent uses:

HarnessLogin it reads
Claude CodeYour Claude Code login
PiYour Pi login, which also covers signing in with ChatGPT
CodexYour ChatGPT/Codex login. The runner reads it from CODEX_HOME, pointed at a read-write mount of your ~/.codex

2. Select the subscription on the agent​

A subscription is picked the same way as any other model, so there is no separate credential step.

Open the Model section in the agent's Configuration column and click the model combobox. Mounted subscriptions appear in the picker's left column alongside your API-key connections, each tagged Subscription. Click the one whose login you mounted, then click a model row under the harness that login belongs to. That sets the model, the harness, and the subscription in one go.

If the subscription is not listed, open Manage model providers at the foot of the picker and look under Subscriptions. See Choose a harness and model.

3. Keep the run local​

The login lives in the runner container, so the agent has to run there. Open Advanced, then Execution environment, and set Sandbox to Local. A Daytona sandbox never receives the login and cannot authenticate with it.

warning

Every local run can read the files mounted into the runner, including this login. Use a subscription only on a deployment you run for yourself. See Sandbox isolation and security.