1.9.9774
Daily-driver build with the safest release cadence.
- Updated
- 9 weeks ago
- File Size
- 515.39 MB
- Release Notes
- Open notes
Stable is the recommended track for most users. Alpha gets you the newest capabilities first.
Daily-driver build with the safest release cadence.
Fastest release track with the newest features and experiments.
Every release stays linked here so you can inspect what changed before you switch versions.
The Export window has been improved. You can now set packing parameters directly there, and also specify the pack name and description.
This still is not the final version of the flow. The goal for the next two months is to bring it to a point where you can assemble a working mini-app in 10-15 minutes, have AI write it for you, upload it in one action, and immediately share it with anyone interested.
Right now we are roughly 70-80% of the way there, especially after the latest fixes.

The in-app update window has also been improved.
It is now easier to navigate the changelog:
RU and EN patch notes directly inside the update window

Free limits were added to EyeAuras AI Gateway.
This was done so everyone can have AI available right away, without needing to register an OpenAI account, add budget there, or pay for a subscription. This is especially important for users in Russia, where direct access to OpenAI is still blocked.
For most users, AI will probably be more of a reference tool: quickly look something up, ask a one-off question, understand a topic, and move on. I hope the free limits will cover exactly that kind of use. For full-scale coding and serious scripting, they most likely will not be enough.
Important: AI is expensive. I reserve the right to keep adjusting these limits, their availability, and the general usage rules as the feature starts seeing real load. The program is free, and I still want at least some AI access to be available to absolutely everyone, so we need to find a balance.
In simple terms, EyeAuras Gateway is a special server address that you can put into the AI profile in the OpenAI Endpoint field, next to API Key and the other settings.
From the user's point of view, it is almost the same as a regular OpenAI profile, except that instead of the standard endpoint you use EyeAuras Gateway.
This is mainly useful for people who do not want to create their own OpenAI key, or who live in Russia. If you already have normal access to OpenAI, direct OpenAI is usually still the simpler option.
EyeAuras Gateway now supports two modes.
This is the main mode. You use AI as an EyeAuras user.
In this mode, you do not need your own OpenAI account. This is how the free limits work: the OpenAI costs are covered on the EyeAuras side, and you simply use AI inside the program.

This is the fallback mode. In it, Gateway does not pay for anything on your behalf and simply forwards requests to OpenAI servers using your own key.
This is only needed for users in Russia.
In short:
Gateway - you want to use AI without your own OpenAI accountProxy - you already have your own key, but need a convenient path to OpenAIImportant: in Proxy mode, your personal OpenAI key passes through EyeAuras servers. Technically, I tried to make this as safe as possible and avoid storing or logging anything unnecessary, but it is important to understand how the setup works.
Support for Codex was added. In my opinion, it is one of the strongest AI assistants available today.
From the user side, the idea is roughly the same as with regular ChatGPT: you give it a task, and the assistant tries to solve it using every tool available. The key difference is that Codex tends to dig much deeper into the problem, re-check its conclusions more often, and usually produces stronger results on complex technical tasks.
Right now, Codex and Claude Code are driving a lot of practical AI programming forward, and now this kind of integration is available here as well.
For now, Codex is not running at full power yet: not all the wiring is connected. For example, I intentionally have not connected it to the scripting system yet, even though that is one of the main future use cases and one of the reasons it was added in the first place. Automatic behavior tree generation, writing scripts, self-diagnostics in the style of "why is this not working" - these are exactly the kinds of scenarios where Codex is especially strong. But first, we will spend about a week evaluating the integration quality itself, let it work as a reference tool for now, and then give it more freedom.
The main use case for Codex is complex work: programming, automatic configuration of auras, trees, macros, and similar systems.
Using it just as a reference tool is a bit like using a cannon to shoot sparrows. On top of that, this kind of usage may simply be more expensive, because Codex tends to double-check itself. That is great for quality on difficult tasks, but not very cost-effective for simple ones.
You can always switch between Codex and regular Chat mode, but conversation context is not shared between them.
p.s. The UI is still under active development. This is far from the final version.

StayOnTop button in the window title barSubTree could not be deleted in behavior treesThe new interface has been in alpha for several weeks now, and at this point it looks like the most critical issues have either already been fixed or simply haven’t shown up yet.
For all new users, IsBlazorMode = true is now enabled by default. In other words, new installations start with the new UI right away.

If you are still using the classic shell, I highly recommend at least trying the new interface. It was first introduced here:
We are launching the public alpha of EyeAuras Bot.
This is a bot that lives in Discord, and you can already message it for help with EyeAuras. It knows the documentation and can help with scripts, settings, and common usage scenarios.

The main usage flow is:
@EyeAuras), and the bot will try to join the conversation and answer your question(s). That said, DM is still the better option, and if you do mention it in a channel, it is best to ask the question explicitly — it is simply more reliable that wayThe built-in AI Assistant inside the app should also be getting smarter.
It now understands EyeAuras-specific details better, gives more useful answers about code and scripts, and in general depends much more on the quality of the local wiki. The better and more complete the documentation is, the smarter the built-in AI becomes.
We also added separate documentation for scripting best practices:
EyeAuras Gateway is also evolving. It is essentially a proxy server on top of OpenAI and is meant to solve two simple problems:
At the current stage, it is a convenient way to try AI through EyeAuras infrastructure without registration and SMS (c).
P.S. that is not entirely true — you do still need an EyeAuras account, but you do not need to pay anything.
Anyone can join testing: if you want access to the current alpha, just message Xab3r in Discord DM.
What matters here:
Read more about EyeAuras Gateway
At the same time, the technical documentation for C# scripting is also being expanded.
A separate article has been added for ScriptContainerExtensions. This is the mechanism that lets you register your own services in the script DI container, connect modular libraries, and build larger scripting scenarios, mini-apps, and packs in a cleaner way.
In short, this is an important topic for anyone who has already outgrown a single Script.csx and wants to build a more modular architecture on top of EyeAuras.
The entire wiki is now available in both Russian and English.
The translation is done automatically through AI, so if something looks awkward or the meaning gets distorted in the English version, please let us know:
/limit-usage and /configured-limitsstop button no longer lets any channel participant stop someone else’s request@everyone, role, or user pingsResponses API: added streaming responsesTool Calls, Reasoning, and Telemetry togglesShow Settings windowIsBlazorMode = true)Небольшой follow-up после 9374, все еще вокруг AI.
Теперь в EyeAuras по умолчанию создаются два AI-профиля:
OpenAIEyeAuras GatewayЭто делает старт чуть проще: можно либо сразу использовать свой ключ, либо иметь под рукой уже готовый gateway-профиль, если вам открыт доступ к этой альфе.

OpenAI и EyeAuras GatewayГлавная новая фича этой сборки - встроенный AI Assistant.
Теперь прямо внутри EyeAuras есть отдельная AI-вкладка, в которой можно:
OllamaEyeAuras AiGatewayЭто пока ранняя альфа, но уже сейчас AI можно использовать как встроенный справочник и точку входа в более плотную AI-интеграцию внутри EyeAuras.

%EYEAURAS_TOKEN% и EyeAuras Gateway для AI-профилейSharePreview
Bindings мог не всплыватьSend Sequence мог не раскрываться как ожидаетсяTransition to the new UI, a major sublicenses rework, EyePad, mini-app workflows, and the first steps toward tight AI integration directly inside EyeAuras.
The moment I have been preparing for over the last two years is finally here: the transition from WPF to Blazor.
The UI for all triggers, actions, and overlays has been rewritten. To switch to the new interface, you can either use the button in the window header or enable New Shell in settings.
For the next few months, it will still be possible to switch between the old shell and the new one, but eventually only the new one will remain. I will do my best to make it better than the old one in every possible way.

What to expect:
*Search nodes inside behavior trees; we will test that code in the good old triggers first, and then the same preview and related functionality, such as effects, will move into behavior trees and macros as well
First, a quick reminder of what sublicenses are. Sublicenses are licenses issued by authors of packs and mini-apps that do something useful. It can be a clicker, a fishing bot, a tool, or anything else. The idea is that you can build such a mini-app and start distributing keys for it however you like.
With the current EyeAuras capabilities, the level of customization is already extremely deep. In practice, you can build a new program where automation, licensing, protection, updates, and similar infrastructure are already there by default.
In parallel with scripting improvements, I am continuing to develop EyePad — a special EyeAuras launch mode focused on code, execution, pack import, and working with .sln files through Live Import.
In practice, EyePad is a working shell for the flow "write code and run it immediately":
.csx or .cs file.sln and work through an IDEThis is no longer just "a script editor inside EyeAuras." It is a separate workflow for people who want to stay closer to code and switch faster between development and execution.
Mini-apps are the next level. Here EyeAuras is used not just as a host for a script, but as the foundation for something very close to a standalone application.
The idea is that you:
This is where packaging, script protection, custom login, sublicenses, and the full distribution story for your own tool or mini-app fit together really well.
The connectivity situation for users in Russia is not getting better, only worse, so I added a new setting that should make life easier. Automatic server selection tries to find the nearest available hub. Right now there are two of them: one in Saint Petersburg and one in Frankfurt. If needed, I can add more later — there is already hardware in Helsinki and Vladivostok.

The editor now has smarter highlighting, InlayHints, better signature help, and navigation to the selected symbol (CTRL + click / F12). There is also ILSpy integration now, which makes it much easier to inspect external types and assemblies directly from the editor.
Compilation is also faster — around 30-40% on larger scripts, and around 0-5% on small ones (one file, 200-300 lines). Overall the editor should feel more responsive now; it was very constrained inside the old shell.

Below is a small teaser of where the next layer of tooling around scripting, EyePad, and mini-app workflows is heading.
The screenshot shows the AI Chat tab. This is part of the idea of tight in-app AI integration directly inside EyeAuras. The goal is to make AI available not somewhere "next to the app in a browser tab," but inside the program itself:
Some of this already exists in alpha, some parts are still being polished, but the overall direction is clear: make it possible to develop scripts and auras with dense AI support, and eventually build mini-apps where AI is simply part of the product out of the box. I think that is the future.

Semi-Offline is now the default mode. Very briefly: it is a way to survive temporary disconnects, restarts, and crashes without instantly losing access — more here...PK_SublicenseStates)ScriptEmbeddedResourceFileProviderEmbedded Resources and StaticWebAssets support for NuGet packages — especially useful for UI components and packages that bring their own web assetsNuGet and package references should now make it into packed builds more reliablySendInputController that could show up in Ctrl+V scenariosWindowListProvider: когда заголовок окна обновлялся, EA теряла окно на 1 кадрGetThreads, VirtualQuery и GetMemoryRegionsIComputerVisionExperimentalScriptingApi был недоступен в SDKCould not build the proper workspace state, please report this errorAdded new RU hub which should allow to circumvent issues with RU-region accessibility. Please report if login still won't work.

EyeAuras.ImGuiSdk , 0.1.42 - markdown editor, animations, composite buttons, fonts integration, images, caching, etc.RegisterViewType(Type viewType, Type dataContextType, object key = default) - this allows you to register your own UI widgetsScriptContainerExtensions being re-registered by BT nodes. This lead to singletons not really being... singletons.Масштабные изменения в скриптах и доступных API, переход на новую модель монетизации и многое другое.
Все ограничения, которые присутствовали во Free версии снимаются - более никакого лимита на количество аур, размер скриптов, интеграцию с Телеграмом и т.п.
p.s. Лицензия пока что нужна для отправки сетевых сообщений, однако и это ограничение тоже вскоре будет убрано, как только решу технические моменты, вероятнее всего к следующему релизу

Да. Весь функционал, который был ранее закрыт лицензией теперь доступен всем. В самом ближайшем будущем с сайта будут убраны опции покупки лицензии.
Пока что - да, это связано с тем, как программа защищает свои модули и пока что является неотъемлимой частью системы. В грядущем году я постараюсь пересмотреть этот подход, однако это займет время. Как минимум нужно будет сделать механизм, который позволяет использовать программу в оффлайне хотя бы несколько месяцев.
С развитием механизма саблицензий и мини-приложений (https://eyeauras.net/share/S20251105201607zPUUkZryl4CY), мне кажется правильным сместить фокус в сторону монетизации готовых продуктов, собранных на базе программы, а саму программу при этом сделать бесплатной. Вся накопленная за 6 лет разработки база теперь доступна каждому, я надеюсь это подстегнет авторов, которые до этого сомневались "а стоит ли попробовать что-то сделать".
Дальнейшая разработка будет направлена на упрощение добавления модулей в программу - к примеру каких-то специфических симуляторов ввода, полезных для конкретной игры или готовых мини-приложений, решающих практические задачи. Все это уже можно делать сейчас, однако информации на эту тему мало и она разрозненная. Это будет исправлено.
Пишите в личку, постараюсь помочь с этим неудобством.
В скрипты добавлен очень мощный механизм - теперь вы можете встраивать прямо в свой скрипт целые файлы, будь то картинки, видео, текст или даже DLL/EXE. И далее прямо из скрипта можно с ними работать - отображать в UI, загружать в Триггеры/Действия или просто распаковать на диск для дальнейшего использования. Особенно полезен такой функционал если вы хотите встроить в скрипт какую-то библиотеку, которой нет в NuGet - теперь достаточно приаттачить файл к скрипту и указать, чтобы программа использовала его как зависимость.
Более того, если вы используете C# Script protection, то эти ресурсы будут еще и зашифрованы как часть скрипта, тем самым защищая ваше авторское право и работу.

Доработки в системе перменных скриптов - слегка поменялся подход к обработке исключительных ситуаций, задача - сделать скриптинг более простым для новых пользователей.
Еще с прошлого года в программе есть режим интеграции с IDE, по факту это возможность писать полноценные программы, при этом оставаясь внутри инфраструктуры EyeAuras.
Вы можете редактировать скрипт прямо из JetBrains Rider / Visual Studio или любой другой среды разработки, в том числе и AI-based, к примеру Antigravity от Google. Это упрощает и ускоряет написание даже маленьких скриптов, не говоря уже о больших проектах.
В этой версии более дюжины доработок и оптимизаций, направленных на ускорение времени загрузки и ускорении внутренних механизмов программы.
Тестирование на базе ImGui бота, использующего чтение памяти, показывает, что теперь можно оперировать в диапазоне 2к FPS, это ВКЛЮЧАЯ стоимость операций чтения памяти и парсинга всех необходимых игровых структур. До фиксов цифры были в районе 500 FPS.

Пожалуйста, сообщайте о любых проблемах!
.csproj