← Changelog
v0.19.45Latest· September 6, 2026
A push that lands here and reaches GitHub
- Nobody has to leave GitHub for this to work. Until now, putting Aura in front of a repository meant deciding what happens to everything already pointed at the old address — the build that runs on every push, the review tools, the partner who has your repository in their own dashboard. A push Aura accepts is now forwarded to that host by Aura itself, on every push, without anyone being asked to move. Your team pushes to Aura and the place your integrations watch sees the same commits arrive, as they always did.
- Who owns a branch is an answer you can check, not a convention somebody wrote down. Ownership of a branch is carried by signatures from the people the team already vouches for, so “who is allowed to move main” stops being a line in a document that nothing enforces and becomes something the machine can be asked, and can answer.
- What the project has learned now travels with the name of whoever learned it. A fact shared across your organisation carries the signature of the person or agent that wrote it and where it came from, and the server checks that signature against the key that arrives with it before storing anything. So a colleague’s considered decision reads differently from anonymous prose, and an entry someone tampered with says so out loud instead of quietly passing as true. Alongside it: what kept happening across your sessions gets written down as something the project knows, and the timeline can bring a file back exactly as it stood at a moment you scrub to.
- The token claim finally has a number, and it is not the one on the pitch. Aura has said since launch that it saves tokens. A paired experiment over fifty turns — the same questions, asked with Aura and without — found no saving on a typical turn. What it did find is that the worst turns get much cheaper: the runaway question that reads half a repository is contained, and fewer runs fail outright and have to be paid for twice. That is what the documentation says now, in place of the broader claim, and the harness that measured it ships with the app so you can run it against your own repository.
- Projects stop disappearing. A crashed index of your open copies of a project could hide them from the list with nothing to explain where they went; there is now a scan that finds them and one click to attach them back, and clicking a project opens it immediately instead of after a pause. The cost report stops reading zero while the real figures sit on disk beside it, restoring an old version of a function uses the history Aura was already computing rather than a second one it was throwing away, and Project Health no longer finishes by running the machine out of memory.
Get this release
Installed already? This lands automatically by silent auto-update.
Everything in this release
New
New
A push Aura accepts is forwarded to the host your team already uses, so putting Aura in front of a repository does not move anyone off GitHub
Who owns a branch is carried by signatures from people the team vouches for, so branch ownership can be checked rather than assumed
A fact shared across your organisation carries its signature and where it came from, and the server verifies it before storing it — a tampered entry says so instead of passing as true
What kept happening across your sessions is read back and written down as something the project knows
Scrub the timeline to a moment and restore a file exactly as it stood there
Per-editor setup instructions move into the one file every agent already reads, instead of one more file per tool
A paired A/B harness and a dashboard measure the token question on your own repository
Crew, Team, Trace and Control mean the same four things in the app as they do at the command line
A signed chip in the team feed can be questioned: click it and the machine re-checks the seal, names who sealed it, or says plainly that it could not
Fix
Fixes & improvements
A crashed index hid your other copies of a project with nothing to explain it — they can be found and attached back, and clicking a project now opens it immediately
The cost report answered $0.00 while the provider’s own counts sat on disk beside it
Restoring an old version of a function used a second history instead of the one Aura was already computing and discarding
Recall had a timeline nothing was ever writing to
Looking at your sessions was enough to delete ten of them
The app ran a command-line Aura it was never built against, and nothing noticed
A stopped session told three different screens three different things
Your task board was two stores that could not see each other; the app, the command line and agents now read one board
One project shows as one row, in the picker and in the cloud
The desktop learned its own relay was dead only when the cloud told it
Map, Trace and Impact were reading the wrong thing — three screens, one cause
aura ask answers from what this repository recorded, not from whatever is newest
A finished piece of crew work links the commit it produced, and a grant says what it binds
Faster
Faster
Project Health finished by running the machine out of memory
Breaking
Breaking changes
The documented token saving is narrower: no saving on a typical turn, a contained worst case, and fewer failed runs