Aura

This release focuses on first run project loading, responsiveness, and making Aura friendlier with real-world folders.

What changed

Missing Git no longer blocks Aura

Aura now treats Git as a capability, not a gate.

If a folder is not a Git repository, Aura will still open it and let the user browse/work with it. Git-dependent features like undo and auto-commit are explained through a non-blocking prompt instead of a modal dialog.

• Removed blocking Git initialization prompts during project load
• Added non-modal Git warning with “Initialize Git” / “Not now”
• Moved Git repo checks off the UI thread
• Preserved Git support for undo, snapshots, and auto-commit workflows

Better support for large and messy project folders

Aura is now more defensive when opening folders that contain heavy generated directories or unusual file layouts.

• Filters common large folders from the file tree:

  • .git
  • .venv
  • venv
  • env
  • node_modules
  • dist
  • build
  • .next
  • .cache
  • target
  • __pycache__

• Avoids symlink traversal in the workspace tree

• Adds timing logs around project-load phases for easier diagnostics

Project/sidebar refresh hardening

The left project panel now avoids a refresh loop during thread backfill and defers heavier refresh work until after the workspace becomes visible.

• Deferred project and drone refresh after workspace selection
• Fixed a potential repeated backfill/refresh loop
• Reduced the chance of first-load UI stalls

Why this matters

A first-time user should be able to download Aura, pick a folder, and immediately see that Aura is alive and working.

This release makes that path more forgiving for GitHub ZIP downloads, non-Git folders, large repos, and stranger-shaped project directories.