Sign agents in on another host

Each agent CLI keeps its own login on the machine it runs on. When an agent on another host is signed out, you can sign it in from the device you are using: Glueprint runs the agent’s own login on that host and shows you each step. You never need to SSH in.

Where to start

Host settings > Agents. Open the host picker and click the gear next to the host. When an agent there needs a login, the gear opens the Agents tab directly. Click Log in on the agent’s row.
The new-session composer. When the agent you picked is signed out on that host, the composer shows Needs login with a Log in link before you send.
An alert (desktop). A Needs login alert links straight to the host’s Agents tab.

Log in also appears when the host can’t tell whether an agent is signed in.

Per-agent steps

The sign-in page always opens in a browser on the device you are using, never on the host.

Agent	What you do
Claude Code	Open the sign-in page, approve, then paste the code it shows back into Glueprint.
Codex	Open the link and enter the one-time code Glueprint shows. Glueprint finishes on its own once you approve.
Gemini CLI	Open the Google sign-in page, approve, then paste the authorization code back into Glueprint.
Cursor	Open the link and approve. Glueprint finishes on its own.
opencode	Needs a terminal, because it asks you to pick a provider from a menu. Log in takes you straight to Continue in terminal.

Glueprint checks the agent’s own login status while you sign in, so the sheet closes as soon as the host reports the agent signed in, even if the agent never prints a success message.

Continue in terminal

Agents change their login screens from time to time. The sheet has a CLI output panel that shows what the agent is printing on the host. If 15 seconds pass with no sign-in link or code prompt, the panel opens on its own.

Click Continue in terminal at any point, or after a failure:

Glueprint stops its own login attempt and opens a terminal on that host.
It runs the agent’s login command there, for example codex login --device-auth.
Follow the agent’s prompts in the terminal. Links open on your device when you click them.
The sheet waits and checks the host every few seconds for up to 15 minutes. It closes on its own once the agent is signed in. Stop waiting ends the wait.

Managed accounts

For Claude Code and Codex you can keep several accounts per host (see Accounts on the agent’s settings).

Re-authenticate works in the sheet and in Continue in terminal. The terminal signs in that account, not the machine’s own login.
Add account must use the guided sheet: Glueprint records the new account only after the provider reports its email.

API keys

If you’d rather not sign in interactively, use Use API key on the agent. Codex stores the key in its own login; Claude Code and Gemini CLI receive it from Glueprint when a session starts.

Over SSH

If you are already in a shell on the host:

glueprint agent login claude-code
glueprint agent login claude-code --account <account-id>

It runs the same login the desktop app would, then reports whether the agent is now signed in. glueprint agent detect shows each agent’s login status and suggests the command for any that are signed out.

A user-level glueprint service install records your shell’s PATH in the service definition, so agents installed through npm, nvm or ~/.local/bin are found when the daemon runs as a service. Run it again after you change Node versions.

Troubleshooting

“The agent CLI isn’t installed on that host.” Install the agent on the host, then check it is on the PATH of the shell the host starts with. On a CLI daemon, re-run glueprint service install.
“Encryption is locked.” The host or this device hasn’t unlocked your organization’s key yet. Wait for the host to finish connecting and try again.
The host went offline. Login needs the host online the whole time. Start again once it reconnects.
Another login is running. One login per agent runs at a time on a host. Finish or cancel the other one first.