Skip to content

v1.4.6 - Reliability, project toolchains, and safer edits

Choose a tag to compare

View all tags
@CarpseDeam CarpseDeam released this 04 Jun 22:29
1.4.6
270d0d0

Aura IDE v1.4.6

This is a reliability and workflow release focused on making Aura feel smoother, stricter, and less noisy during real development.

Highlights

Safer edit mechanics

Aura’s edit transaction layer is now more resilient when applying model-generated changes.

  • Added deterministic exact-text recovery for edit transactions.
  • Improved handling for newline-normalized, trimmed-whitespace, and surrounding-context matches.
  • Ambiguous or unsafe matches now fail clearly without mutating files.
  • Same-file edits are applied against an updated in-memory buffer instead of stale disk state.
  • Edit failures now include structured details like failed operation, reason, candidate count, and context.
  • Recovery exhaustion now reports the actual failed edit operation instead of vague follow-up noise.

Better Worker outcome truthfulness

Worker results now distinguish more clearly between different kinds of failures and caveats.

  • Unrecovered edit-mechanics failures remain blocking.
  • Recovered edit failures no longer poison later successful writes.
  • Files changed without validation now correctly require follow-up.
  • Modified file reporting is deduped.
  • Environment caveats are no longer misclassified as edit failures.
  • Missing local tools/dependencies are reported as environment setup issues, not fake code validation failures.

Project-local toolchain support

Aura now respects project-local development environments instead of assuming global tools.

  • Added a generic project toolchain layer.
  • Added Python .venv detection as a Python-specific adapter.
  • Python validation now prefers the project .venv interpreter when available.
  • pytest, ruff, and mypy are only run when available/requested/relevant.
  • Aura no longer treats missing global pytest as a code failure.
  • Global installs are blocked by default unless explicitly approved.
  • Non-Python projects are not treated as Python projects.

Language-agnostic workflow preservation

Aura remains a general coding harness, not a Python-only IDE.

  • HTML/CSS/JS projects do not get Python venv behavior.
  • Non-Python projects avoid pytest/py_compile assumptions.
  • Project-local toolchains are handled generically, with Python support scoped behind the Python adapter.
  • Validation behavior now depends on the project and task instead of hardcoded Python assumptions.

GUI and workflow polish

  • Improved live Worker summary behavior so task completion is visible immediately instead of only after reload.
  • Improved bottom-of-chat spacing/scroll behavior around the input panel and active spec cards.
  • Reduced UI weirdness around final summaries, spec card cleanup, and bottom scrolling.
  • Added protection around syntax highlighting so highlighter failures should not spam the console or destabilize the UI.

Validation

Focused validation passed for:

  • edit transaction reliability tests
  • Worker edit recovery tests
  • project-local Python environment tests
  • terminal policy tests
  • prompt/toolchain behavior tests
  • focused dispatch classification tests
  • py_compile on changed Aura modules

Why this release matters

This release is aimed at reducing Worker thrash during normal coding work.

Aura should now be better at:

  • applying edits safely
  • recovering from edit mismatches
  • telling the truth about what happened
  • using the right project environment
  • avoiding bogus validation failures
  • keeping Python behavior scoped to Python projects
  • making live task completion easier to trust

In plain terms: Aura should feel less brittle, less noisy.

Assets 3
Loading