Skip to content
Docs menu
On this page

Agents Signing in

Signing in

Agents sign in with their own tools. When one needs you to, the panel says so as soon as you pick it.

Where each agent stands

The Agents button next to Settings, at the bottom of the sidebar, and Settings, Agents show the same status: Ready when Zorvo saw you signed in, Sign in when the agent asked for it, and Not checked when Zorvo has not asked yet.

In Zorvo

An agent that offers its own login, such as Claude Code's Claude subscription, runs it in a terminal inside Zorvo. Your message is sent once you are signed in. Where an agent offers a key instead (Gemini CLI's API key, for example), the panel explains it and you set it up outside Zorvo, then click Check again in the sign-in panel, or Check sign-in in Settings. Zorvo reads your shell's settings again before it asks the agent, so a key you just added to ~/.zshrc is found.

Set up Qwen Code. When Qwen Code needs a provider, the new session shows Set up Qwen Code, which opens Qwen Code's own setup in a terminal, so you pick the provider there. Closing a sign-in or setup terminal checks again whether you are signed in.

Some agents cannot say who is signed in and keep their key in a variable, such as GLM Agent with Z_AI_API_KEY. While that variable is not set in your shell, the agent reads Not checked, not Ready, and its row says what to do. Zorvo only looks whether the variable is set, never at its value.

In your terminal

Sign in once in a terminal, then send your message again.

AgentSign in
Qwen CodeRun qwen once
Claude Codeclaude, then /login
Codexcodex login

Keys and tokens

Still stuck? See Troubleshooting.