Report what happened.

Send feedback

1. Open the Solara account portal and sign in with your verified email.
2. Choose Overview, then expand Send feedback.
3. Choose Bug, UX, Performance, Provider, Feature request or Other.
4. Complete What happened?, review any selected screenshots and choose Send feedback. Read the result message before retrying.

In the desktop, Settings → General → Desktop updates → Send Early Alpha feedback opens the portal. It does not automatically attach your project, profile or logs.

A success message confirms that your report was saved. It does not mean a person has reviewed it or replied.

Include these details

• Version: the installed version shown in Settings → General → Desktop updates, plus your operating-system version and computer architecture.
• Context: Plan or Build, Solo or Team, Auto on or off, local or remote execution, and the exact provider/model if relevant. Include only a non-secret endpoint description.
• Steps: the smallest sequence that led to the issue, using a disposable example where possible.
• Expected and actual: what you wanted, what the app displayed, and what changed on disk if you observed it.
• Impact: whether work is blocked, files appear changed or lost, or a command may still be running. Record the approximate time and time zone.
• What you tried: any troubleshooting steps and whether the issue happened again.

Type the installed version even when the portal shows a release: reports can be associated with the portal's current release, which may differ from your installation.

Share only the minimum

Do not send API keys, passwords, sign-in links, access or refresh tokens, presigned download URLs, billing credentials, account identifiers, personal correspondence or private source code. Replace sensitive values with placeholders before submitting. Do not attach an entire app profile, database or repository.

The form accepts up to three PNG, JPEG or WebP screenshots, with a 5 MiB limit per input image. Crop or redact them first. The browser resizes and re-encodes images to remove original metadata; visible secrets remain visible unless you remove them.

Feedback text and screenshots are associated with your account and available to Solara administrators for support. They are not anonymous submissions.

If the report is saved but an image upload fails, use Retry missing screenshots within the form's stated one-hour window, or Keep report without missing screenshots. Avoid creating another report for the same upload failure. Keeping the report does not delete images already uploaded.

When you get stuck

Sign-in or revoked access

Signup is open, and verifying your email activates a new account automatically. Revoked access needs an administrator to restore it from the admin panel. Use Check access again after restoration. If you cannot enter the portal, contact solara@mailbox.org; portal feedback requires approved access.

No release or expired download

Not published yet is not an installation problem. Follow the portal's release instructions. Once a build is available to your account, use the portal's download action to request a fresh link instead of reusing a forwarded or expired URL. If its checksum differs from the published SHA-256, stop before opening it. For a signed build, the signature must also be valid and its publisher must match the release instructions. Stop if a build described as signed has no valid signature.

Availability is separate for Windows x64 and Apple Silicon Mac. Mac distribution is still in preparation. Selecting an operating system does not grant a download or substitute a build for another computer.

Close an account or ask about your data

Use Settings → Close account in the portal. Closure ends access now and schedules hosted account deletion after 30 days. Support reports expire 30 days after resolution. Local projects and chats remain on your computer. If you cannot sign in, email solara@mailbox.org; do not include a password or sign-in link. See the data-handling notice for scope and the remaining mailbox, log and backup limitations.

Windows warnings or installation blocked

Unsigned alpha software may trigger publisher or reputation warnings, and Windows or your organization's policy may block installation. A matching checksum only confirms that the file matches the published record. Keep Windows protections enabled. If installation is blocked, record the message without private details and use an agreed support route. Do not change device policy to get past the block.

Email or account access

Check the inbox you entered and its spam folder. Wait at least 60 seconds before requesting another link. A desktop request needs its own fresh link. Retry connection or Retry access check can appear when the service could not be reached; an unavailable check is not proof of revocation.

Feedback requires account access. If you cannot sign in, email solara@mailbox.org with a minimal error summary. This page cannot open a support ticket for you, restore access or promise a response time.

Provider errors or unclear execution

Record the error, selected endpoint, exact model and region without exposing credentials. Check your provider's account access and budget before trying again. A connection or catalog result does not prove a model request completed. If completion is uncertain, do not repeatedly resend a potentially billable request.

File loss, cleanup or startup problems

Stop further changes in the affected trial project. Preserve your backups and the visible error. Do not clear the app profile, overwrite the project or install Alpha44 over a schema-24 profile to troubleshoot. Restarting is not proof that commands or child processes have stopped. Seek an agreed recovery step through the available private support route.

Known limits for this trial

• Windows x64 and your own configured provider; any provider charges are yours.
• Plan blocks effectful model tools, while provider requests and some attachment preparation can still send data.
• EA 0.13-62 uses automatic Sandbox for local chat commands. Manual Terminal, goals and task workspaces remain separate; the entire application is not sandboxed.
• EA 0.13-62's schema-28 profile cannot be opened by older clients.
• Follow the instructions for your exact release when moving to a newer version. Do not assume automatic updates or downgrade compatibility.

The portal's Known issues section lists issues shared with testers. New or unreported problems may still occur. If your issue is not listed, include it in your feedback.

Contact Solara

Solara operates this alpha. Our monitored support and privacy contact is solara@mailbox.org. Response expectations and account and data-request procedures still need confirmation. Hosted reports and images expire 30 days after resolution, with failed deletions kept for retry. Mailbox, log and backup deletion remains unverified. No support response time is promised.