This release includes breaking changes for platform teams planning a safe upgrade.
✓ No known CVEs patched in this version
Topics
+4 more
Summary
AI summaryDrones are now more capable reusable workflow workers with clearer tool access, policies, budgets, and contracts.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Feature | Medium |
Drones now support reusable worker capabilities with tool access, write policies, run budgets, setup notes, and output contracts. Drones now support reusable worker capabilities with tool access, write policies, run budgets, setup notes, and output contracts. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Feature | Medium |
Drone Bay presents a compact roster view showing name, purpose, write policy, trigger mode, last run status, and Run button. Drone Bay presents a compact roster view showing name, purpose, write policy, trigger mode, last run status, and Run button. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Feature | Medium |
Successful Drone saves automatically refresh Drone Bay without requiring a restart. Successful Drone saves automatically refresh Drone Bay without requiring a restart. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Bugfix | Medium |
Added the real `save_drone_definition` Worker tool for proper Drone persistence. Added the real `save_drone_definition` Worker tool for proper Drone persistence. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Bugfix | Medium |
Workshop-created Drones now persist through the same DroneStore path as manually created Drones. Workshop-created Drones now persist through the same DroneStore path as manually created Drones. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Bugfix | Medium |
Removed the normal need for Drone creator/verifier scripts, eliminating temporary helper script artifacts. Removed the normal need for Drone creator/verifier scripts, eliminating temporary helper script artifacts. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Bugfix | Medium |
Improved Drone Bay readability and scan speed for faster navigation. Improved Drone Bay readability and scan speed for faster navigation. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Bugfix | Medium |
Enhanced refresh behavior after Drones are created, ensuring immediate UI updates. Enhanced refresh behavior after Drones are created, ensuring immediate UI updates. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Bugfix | Medium |
Added validation around the updated Drone workflow to catch configuration errors early. Added validation around the updated Drone workflow to catch configuration errors early. Source: llm_adapter@2026-06-12 Confidence: high |
— |
| Bugfix | Medium |
Follow‑up fixes improve reliability of phone Companion path routing for desktop command results and error replies. Follow‑up fixes improve reliability of phone Companion path routing for desktop command results and error replies. Source: llm_adapter@2026-06-12 Confidence: high |
— |
Full changelog
This release is focused on Drones.
Making them cleaner to build, easier to launch, and much more useful as saved workflow workers inside Aura.
What’s new
Drones are now more capable workflow workers
Drones have been expanded beyond simple saved prompts into more capable, reusable workers with clearer tool access, write policies, run budgets, setup notes, and output contracts.
That means a Drone can now be shaped around a real repeatable workflow, saved, launched from Drone Bay, and run through Aura’s normal harness instead of behaving like a one-off chat shortcut.
Cleaner Drone creation
Workshop built Drones now save through Aura’s real save_drone_definition path.
Before, some Drone builds could leave behind temporary helper scripts. That was not the right product flow. Now the path is cleaner:
Describe the Drone, build it, save it, see it in Drone Bay.
No manual cleanup. No creator scripts. No weird repo artifacts.
Drone Bay is now a compact roster
Drone Bay has been cleaned up into a tighter, more professional list of saved Drones. The default view is now focused on fast scanning and quick launch:
- Drone name
- short purpose
- write policy
- trigger mode
- last run status
- Run button
- details and actions through the overflow menu
Run history no longer clutters the main Drone list.
Better Workshop-to-Drone flow
When a Drone is saved successfully, Aura refreshes Drone Bay automatically so the new Drone appears without needing a restart.
Companion reliability follow-ups
This release includes follow-up fixes for the phone Companion path, including more reliable routing of desktop command results and error replies back to phone chat.
Drone icon groundwork
A curated Drone icon set has been added as groundwork for the upcoming pinned Drone quick-launch system.
Fixes and polish
- Added the real
save_drone_definitionWorker tool. - Workshop-created Drones now persist through the same DroneStore path as manually created Drones.
- Removed the normal need for Drone creator/verifier scripts.
- Improved Drone Bay readability and scan speed.
- Preserved existing Drone actions like Run, Edit, Duplicate, Delete, and Make Tool.
- Improved refresh behavior after Drones are created.
- Added validation around the updated Drone workflow.
Upgrade notes
Existing Drones should continue to work normally.
This is a polish and reliability release, but it also lays the foundation for Drones to become a much bigger part of Aura’s workflow system.
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]