Your Scylla Account identifies you to Scylla Workbench services such as Team membership, account-based licensing, Team Memory, and other hosted account features.
It is separate from the accounts you use with AI providers.
Three different identities
It helps to keep these separate:
Windows identity
Scylla is a Windows desktop application. Local files, processes, terminals, and many local operations ultimately run under your signed-in Windows user and remain subject to Windows permissions.
Scylla Account
Your Scylla Account is used for Scylla-hosted identity and entitlement features.
Examples include:
- Team organization membership;
- seat assignment;
- desktop Team activation;
- Team Memory availability;
- account and session management.
Agent Provider account
OpenAI, Claude, Cursor, GitHub, and other Agent Providers own their own authentication.
Signing into Scylla does not sign you into a provider.
Signing into a provider does not activate your Scylla Team seat.
Signing into Scylla
Scylla desktop uses a browser-based sign-in flow rather than asking you to type your Scylla Account password directly into an Agent prompt or provider panel.
A normal desktop sign-in looks like:
- Choose Sign in with Scylla in the desktop application.
- Scylla opens the Scylla Workbench account flow in your browser.
- Sign in to your Scylla Account there.
- The browser returns the authorization result to the desktop.
- Scylla verifies and stores the resulting account/entitlement state needed by the application.
The desktop should never require you to paste your normal account password into Agent chat.
Team activation
For Team, signing in is only one part of activation.
You also need an organization membership and an assigned seat.
If you can sign in but the desktop does not become Team-active, check Seat Assignment and Desktop Team Activation.
Provider sign-in
Connect providers from Scylla's Agent Provider controls.
Provider authentication remains provider-owned. The exact sign-in process depends on the provider and runtime in your Scylla build.
A provider may be fully authenticated while Scylla Account is signed out, and vice versa.
Manage Account
Use the Scylla Workbench account/console for account-level features such as:
- organization membership;
- Team seats;
- installations;
- billing when your role allows it;
- account sessions;
- Team Memory configuration where available.
The website account is the control plane for hosted account state. Local project source and local Keyring contents remain desktop concerns.
Signing out
Signing out of your Scylla Account should clear Scylla-hosted account context from the desktop.
It does not necessarily sign you out of every Agent Provider, because those are separate accounts and processes.
If you are handing a Windows machine to another person, also review:
- Agent Provider sessions;
- local browser sessions;
- Scylla Keyring lock state;
- open terminals;
- local project access.
Password changes and sessions
Account security actions such as password changes or session revocation belong to Scylla Account management.
If you revoke a session, expect that session to stop being valid once the server-side revocation is applied.
Never share session tokens, browser callback data, or other account credentials in support requests.
Scylla Account vs license keys
Community, Professional, and Team may use different entitlement flows.
Team activation is account-based. A Team member should not need to pass around a reusable Team license key.
Professional licensing and evaluation behavior may use signed entitlement state that remains separate from AI provider authentication.
Common problems
I signed into Scylla but my Agent Provider is unavailable
Connect/authenticate the Agent Provider separately.
My provider works, but Team features are missing
Check Scylla Account sign-in, Team organization membership, and seat assignment.
The browser sign-in completes but desktop does not update
Return to Scylla and retry the account refresh/sign-in action. If the issue persists, capture the Scylla version and the account-state message shown in the application.
I signed out, but a provider still works
That can be expected. Provider sessions are separate from Scylla Account sessions.