September 15, 2026 · 3.0.0-alpha.62
A closed permission hole, and work that resumes itself
A shell payload can no longer launder a forbidden command past the risk ladder. Work stopped by a provider's allowance now says so and comes back on its own, and a stalled automation no longer silently skips every night after it.
- Fixed
Security: a shell payload can no longer launder a forbidden command. sudo inside bash -c graded as merely high risk — which a saved rule could auto-approve — and env sudo graded low, running with no prompt at all. Wrappers and argument carriers are now graded by what they actually hand to the machine, and a stored rule can never answer for a high-risk action
- New
Work that stops because an agent ran out of its provider's allowance now says so, and comes back on its own when the allowance returns — with a notification at both ends, and an idle agent picking the work up when there is one
- Fixed
A scheduled automation whose mission stalled used to stay 'running' forever, so every later occurrence was silently skipped. Missions now close their run, and one waiting on capacity no longer blocks the next night
- Fixed
Runs record what they actually cost, and a restart explains why it paused your task instead of demoting it silently
- Improved
Setup & System Health guidance, dismissible getting started, and composer ridgeline styling
- Fixed
Mac and Windows desktop update manifests and standalone CLI installers are available together on the public release
- Improved
CLI browser-based password entry accepts uppercase letters, symbols and pasted passwords
- New
velora tasks --json, velora approvals --json and velora run --wait-for-capacity, so a script can read what is waiting and see work through a provider limit