This release adds 2 notable features for engineering teams evaluating rollout.
✓ No known CVEs patched in this version
Topics
+4 more
Summary
AI summaryFirst‑run onboarding now prioritizes Aura Credits, eliminating crashes from missing DeepSeek keys.
Full changelog
This is a quick hotfix for first-run Aura Credits onboarding.
What changed
New users should no longer hit the old DeepSeek/API-key startup wall before they can enter an Aura Credits key.
Aura now treats Aura Credits as the primary first-run path, opens the Settings → Aura tab from setup, and keeps “Continue Read-only” truly read-only instead of trying to resolve a missing provider key during startup.
Fixes
- Fixed fresh installs crashing or warning about missing DeepSeek keys before Aura Credits setup.
- Updated first-run setup copy to guide users toward Aura Credits first.
- Changed the setup action to open the Aura tab instead of the API Keys tab.
- Added a direct Settings → Aura route for onboarding.
- Made the API backend initialize lazily so provider keys are not required during app launch.
- If an Aura Credits key is already saved, Aura can automatically switch to the Aura provider instead of showing the old provider gate.
- BYOK providers still work as before.
Why this matters
Aura Credits are now part of the front door, not a hidden side path. New testers should be able to install Aura, paste an Aura key, refresh balance, and start using Aura without needing to understand BYOK setup first.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About Aura
All releases →Related context
Related tools
Earlier breaking changes
- v1.4.0 All file-writing paths now route through a validation pipeline.
Beta — feedback welcome: [email protected]