Questions

A web assistant answers your question and you go do the rest yourself. Aetox finishes the job. Because it is on your machine, it can open real files, write real files, open real websites and click real buttons.

What you get back is a file in your folder, not text in a chat box you have to copy and paste onwards.

No. You type in plain language what you want, and it handles the rest. There is an assistant door set aside for work that is not coding.

To be honest, the 8 built-in presets lean toward web and code work. For anything else you command it in plain language as usual, and keep the instructions that work to reuse yourself.

Conversations and work files live on your machine alone. We have no middle server, keep no usage statistics, and there is no account. With a local model the data never leaves your machine.

If you enter another provider's key, what you type goes from your machine to them directly, not through us. The key is encrypted to your Windows account, kept in its own file, and stripped from the log. One limit to state: that encryption is Windows-only, which is one reason it ships on Windows only for now.

With a project open, it stays in that folder plus the ones you added. With no project open, it sees the whole machine, and the files it writes land in that session's output folder.

What it can never open in any mode is the key and password stores: .ssh .aws .gnupg, the Windows credential store and every brand's browser profile. How often it asks first depends on the permission level you pick; publishing anything outside is asked about at every level, and every command is logged.

These rules are checks in Aetox's own code, not an operating-system sandbox. On a machine with data you cannot lose, give Aetox an API key of its own and run it in a VM or Windows Sandbox.

The program is free. No subscription of ours, no paid tier, no account to sign up for.

With a local model there is no cost at all. With another provider's key, you pay them for what you use. We are not in the middle and add nothing on top.

No. Aetox is free to use, install on as many machines as you like and use for commercial work, but the licence forbids modifying, redistributing, rebranding or selling it. Skills, agents, prompts and MCP servers you write yourself are yours, and you can sell them.

Source in the public repo stops at v1.7.0 and stays there to read and audit. Later releases ship as installers only, so the build you run has no source to read.

What you can check without source: every release has a checksums.txt with each file's SHA-256, signed with the app's update key, and builds after 21 Oct 2026 include an sbom.txt listing every Go module and web package that went in. The Microsoft Store build is signed by Microsoft.

The program takes 124.8 MB in two files: the window and its engine. Any ordinary machine opens it comfortably.

What takes the power is the model. To run a local model yourself you should have a decent amount of RAM to spare. With another provider's key, your machine barely has to work at all.

Yes. You can schedule an Aetox chat to run on its own, and see every scheduled job in the command center. Jobs run while Aetox is open; a run missed while the machine was off happens once when you open the app again. For work that must keep running with the machine off, n8n or Windmill is still the better fit.

Uninstall from Windows' Add or remove programs as usual. There is no account to go delete, and no data of yours left anywhere except on your own machine.

Not yet. Right now it does Windows first and well, because there is one person writing it and they use Windows every day for real work.

The engine already compiles on Linux and macOS, but the browser part and the key encryption are not done there yet. Other systems are the plan after this.