Account & auth

The app supports authentication so deploy and AI features can be tied to a user. When you’re not signed in, those features may be disabled and you’ll see a prompt to log in.

Auth states

• Loading — The app is checking whether you have a valid session.
• Authenticated — You’re signed in; deploy and AI are available (subject to plan/entitlements).
• Unauthenticated — No session; a Log in button and banner may appear, and deploy/AI actions are gated.

Session is persisted (e.g. in local storage) for a limited time (e.g. 7 days) so you stay signed in across restarts.

Signing in

• Click Log in (e.g. in the top bar or entry screen). A sign-in overlay opens.
• Complete the flow (e.g. email or OAuth). The app will move to authenticated and store the session.

(In the current version, sign-in may be a mock for development; real integration with Clerk or another provider is planned.)

User profile

• When signed in, an account control in the header opens the user screen (separate from the project list).
• From there you can:
  • Go Back to the project list or current workspace.
  • View user-related info (e.g. email, name, username) when available.
  • Sign out — Clears the session; you return to unauthenticated state.

The entry screen (project list) does not require sign-in; you can open and edit projects without an account. Only deploy and AI (when gated) require authentication.

Username and deploy namespace

• Your username is a unique, URL-safe handle (e.g. jane, acme-studio). It is used for deploy paths (e.g. @username/project-name/) so your deployed assets have a stable, namespaced URL.
• If the app supports profile updates, you may be able to set or change your display name; username uniqueness is enforced by the backend.