Your own vendor subscription

Sign a CLI in with your own account and it runs on your subscription instead of your credit here.

Signing a CLI in with your own subscriptionIn a private workspace you own, you start the native sign-in of Claude Code or Codex. You approve on the vendor's own page and the CLI confirms completion itself. Work then runs on your vendor subscription and the vendor bills it. If a vendor limit is reached you get an error and ZeroLog does not reroute. When the runtime stops or is recreated you connect again.1. Pick a private workspaceyou own (needs a container;shared workspace is refused)2. Start the CLI sign-inClaude Code: /login in CMDCodex: device sign-in3. You approve on thevendor's own page4. The CLI confirmsitself, nothing is pastedinto ZeroLog5. Work runs on yourvendor subscriptionVendor limit:error, no rerouteRuntime recreated:connect again
The sign-in leaves the CLI for the vendor's page and returns to the CLI; the vendor then bills the work.
Diagram as text
  1. Pick a private workspace you own. It needs a container, and a shared workspace is refused.
  2. Start the sign-in in the native CLI: /login in CMD for Claude Code, device sign-in for Codex.
  3. Approve on the vendor's own page.
  4. The CLI confirms completion itself. No code is pasted into ZeroLog.
  5. Work runs on your vendor subscription and the vendor bills it, not ZeroLog credit.
  6. If a vendor limit is reached you get an error; ZeroLog does not move the request to another provider.
  7. After the runtime stops or is recreated, connect again.

The sign-in

Select a private workspace you own. For native Claude Code, open CMD in your chat, choose Your account and run /login. For Codex, use Connect account under AI accounts in settings. This needs a container, which the Free plan does not include.

  1. The CLI starts /login or device sign-in
  2. you open it
  3. the CLI confirms completion
Nothing is intercepted or replayed. The path leaves the CLI and comes back to it, because sign-in mirrors each CLI's own flow: it is that CLI doing the signing in.

Once signed in

The credential
Available only in a workspace owned by you that nobody else can write to.
The login
It is temporary. After the runtime stops or is recreated, connect again. Sign-in is refused in a shared workspace, because anyone who can write there could read the token.
The bill
That vendor bills you on your subscription. Nothing reaches your credit ledger.
The limits
Your subscription's own limits apply unchanged. This service does not raise them, extend them, or reroute a request that has hit one.

What does not reach here

Different native sign-ins

In Claude Code, use /login. For Codex, run codex login --device-auth, open the displayed URL and enter the device code on OpenAI’s page. Codex waits for completion itself: no code is pasted back into ZeroLog.

Tool conversations and model settings stay separate. Files, packages and caches can remain in one workspace. Give the next tool a handover with the task, changed files and tests. See the tool-switch workflow.