LuxAI account

LuxOS has one shared LuxAI account per user profile. You sign in once in the system and LuxOS apps – LuxAI, Lux Code and LSL IDE – reuse it; nobody signs in inside each app separately. The account belongs to the service at https://lux-ai.cz.

Where to sign in

  • App LuxAI Account (luxos-account, package luxos-account): sign in and full account management (see Managing the account) – it replaces the account page https://lux-ai.cz/settings. It also shows the account on this computer with its profile picture (the same picture as on the login screen); clicking the picture or Change Picture opens Profile Picture (luxos-profile-picture, see settings-apps.md). The user button of the LuxOS menu opens this app.
  • The welcome window after first login.
  • Optionally already in the installer (graphical and text): password, code sent by e-mail, or creating a new account.
  • LuxAI and Lux Code offer Sign in with LuxAI account / Sign in again when there is no account or the server answers 401/403; this runs luxos-account login.

Sign-in methods (shared GTK panel SignInPanel in /usr/lib/luxos/python/luxai_account_gtk.py): password, 6-digit code from e-mail, new account, and web login (PKCE through https://lux-ai.cz/ide/connect?…&app=luxos).

Command line

luxos-account            # account window (sign in / account management)
luxos-account login      # sign-in window; exit code 0 = signed in
luxos-account register   # same, directly creating a new account
luxos-account status     # JSON {"signedIn": true, "user": {...}} - never contains the token
luxos-account token      # prints the session token (for apps of the same user only)
luxos-account logout     # signs out and invalidates the session on the server

luxos-account status is the safe way to check whether a user is signed in. Never print, log or share the output of luxos-account token – it is a secret session credential.

Storage

~/.config/luxai/account.json (directory 0700, file 0600, written atomically):

{
  "version": 1,
  "origin": "https://lux-ai.cz",
  "sessionToken": "…",
  "user": { "id": "…", "email": "…", "displayName": "…", "username": "…" },
  "client": "luxos",
  "updatedAt": "2026-10-20T16:30:00+0200"
}
  • Missing file = not signed in.
  • Apps only read it; it is written by luxos-account (and the installer). On HTTP 401/403 apps offer Sign in again and do not delete the file themselves.
  • The origin can be overridden for testing with LUXAI_ORIGIN.

Models and monthly credits

The account offers two AI models:

Model id Description in LuxAI
Flash flash "smarter", default model; can see images
Lite lite "faster, larger limit"; no image input by default; also used to generate conversation titles

Since 19 November 2026 usage is counted in credits: every account has 20 000 credits per month, shared by all models (Flash, Lite and any other) and by all apps that use the account (LuxAI, Lux Code, LSL IDE). A request costs credits according to what it really costs to run, so a smarter model or a long answer uses more of them. Some accounts are unlimited.

The real numbers are delivered by the server in GET /api/me: usage.credits (used this month), usage.creditsLimit, usage.unlimited, plus usage.week and usage.month. The LuxAI Account window shows one bar under AI usage this month – "X of 20 000 credits this month" with the numbers from the server, formatted for the app language – or "Unlimited". Treat the values from /api/me as authoritative because the server may change them. The fields fastTokens, fastLimit, liteTokens and liteLimit are still sent for older app versions only; if a server returns only those, LuxAI Account falls back to the old Flash and Lite bars in tokens.

When the credits are used up, requests get HTTP 429 {"error": "monthly_limit", "limit": …, "unit": "credits"} and the apps say "You've used this month's LuxAI credits. They renew on <date>." (without the date when it cannot be derived from usage.month).

Managing the account

When signed in, LuxAI Account shows a sidebar with these pages (same API as the web page https://lux-ai.cz/settings; every request carries the account cookie and X-Lux-Client: luxos):

Page What it does Endpoint
Overview name, @username, e-mail; one credits bar with percent, "X of 20 000 credits this month" and the renewal date when the server sends it (usage.month or usage.resetAt); "Unlimited" for unlimited accounts; the used-up message when the credits run out GET /api/me
Profile change the username (3–32 lowercase letters, digits, . _ -, first a letter or digit; errors invalid_username, username_taken, rate) PATCH /api/account/settings {"username"}
e-mail – shown only; changing it has no API (button Contact Support → info@lux-ai.cz) –
profile picture – local to this computer (luxos-profile-picture); the web has no avatars –
Password & Security change password (current + new twice, strength meter; errors invalid_current_password, weak_password, same_password, rate). The current password may be empty right after signing in with an e-mail code. All other sessions are signed out, this computer stays signed in POST /api/account/password {"currentPassword", "newPassword"}
sessions: only "This computer" with Sign Out – the server has no session list; changing the password signs out all other devices POST /api/ide/logout
Preferences AI answer style for LuxAI chat: balanced, concise, detailed, technical, friendly PATCH /api/account/settings {"aiResponseStyle"}
light/dark mode of the website (stored in the account) PATCH /api/account/settings {"theme"}
Privacy & Data Export to a JSON file (0600): profile, settings, usage and the web chat history; the session token is never included. If the history is not accessible from the app, only the profile is exported GET /api/me, GET /api/chat/history, GET /api/chat/history/<id>
Terms of Use (they also cover personal data) in the app or on the web GET /terms
Delete account: the server has no deletion API; per the Terms the user asks support. Strong confirmation (type the account e-mail + tick "I understand") then opens a prepared e-mail to info@lux-ai.cz – nothing is sent automatically –

The sidebar also has Open on the Web (/settings) and Sign Out. If the server answers 403 to a change from the app (e.g. {"error": "origin"}), the card shows "This change is not available from LuxOS yet" with an Open on the Web button; 401 returns to the sign-in screen. There are no API keys on the account page (developer API documentation: https://api.lux-ai.cz/docs).

Using the account from apps

Every request to https://lux-ai.cz carries:

  • cookie lux_account_session=<sessionToken>,
  • header X-Lux-Client: <client> – allowed values lsl-ide, luxos, lux-code, luxai.
Call Purpose
GET /api/me user and monthly usage
POST /api/ide/chat/completions OpenAI-compatible chat (tools, stream: true = SSE), billed to the account limit
GET/PUT/DELETE /api/ide/cloud/... cloud files (LSL IDE cloud)
POST /api/ide/logout invalidate the session
PATCH /api/account/settings {"username" \| "theme" \| "aiResponseStyle"} → {user}
POST /api/account/password {"currentPassword", "newPassword"}; signs out other sessions
GET /api/chat/history[/<id>] web chat history (export)
GET /api/mail/mailboxes mailboxes on the LuxAI server this account may use: {"mailboxes": [{"address", "display_name", "imap": {host, port, security}, "smtp": {…}, "auth": "luxai-oauth"}]} (LuxOS Mail)
POST /api/mail/token {"address"} → short-lived access token (15 min) for IMAP/SMTP via SASL OAUTHBEARER/XOAUTH2; never stored by the app

Helpers:

  • Python: /usr/lib/luxos/python/luxai_account.py – load(), me(), request(...), login_password, request_code + login_code, WebLogin, logout(), register_start, fetch_terms(), error_text(err, _); account management: set_username, set_theme, set_response_style, update_settings, change_password, export_data(path), deletion_mailto(user), usage_reset(usage), account_error_text(err, _), web_only(err).
  • Shell/LSL/Lux Code: luxos-account status, luxos-account token (pass the token only in a header or cookie, never in a URL or command line visible to others).

Lux Code uses the account automatically when ~/.config/luxai/account.json exists (LUX_CODE_AUTH=auto|account|apikey, default model LUX_AI_MODEL=flash); otherwise it falls back to an API key from its .env.

Creating an account

Possible directly in LuxOS (installer and luxos-account register), without a browser:

  1. name, e-mail, password (12–128 characters) and acceptance of the terms (text from GET /terms is shown in the app),
  2. POST /api/auth/register/start sends a 6-digit code to the e-mail,
  3. POST /api/auth/code/verify creates the account and signs in.

Errors: invalid_email, email_domain_blocked, weak_password, terms_required, account_exists (409), rate / slow_down (429), email_domain_check_unavailable (503), email_domain_review (422). If the server does not allow registration from native clients (403 {"error": "origin"}), the apps offer to finish at https://lux-ai.cz/register.

Troubleshooting

  • "Your LuxAI session has expired or is not valid" → run luxos-account login (or open LuxAI Account) and sign in again.
  • Check state without exposing secrets: luxos-account status.
  • Sign out everywhere on this profile: luxos-account logout.
  • Never edit account.json by hand and never ask the user for their password in a chat – use the sign-in window.

See also: Configuration, Apps.