co auth
One-time setup for managed models — no provider keys needed. Authenticates your agent with OpenOnion and unlocks the co/ model prefix across providers.
Quick Start: Run co auth once and start using co/gpt-4o, co/claude-3-5-sonnet, or co/gemini-1.5-pro — no API keys to manage.
Quick Start
Two commands cover the full setup:
co auth is required before you can use any co/ models. co auth google is optional — only needed for Gmail/Calendar tools.
What co auth does
Behind the scenes
~/.co/keys.env as OPENONION_API_KEY.env, it's updated too~/.co/keys.env gains AGENT_EMAIL and IS_EMAIL_ACTIVE=trueAfter running, your ~/.co/keys.env looks like:
OPENONION_API_KEY=oo_live_abcd1234... AGENT_EMAIL=0x7a9f3b2c@mail.openonion.ai IS_EMAIL_ACTIVE=true
What co auth google does
Connect a Google account so your agents can send Gmail and read Calendar:
.env for your agents to useUse Managed Models (co/ prefix)
Once authenticated, use any co/ model — no provider API keys required:
Works across providers:
OpenAI
- co/gpt-4o
- co/gpt-4o-mini
Anthropic
- co/claude-3-5-sonnet
- co/claude-3-5-haiku
- co/gemini-1.5-pro
- co/gemini-1.5-flash
Troubleshooting
Missing token?
Run co auth again — it will refresh your OPENONION_API_KEY in ~/.co/keys.env.
Network issue?
Try again or check your connection. co auth needs to reach oo.openonion.ai.
Global vs project
co auth prefers a local .co directory if keys exist there, otherwise falls back to ~/.co.
ConnectOnion