v0.3.10

Aura v0.3.10

Applications launched with an Aura environment can continue creating child processes after Aura closes. This fixes command startup timeouts in long-running applications such as Codex when their original Aura launcher has exited.

Changes

• Application and CLI launches with a Profile now use an independent session host. It retains the Runtime Broker and the immutable startup configuration until the entire tracked process tree has exited, including children that outlive their root process.
• Normal launcher exit, launcher termination, and closing the launcher's console no longer remove the Broker from an otherwise running process tree. The session host detaches from the launcher's console after startup completes.
• The session host executable and paired Runtime DLLs run from content-verified caches outside the installation directory. Installer shutdown of installed Aura executables does not directly terminate the cached session host.
• Startup retains authenticated Runtime identity checks and rejects injection failures. Session handoff checks both pipe endpoints and transfers the retained root process handle, so short-lived roots do not depend on reopening a PID.
• Windows Terminal handoff keeps its per-run Job and failure cleanup. Packaged applications retain their existing best-effort Job assignment behavior; managed Workspace runs continue using the existing Supervisor path.

Validation and limitations

• Before versioning, real-process checks covered normal launcher exit, termination of the test launcher, and closing its own hidden console. The fixture configuration and US Development Profile completed 30 cmd, Git, Cargo, Rustc, and PowerShell launches, preserved the Profile and actual timezone view, and released the Broker after the last target exited.
• Existing launcher and CLI checks passed with 244 tests passed and 12 conditionally ignored. No additional test cases were authored during this release preparation.
• Publication requires successful Windows CI for the exact release commit, including the existing workspace checks, detached-session checks, and separate CPU-renderer regression suite. The installer is built through the canonical packaging script and its public checksum is verified independently.
• These checks do not establish an interactive installed-Codex session, an elevated in-place upgrade, or Windows Terminal ConPTY interaction. Packaged application activation retains its existing post-activation coverage and tracking limitations.
• Aura remains a process-scoped environment launcher, not a security sandbox. Host Windows settings are unchanged.

Upgrade

Install aura-setup.exe or use the updater, reopen Aura, and restart applications through the updated version. Existing application, Profile, and UI settings are retained. Processes started by an older Aura version do not automatically acquire the new session host; already detached old instances need to be relaunched to benefit from this fix.

Installer

• File: aura-setup.exe
• Size: 11599413 bytes
• SHA-256: e288d6055b11312f090507d1bddf25cb68a59653622ce000e4bcce684f7204bc