Aura

Highlights

Worker dependency gate removed

Aura no longer turns missing imports into a special dependency setup state that can freeze unrelated reads, writes, or terminal commands.

Workers can now handle project setup the normal way: install dependencies, run validation, and continue the task without getting trapped in a setup loop.

Worker terminal flow opened up

Worker terminal commands are no longer restricted by a narrow validation/install allowlist.

This fixes cases where normal commands like compileall, pytest, source inspection, project scripts, or CLI validation could be blocked or misclassified before the command even ran.

Python tool preflight also no longer blocks commands because Aura thinks pytest, ruff, or mypy is missing. The terminal output is now the source of truth.

Craft stays focused on code quality

Craft remains active as the code-quality gate:

• syntax problems
• placeholder/stub code
• fake implementations
• broad silent exception swallowing
• obvious AI slop
• contract violations

The key change is that Craft no longer participates in dependency/setup maze behavior. Craft guards code quality; validation proves the project.

Project workflow is smoother

Aura now behaves much closer to the intended loop:

read → write → install if needed → validate → repair → done

Aura’s goal is simple: take an LLM and make it produce human like, maintainable code inside real projects.
This release removes two major sources of harness friction that were getting in the Worker’s way. The result is a faster, cleaner, more natural coding workflow.