Changelog

What changed in each release. Autonoma updates itself from a signed feed, so an installed copy reaches the latest version on its own.

5.4.1 Current

Released 2026-09-07

Fix

  • The previous 5.4.0 release inadvertently shipped with an older aegis.exe executable. This hotfix correctly packages the newly compiled Rust binary.

5.4.0

Released 2026-09-07

Added

  • Full Reverse Engineering Toolkit Parity and RAE Engine Integration
  • 44 unique command families from the Rust aegis CLI ported into the Python backend (re_engine.py) and React UI.
  • Wired advanced engine modules including api_har_capture, api_static_analyzer, api_memory_analyzer, and defense_bypass.
  • Added complex subcommands for Stratum protocol analysis, Logic Inversion, Spoofing, and Frida-based Defense Bypass.

5.3.3

Released 2026-08-16

Fixed

  • The Service panel could not see a service that was running. System → Service showed "Could not read service status" over a row of dashes while the background service was up and answering in a few hundredths of a second. Nothing had failed — the app was throwing away a perfectly good answer because it arrived in a slightly different form than the screen expected.
  • Five more screens had the same fault and nobody had noticed: the first-run setup checklist, the keystore location panel, the Overview live report, the AI and Evolution health section, and the system health readout. Only the Service panel was visible enough to be reported.

5.3.2

Released 2026-08-12

Fixed

  • Save As lost the file it said it had saved. Saving under a new name from the command palette marked the tab as saved and wrote nothing to disk. With more than one file open it also renamed the wrong tab.
  • Mining reported that it had started when it had not. Mining is off until you turn it on, so pressing Start on a new installation was refused — and the app showed a green "Crypto miner is now running" message anyway. Stopping had the same fault.
  • The social composer showed an empty platform list however many accounts were connected.
  • Acknowledging a system health alert did nothing and the alert returned on the next refresh.
  • Adding or removing a git remote in the IDE asked for the details and then did nothing.
  • Requesting a language’s text never reached the code that reads it, so the app fell back to English without saying why.

Added

  • Data protection: export a copy of the personal data this installation holds, erase it on request, and export the audit trail. Required by Quebec’s Law 25 and the GDPR.
  • An AI assistant in the code editor: explain, review, suggest improvements, complete, refactor, generate tests, fix an error. Answers go into the undo history and leave the file unsaved.
  • Mining now states what turning it on costs — full load on your processor or graphics card, and electricity you pay for that can exceed what is mined — before offering the switch.
  • Video generation names the exact setting each missing provider needs, and refuses to start a job that cannot finish.

Changed

  • The Features tab reports what actually works on this machine. It used to say every feature was active on a new installation with no keys set. It now separates ready, needs setup and not checked, and names the key, program or package each blocked feature is missing.
  • Removed controls that never did anything: Split Editor and Close Split, and three shortcuts labelled DeFi, Staking and Bridge that only opened other companies’ websites.

5.3.1

Released 2026-08-11

Fixed

  • Paid features were handed out to everyone whenever the module that reads your plan failed to load: the entitlement check answered yes and the quota check reported an unlimited allowance.
  • Encrypting your API keys reported success while writing plain text, when the encryption library was missing.
  • A damaged account file could let a stranger in as administrator.
  • The audit log is preserved when it cannot be read, instead of being replaced.
  • The local lock reported itself as on when it was not.
  • Breakpoints, continue and pause now reach the debugger.
  • A rejected git push is reported as a failure rather than a success.
  • The terminal reports what actually happened when a command or a kill fails.
  • A failed request is no longer retried in a way that could send a payment twice.

5.3.0

Released 2026-08-07

Added

  • API keys settings screen covering every provider in the catalogue, each configured with your own account. Nothing ships with a credential.
  • Credential store encrypted at rest with a key generated once per installation.
  • Connected accounts for social publishing: several accounts per platform, each with its own credentials, connected by sign-in, API keys or a webhook URL.
  • Custom webhook accounts. The URL is stored and held encrypted; no sender posts to it yet, and the app lists it as unable to publish for that reason. This line used to claim it reached Slack, Teams, Zapier, Make and n8n.
  • Social Studio: quote card composer, batch planner, approval workflow and plan export.
  • Dry run mode, which simulates irreversible operations and journals what would have happened.
  • Signed releases. Installers carry an Ed25519 signature and the app refuses any update that does not verify.
  • Licence key system. Keys are verified cryptographically on your own machine, so the first run needs no connection.
  • Licence server check, asked only whether a licence has been revoked — never whether it is genuine. If it cannot be reached the app keeps working for a further thirty days.

Fixed

  • Crash recovery never worked in any previous version. The session marker was read before the thing that wrote it ran, so no crash was ever reported.
  • Saving an API key rewrote your .env file by splitting every line on "=", destroying comments, blank lines and section headers. It also wrote to a location a standard user cannot write to once installed.
  • A .env reload could silently overwrite a credential entered in the interface, making the settings screen appear to do nothing.
  • Six defects in the update path.
  • Window layout, geometry and last-open tab were lost on upgrade from the previous product name.
  • Rendering no longer assumes a fixed refresh rate, so high-refresh monitors are used properly.

Changed

  • Posts now target a specific connected account rather than a platform, so several pages can be run side by side.
  • A post addressed to a disconnected account can no longer be approved or published.
  • Installer reduced from 625 MB to 567 MB by removing packages that were being copied in despite being excluded.

2.4.0 to 5.1.0 — not recorded

No changelog was kept across these releases. Rather than invent entries after the fact, the gap is left visible. Whether a specific change landed in that window is a question that can be answered properly from the source rather than guessed at — see contact for how to reach us, and what is not working yet.

2.4.0

Note

  • The last release before the recorded gap.