Authentication

Sun Studio requires a Sunnylabs account, confirmed email, a Sun Studio license granting full access and an accepted device activation. Login and initial session restoration require a network connection to accounts.sunnylabs.tech. The standalone Sun CLI does not require a Studio account.

Enter your email and password in Studio's sign-in screen. The desktop main process communicates with the Sunnylabs accounts API; there is no device code or browser authorization step.

Account creation offers individual or team accounts and monthly or annual billing. The interface can offer a trial; its availability, duration and access are determined by the account service, not a local timer. Confirm your email before opening the editor.

Studio encrypts its API token using the operating system's secure storage in auth-session.bin. If secure storage is unavailable, the credential remains in memory only and a new sign-in is required after closing. On Linux, plaintext basic_text storage is not accepted.

Linux persistence requires libsecret and an available, unlocked Secret Service keyring. Settings reports the storage mode. Unlock or repair the keyring and sign in again rather than enabling plaintext storage.

A saved token is not offline authorization. The editor stays locked until the profile has a verified email, the license is usable, device activation is approved and safe credential persistence has completed (or the supported memory-only storage policy has been applied).

During automatic recovery the interface remains restoring, pending or loading; a recoverable attempt does not show an error before the final failure. A network failure restoring the initial saved token preserves credentials for another attempt; HTTP 401 expires the session and clears credentials.

Each GET has at most 3 attempts by default: the initial request plus 2 retries, only for transport/network errors (including a per-request timeout) or HTTP 502, 503 and 504. Default backoff is 500 ms then 1000 ms. The timeout remains 10 seconds per attempt, not an overall startup deadline.

GET responses with HTTP 401, 403, 422, 429 or 500 are not retried automatically. Malformed successful authentication responses are validation failures, not transport retries. Every POST, including login, signup, device activation, logout and verification-email resend, is never retried automatically.

After final failure, Try Again reruns the full profile, license and device validation flow. If the profile succeeded and a later license or device step failed, it reuses the token already in memory; it does not submit a new credential login. A transient device-activation POST failure still requires manual Try Again because POST is not automatically replayed.

Cancel, a new sign-in, sign-out and disposal abort in-flight HTTP requests and backoff waits and reject stale completions. A canceled or superseded operation cannot unlock the editor.

After validation, protected actions periodically recheck the license and device, normally after ten minutes. A network-classified failure during an already validated session retains access and schedules a retry after one minute. This existing grace is not offline login or a guarantee of unrestricted offline use.

HTTP 502, 503 and 504 remaining after the GET retry budget is exhausted still lock access under the existing fail-closed policy; HTTP 503 does not generally authorize offline access. Invalid sessions, inactive licenses and rejected device activation block access. Leaving the authenticated state stops the language engine; your program is not replayed automatically.

Entre com email e senha da conta Sunnylabs; a API em accounts.sunnylabs.tech valida perfil, licenca Sun Studio e dispositivo, sem codigo ou autorizacao no navegador. O editor so e liberado com email verificado no perfil, licenca utilizavel, ativacao de dispositivo aprovada e persistencia segura concluida (ou politica suportada de armazenamento somente em memoria aplicada). Nao existe bypass de autenticacao offline; o CLI independente nao exige conta Studio.

O token salvo e criptografado em auth-session.bin pelo armazenamento seguro do sistema. Sem armazenamento seguro, fica apenas em memoria; basic_text no Linux nao e aceito. libsecret exige um provedor Secret Service com chaveiro desbloqueado. Falha de rede na restauracao inicial preserva a credencial; HTTP 401 expira a sessao e remove as credenciais. Durante a recuperacao automatica a interface permanece em restauracao, pendente ou carregando, sem erro antes da falha final.

Cada GET tem no maximo 3 tentativas por padrao: a inicial mais 2 repeticoes, apenas para erros de transporte/rede (inclusive timeout por requisicao) ou HTTP 502, 503 e 504. O backoff padrao e 500 ms e depois 1000 ms. O timeout continua sendo 10 segundos por tentativa, nao um prazo total de inicializacao.

GET com HTTP 401, 403, 422, 429 ou 500 nao tem repeticao automatica. Resposta de autenticacao bem-sucedida mas malformada e falha de validacao, nao erro de transporte para retry. Todo POST, incluindo login, cadastro, ativacao de dispositivo, logout e reenvio de verificacao de email, nunca tem repeticao automatica.

Apos a falha final, Try Again (Tentar novamente) refaz todo o fluxo de validacao de perfil, licenca e dispositivo. Se o perfil ja foi obtido e a etapa de licenca ou dispositivo falhou, reutiliza o token em memoria, sem novo login com credenciais. Uma falha transitoria no POST de ativacao do dispositivo ainda exige Try Again manual, pois POST nao e repetido automaticamente.

Cancelar, iniciar outra entrada, sair da conta ou encerrar o controlador aborta requisicoes HTTP e esperas de backoff e rejeita conclusoes obsoletas. Operacoes canceladas ou substituidas nao podem liberar o editor.

Acoes protegidas revalidam licenca e dispositivo normalmente apos dez minutos. Uma falha classificada como rede numa sessao ja validada preserva acesso e agenda nova verificacao apos um minuto; essa tolerancia existente nao permite login offline. HTTP 502, 503 e 504 restantes apos esgotar as tentativas GET continuam bloqueando acesso pela politica existente de falhar fechado, nao uma permissao offline para qualquer 503.

Sessao invalida, licenca inativa ou dispositivo rejeitado bloqueiam acesso. Sair do estado autenticado encerra o motor, sem executar novamente o programa. Sair da conta remove a credencial local e tenta logout no servidor; falha de limpeza local impede nova entrada ate ser resolvida. Arquivos e recuperacao do editor permanecem no perfil do sistema operacional, sem isolamento entre contas Sunnylabs.

Stop running code, open Settings and sign out of the Sunnylabs account. Studio removes the local credential and attempts server logout. Runtime variables, functions and figures are discarded; source files and editor recovery remain. If local credential cleanup fails, resolve the displayed error before signing in again.

Editing and execution remain local; authentication is not source-file synchronization. The UI does not receive the API token. Persistent credentials are encrypted separately from editor recovery.

Local files and recovered tabs belong to the operating-system profile, not an isolated account vault. Switching Sunnylabs accounts does not erase, encrypt or separate those documents. Use separate OS accounts when local isolation is needed.

• Confirm the account email and verify that the Sun Studio license is active.
• For a device-limit error, manage device activations in your account before retrying.
• After startup recovery is exhausted, check network access to accounts.sunnylabs.tech and use Try Again. A saved token alone does not enable offline sign-in.
• The confirmed client defects were failing on the first transient GET error and Try Again potentially doing nothing after profile success. A network-error screenshot does not establish the actual server, DNS or TLS cause; that cause remains unknown.
• For repeated login requests, check secure-storage availability and the unlocked system keyring.
• Authentication errors use sanitized messages, without secrets, raw exception text or raw network details. Never share passwords, tokens or the credential file in support reports.

• Confirme o email, a licenca ativa e o limite de dispositivos da conta.
• Apos esgotar a recuperacao inicial, confira acesso a accounts.sunnylabs.tech e use Try Again; token salvo nao permite entrada offline.
• Os defeitos confirmados no cliente eram falhar no primeiro erro GET transitorio e Try Again poder nao agir apos obter o perfil. A captura de erro de rede nao determina a causa real no servidor, DNS ou TLS; essa causa permanece desconhecida.
• Se a entrada for solicitada a cada abertura, verifique armazenamento seguro e chaveiro desbloqueado.
• Erros de autenticacao usam mensagens sanitizadas, sem segredos, texto bruto de excecoes ou detalhes brutos de rede. Nao compartilhe senha, token ou arquivo de credenciais no suporte.