Zozo Docs

Connect a Personal Subscription Credential ​

A subscription Credential is the login material Zozo uses to run your coding agent. For work on your own repositories and budget, we recommend a personal subscription. For unattended work billed to a client, we recommend a vendor API key. Both kinds are supported; your plan doesn't restrict which kind you can add.

Subscription Credentials require recorded consent to your vendor's terms. See Auth & Consent for the disclosure. Each Credential has its own name, coding Provider (Claude or Codex), and recorded health. Connecting one makes it available to Zozo; see Understanding Credentials to assign it to work.

Connect the Credential ​

  1. Open Credentials in your dashboard (#/auth), or use the credential step in Setup.
  2. In Add a Credential, enter a name such as personal-claude, choose its Provider, and select the subscription kind:
    • Claude: choose Subscription (OAuth token). Run claude setup-token where you're logged into Claude Code. It prints a long-lived token starting with sk-ant-oat01-.
    • Codex: choose Subscription (auth.json). Follow Create a Dedicated Codex Auth File to sign in separately for Zozo while keeping your local login intact.
  3. Read and accept the disclosure. It confirms that your subscription is governed by your vendor agreement and that Zozo may disable subscription Credentials if the vendor asks it to. Add Credential stays disabled until you accept.
  4. Paste the token or choose the dedicated auth file, then click Add Credential.

Keep the Codex session dedicated to Zozo

Sharing an auth file with an active local Codex session can leave either copy with a consumed refresh token when the other refreshes. Create a fresh login for Zozo and let Zozo exclusively use that session after upload.

Validate and Reconnect ​

Saving takes a few seconds while Zozo validates the Credential with the coding runtime. On success, its row appears on Credentials with an authenticated health badge and a consent timestamp. A failed validation shows an error and leaves any existing Credential unchanged.

To replace a Credential, re-enter its existing name and Provider in Add a Credential. Consent stays attached to that name. Deleting the Credential also deletes its consent; a fresh name requires fresh consent. For Codex, generate a new dedicated login for each replacement.

Set Model and Effort ​

In the Credential's row, click Tune runtime. Set Model and Effort independently for Intake + Wayfinder and Dispatch, then click Save tuning. The model field suggests known model IDs and accepts runtime-native IDs.

Blank fields use the Provider's default. Saving tuning preserves the secret, consent, and recorded health. New Threads (conversations containing your work) use the saved values; existing Threads keep their selected tuning.

Docs for Zozo: a coding-agent harness.

Copyright © Zozo