1.9.9109
Daily-driver build with the safest release cadence.
- Updated
- 15 weeks ago
- File Size
- 485.43 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.
A small patch focused on improving window responsiveness under load and helping your packs appear in search results faster.
New Memory API documentation for C# scripts has been added. It gradually explains the core memory model in EyeAuras: which backends are available, where to start, how to find a code cave, how to plug in your own IProcess, and how to build custom memory backends.
Useful entry points:
New signed fields were added to UserLicense in the internal licensing APIs, and sublicenses now expose an explicit MaximumSessions.
var license = GetService<ILicenseAccessor>();
Log.Info($"UserId: {license.UserId}");
Log.Info($"Roles: {string.Join(", ", license.Roles)}");
Log.Info($"AppVersion: {license.AppVersion}");
if (license.ShareSublicenses.Length > 0)
{
Log.Info($"MaximumSessions: {license.ShareSublicenses[0].MaximumSessions}");
}
Read more: Pack sublicenses
IProcessControlApi now includes explicit FreeMemory(...) and ProtectMemory(...) methods. That means an allocated region can now go through the full lifecycle properly: get it through AllocateMemory(...), change protection, perform the required actions, and then release it cleanly.
using System.Diagnostics;
using EyeAuras.Memory;
using var process = LocalProcess.ByProcessId(Process.GetCurrentProcess().Id);
var control = (IProcessControlApi) process;
var region = control.AllocateMemory(
IntPtr.Zero,
4096,
MemoryAllocationType.Commit | MemoryAllocationType.Reserve,
MemoryProtectionType.ReadWrite);
var oldProtection = control.ProtectMemory(region.Address, region.Size, MemoryProtectionType.ExecuteRead);
control.ProtectMemory(region.Address, region.Size, oldProtection);
control.FreeMemory(region);
Read more: Memory API - Getting started
BlazorWindow resizing and dragging were significantly improved, so windows should behave better under loadsublicense limits to the internal licensing APIsScryde detectionC# scripts now have a Properties button that opens a separate script properties window. It brings the main settings and dependencies together in one place: Overview, NuGet package management, References for internal and external assemblies, and Embedded Resources for files that should be distributed together with the script.

Learn more:
Codex now understands EyeAuras-specific details better, so it should be more useful for complex technical tasksExport and Import dialogs to make them more convenient to useBlazor windows, where the window could suddenly jump to the sideICodeHighlightService errorCodex inside EyeAuras keeps getting a more practical UX: separate threads, a clearer workflow, and in general a more usable mode for complex coding tasks.
If the regular AI Assistant works better as a quick in-app chat and reference tool, Codex is already better thought of as a separate mode for heavier technical work.
Read more about AI Codex Coding Assistant

The Export / Import flow is also continuing to improve. It is now a much clearer and more convenient way to publish packs, update them, and import them back with previews and proper options.
Read more about Export / Import

EyeAuras Gateway budget monitoringThis update is mostly focused on bug fixes and polishing a few parts of the UI.
Added code rendering in dedicated blocks.

Added budget and limit display. Just hover over the status next to your profile.

Export when Binaries Only mode is enabledThe 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)This is a small follow-up to 9374, still focused on AI.
EyeAuras now creates two AI profiles by default:
OpenAI profileEyeAuras Gateway profileThat makes the first setup a bit easier: you can either use your own key right away or already have a ready-made gateway profile if you have access to that alpha route.

OpenAI and EyeAuras GatewayThe main new feature in this build is the built-in AI Assistant.
EyeAuras now has a dedicated AI tab inside the app where you can:
OllamaEyeAuras AiGateway when neededThis is still an early alpha, but even now it is already useful as an in-app reference and as the first practical layer of deeper AI integration inside EyeAuras.

%EYEAURAS_TOKEN% and EyeAuras Gateway in AI profilesSharePreview crash
Bindings editor would not pop upSend Sequence would not expand as expected