Your own vendor subscription
Sign a CLI in with your own account and it runs on your subscription instead of your credit here.
Diagram as text
- Pick a private workspace you own. It needs a container, and a shared workspace is refused.
- Start the sign-in in the native CLI: /login in CMD for Claude Code, device sign-in for Codex.
- Approve on the vendor's own page.
- The CLI confirms completion itself. No code is pasted into ZeroLog.
- Work runs on your vendor subscription and the vendor bills it, not ZeroLog credit.
- If a vendor limit is reached you get an error; ZeroLog does not move the request to another provider.
- 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.
- The CLI starts /login or device sign-in
- you open it
- the CLI confirms completion
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
- No automatic model switch. Customer catalogue requests show an error when a model is unavailable; choose another model yourself. Vendor-account requests are not transferred to another provider either.
- Spend limits and the budget governor, because there is no spend of ours to cap.
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.