Keep it running
Updating and fixing
Aetox checks for a new version by itself, verifies what it downloaded, and waits for you to restart. If something stops working, the log says why.
The update it does itself
About twenty seconds after it opens, and once a day after that, Aetox asks whether there is a newer release. When there is, a card says so and offers to download it. It does not download on its own.
- It downloadsOnly when you press the button on the card.
- It verifiesThe file's signature and hash are checked before it is allowed to run.
- You restartRestart to update closes the app, applies the update and opens it again. The installer asks Windows for permission once.
If the update does not take
| Installed from | Do this |
|---|---|
| Store | Store › Library › Get updates. Windows owns that build; the in-app updater does not touch it. |
| Installer | Run the newest installer over the old one — settings and chats stay. |
| Portable zip | Close Aetox, unzip over the old folder. Both aetox.exe and aetox-engine.exe must be replaced together. |
| Scoop | scoop update aetox |
The full checklist, including what a half-applied update looks like, is UPDATING.md.
When something is wrong
- Logs
%APPDATA%\Aetox\logs—engine.logplus one file per launch- Settings
%APPDATA%\Aetox— the JSON files the app writes, next toaetox.db- Report a bug
- Settings › About Aetox Harness prepares an issue with the version and a log attached, secrets already stripped
The first things to try
- The model answers with an error — check the key or the sign-in in Settings › Model settings; a key that expires mid-day looks like a broken app.
- It cannot see a file —
.ssh,.aws, browser profiles and Aetox's own key files are refused by design, at every permission level. - A step waits forever — the approval card may be behind the window, or the level is Ask and the call is waiting for a click.
- The window opens empty — read
engine.log; the engine failed to start and the log says which line.