Klaus
International site Sign in
Contact us Download Klaus

Account and sign-in

How Klaus account sign-in and third-party subscriptions (including local credential reuse) work independently.

  • Jump straight in: the app opens into the workspace on launch, with no sign-in required. No model source (your own subscriptions, custom API keys) requires a Klaus account.
  • Klaus account: used for features that need a cross-device identity — Friends, team collaboration, cross-device conversations, phone pairing, and feedback. Choose "Sign in" from the user menu in the bottom-left corner; the browser authorization flow returns you to the app when done. These features are unavailable while you are signed out, but everything else is unaffected.
  • Profile page: click the avatar in the sidebar to open it. It shows five real usage stats — total tokens, peak token usage, longest task time, longest streak and current streak — with a "Token activity" chart below in daily, weekly and cumulative views. "Edit profile" changes the display name and username and crops the avatar by dragging. The "Profile" page in Settings opens the same page.
  • Third-party subscription sign-in: if you already have a Claude, ChatGPT/Codex, Qoder, QwenWork, QoderWork, WorkBuddy, or Kimi subscription, or a Bailian Token Plan, MiniMax M Plan, Zhipu Coding Plan, or Ark Coding Plan, you can connect it as a model source and use the quota you have already paid for inside Klaus. When the corresponding official client is already installed on this machine, Claude, Codex, Qoder, QwenWork, QoderWork, and WorkBuddy can also reuse its local sign-in instead of signing in again; Kimi and the plans take a key from their console. See Models for how each source connects. Traffic and quota on these sources still belong to the corresponding provider account.
  • These sign-ins are independent of each other: signing out of your Klaus account does not sign you out of Claude, and vice versa. Signing out of your Klaus account only affects the features above that need an account — it does not delete third-party subscription credentials or custom API configurations.

Credentials stay on this machine only and are never handed to the model: if you ask in a conversation "what is my API key", it will only tell you whether one is configured, never recite the key.