# Aura v1.8.2

This release focuses on stability, diagnostics, and installer hardening. The goal is simple: Aura should start reliably, fail visibly when something external goes wrong, and give testers a way to send useful logs.

Highlights

Send Logs support

Aura now includes a clearer Send Logs flow for diagnostics.

When something goes wrong, users can send recent local logs directly from the app. Aura returns a reference ID that can be used to look up the report on the backend.

This gives tester issues an actual trail instead of relying on screenshots, guesses, or “it did nothing.”

Startup and crash logging hardened

Startup logging is now more durable, including safer crash-log handling for packaged builds. If Aura fails early, the logs should have a much better chance of capturing what happened.

Frozen build startup check

The release build now runs a packaged startup check before creating the installer or uploading anything.

The built Aura.exe is launched in a temporary profile, allowed to initialize, then shut down automatically. The build fails if the packaged app cannot start cleanly or if expected startup log markers are missing.

This helps catch missing packaged dependencies, missing assets, or frozen-build startup failures before a release reaches users.

Provider first-response watchdog

Provider streaming now has a first-response watchdog.

If Aura connects to a provider but no first response chunk arrives within the timeout window, the app now surfaces a clear API error instead of appearing stuck forever. Long valid streams are still allowed after the first response arrives.

Packaged SSL and certifi diagnostics

certifi is now an explicit runtime dependency and is manually bundled into the packaged build.

Aura also logs safer SSL diagnostics during provider startup, including whether the certifi certificate bundle exists in the packaged environment. Environment variables are masked as set/not set instead of logging raw values.

Workspace root guardrails

Aura now blocks obviously dangerous broad workspace selections such as drive roots, home, Desktop, Downloads, Documents, and broad OneDrive roots.

Users are guided to choose a real project folder instead. This prevents accidental massive scans and weird project state.

Repo map scan budgets

Repo map generation now has directory, file, and elapsed-time budgets.

If a workspace is unexpectedly large, Aura stops scanning gracefully, logs the budget trip, and returns a partial repo map instead of freezing.

UI resize fix

Fixed a GUI sizing issue where the chat window could become extremely wide and refuse to resize below a huge minimum width.