Sign in so captured sessions route to the right paper console account. Prerequisite: paperctl is installed.
Sign in
paperctl loginOpens a browser for WorkOS auth. Sign in with your work email. On an SSH session or a machine without a browser, run paperctl login --no-browser — it prints the verification URL so you can open it from any device. Confirm who you’re signed in as with:
paperctl whoamiRun paperctl login again any time to switch accounts.
Pick your organization
If you belong to multiple organizations, choose which one paperctl routes through:
paperctl org selectThe new selection takes effect the next time paperctl starts. If it’s already running, restart it with paperctl init.
To bring teammates in, invite them by email from Settings → Team in paper console (requires the admin role). When they run paperctl login, the org is pre-selected and the CLI auto-discovers the default gateway — nothing else to set up on their side. Manage your team workspace covers roles and what members see.
Need to create an organization?Optional
If you’re the first person on your team, head to console.papercompute.com to name your org. The console provisions a default gateway and backends so paperctl has something to route through — an Anthropic backend for Claude Code plus the two Codex backends covered in Backends and providers.
Invited by someone? Skip this — your org is already set up.
Staying signed in
After login, the daemon keeps a short-lived token warm in ~/.config/paper/ — day-to-day use needs no re-authentication. paperctl status shows auth health; if it reports a problem, paperctl login fixes it.
To sign out and clear the daemon-owned credentials:
paperctl logout