Questions and answers

AIWeavio is a Windows desktop program. It runs on Windows 10 and Windows 11.

No, there is no code to write. A bot is assembled from ready-made blocks, where each block is one plain action: "find this picture on screen", "click", "wait two seconds", "if it was found do this, otherwise do that". You pick the blocks you need from a list and join them with arrows; the arrow shows what happens after what. The result is a diagram much like an ordinary flowchart, except this one runs: press Start and the program walks through it, doing exactly what you drew. Values travel along the lines too — the block that searches for a picture hands over the coordinates of what it found, and the click block accepts them, so join those two and the click lands precisely where the picture was. And when a lot of actions come one after another and drawing each as its own block would be tedious, there is a block where the whole chain of key presses and pauses fits on a single line — a full account login, say: click the field, type the name, Tab, type the password, Enter.

AIWeavio works in two modes, and the answer differs for each. The first, and the default, works on top of the client: it looks at the picture of the window — finds an image, a piece of text, a pixel or an object detected by a trained model — and then acts through real input: the standard system path, sending straight into a window, a driver, or an external USB Pico device that the computer sees as an ordinary keyboard and mouse. Nothing reads the game's memory and nothing inside the process is altered, so there is very little here for protection to take issue with. What remains is behaviour: even intervals and repeating movements give automation away faster than any technical marker, which is why the delay, jitter and random click-point settings are worth your time. The most conservative option of the group is Pico, being an external device outright; the driver mode, by contrast, installs a system-level component whose presence is visible. The second mode works inside the client — the in-app input path and reading process memory. It exists for cases the first cannot handle, and it is visible to protection software: reading memory means opening access to the process, and the in-app path additionally loads its own module into the game, which the game can enumerate for itself. There are no guarantees against detection here, and whether to use this mode is your decision.

Yes, with the Object Detection Studio (Pro). It walks you through capturing screenshots, drawing and labelling boxes, exporting a training package, running the training in Google Colab from your normal browser, and loading the finished model back in for live testing.

Scenarios are JSON files. The Scenarios panel supports New / Open / Save / Save As / Export / Delete plus a recent-scenarios list. A scenario file is portable — you can move it between two machines and, as long as both have the same paid features, it opens the same way.

Free covers the whole graph editor, every mouse and keyboard block, classic image and colour detection, files and data (TXT / CSV / Excel), variables, maths and the basic flow blocks, plus Image Lab, the ready-made bot catalog and the AI Agent within the free blocks. Free limits: up to 5 scenarios open at once, up to 100 blocks in a scenario, and only one game window per scenario. Pro adds several game windows, MultiBox, browser and Android automation, neural-network detection, the Object Detection Studio, text recognition, the Memory Viewer, the Scheduler, advanced screen search, web requests and notifications, and parallel branches.

Only one desktop can be signed in at a time. If you sign in on a second computer, the first one gets a "session ended" popup and stops. Web login is separate and isn't affected.

It tells you, but it does not replace itself behind your back. The app checks whether a newer version is out and shows you the download — you install it when it suits you. Optional add-ons from the Components screen are handled separately, and every download is checked for integrity before it is applied.

Windows shows something along the lines of "The code execution cannot proceed because MSVCP140.dll was not found". The file is not part of AIWeavio — it belongs to the Microsoft Visual C++ Redistributable, a free Microsoft component that a great many Windows programs rely on. It is simply missing on your system. Install the Visual C++ Redistributable 2015–2022 (x64) from the Microsoft website, restart the computer, and start AIWeavio again. The link is on our Download page, in the System requirements block. AIWeavio needs all three of those files, so if a different one is named, the same installer resolves it.

That is Windows SmartScreen. It is not a virus report: SmartScreen holds back any program it has not yet seen often enough, and every new build starts out unfamiliar to it. If you downloaded the file from aiweavio.com or from our GitHub releases page, you can proceed — click "More info" in that window, then "Run anyway". Should you have any doubt about where the file came from, delete it and download again from the Download page rather than clicking through.

Optional components include things like the input driver and the memory-reading helper. To do their job they use techniques that automation tools and malicious programs have in common, so heuristic antivirus engines sometimes flag them on sight. Every package we ship is verified by signature, size and checksum before it is applied, and a file that fails those checks is never installed. If your antivirus quarantined a component, add the AIWeavio folder to its exclusions and install the component again. If you would rather not do that, you can simply skip the component — the rest of the app keeps working without it.

Windows 10 starting from version 1607 (the Anniversary Update), and Windows 11. AIWeavio is built as a 64-bit application only, so it will not launch on 32-bit Windows at all. On Windows 10 builds older than 1607 the app closes at startup — it calls a system display-scaling function that those builds do not provide. macOS and Linux are not supported.

Both come down to the same thing — administrator rights. The Components screen offers several tools, and one of them, the external input driver, installs at system level: Windows only allows that with elevated rights, so AIWeavio will not even begin the installation without them. Windows cannot grant those rights to a running program, which is why you need to close AIWeavio and start it again with "Run as administrator", then install the component. The second case looks different but has the same root: some programs and games themselves run elevated, and Windows does not let an ordinary program send input to a window that has more rights than it does. If a scenario runs, the log looks clean, yet the cursor does not move and keys do not arrive — restart AIWeavio as administrator and try again.

Through YooKassa. Open your account dashboard, choose a plan and click "Pay with YooKassa" — that takes you to YooKassa's own page, which accepts bank cards (Visa, Mastercard, Mir), SBP, ApplePay and SberPay. The method is chosen there, and we never see or store your card details. PRO activates automatically once the payment goes through, so there is no need to send us a receipt. If a payment went out but PRO did not activate, please write to us and include the date and the amount.

Whichever suits you: the chat in the bottom-right corner of this site, our Telegram channel, or email at support@aiweavio.com — all of them are listed on the Contacts page. To get a useful answer on the first reply, please tell us your Windows version, which AIWeavio build you are on, and what exactly happens; a screenshot of the error helps a great deal. If the problem is with a scenario, the System Console has a one-click export that packs the logs into a single file you can attach.