Eddie Desktop edition 2.26.2 released

[vhorfurz 2]

On 9/2/2026 at 4:50 PM, JesusxSaves said:

At this point the dev should use AI to write and verify the code. Give me the source code and i do a new UI, split-tunneling and other needed futures withing days with only vibecoding with AI. took me 2 weeks to write 2 complex android games with AI. Started a month ago with all of this. Really cant understand why the devlopment takes literally ages with AirVPN. Split-tunneling should have been here since years, same as a new UI. Its high complaining i understand but opening Eddie feels/looks like i run a XP application on Windows 11.

Hello JesusxSaves,
This thread began on 21 August with the announcement of the release of Eddie 2.26.2 Desktop Edition.
On 2 September, I realised I’d overlooked this announcement regarding the release of the ‘stable’ version; I tested it again without success, and posted a comment to say that my issue with launching eddie-ui was still unresolved.
Three hours later, you posted a comment beneath mine criticising the Eddie/AirVPN developers, writing that you’re capable of doing better than them at writing an entire graphical VPN client program using LLMs, and adding that you easily create games on Android using vibe coding.

Perhaps I’m mistaken, but I get the slight impression that you’ve taken advantage of my post—in which I expressed my frustration at being stuck on version 2.25.1 of eddie-ui—to vent your own frustration.

Even if the fact that you posted your message three hours after mine is a coincidence, I do not wish to be associated with what you wrote, and to remove any ambiguity: I am completely opposed to what you are claiming.

I find that the way you phrase your criticisms in this post is rather inelegant, and disrespectful towards the eddie/AirVPN developers.

It is possible that forum readers who are curious and keenly interested in all things relating to the vibe coding scene might be unduly influenced by the way you phrase your comments, and that this could lead to a certain amount of harmful pressure being placed on the eddie/AirVPN developers. That is why I would like to add my own perspective below:

• Low-level vs Graphical User Interface: The server and client software developed by the eddie/AirVPN team falls under the SECURITY category (not the Android gaming category). This requires a sound low-level understanding of operating systems, expertise in constantly evolving network protocols, security monitoring, and the ability to respond swiftly should any vulnerabilities be discovered. For security software developers, focusing on the low-level aspects is always a PRIORITY over the higher-level graphical user interface. The graphical user interface of the free software eddie-ui is becoming outdated, but it is not fundamentally incompatible with operating systems (for the time being). It is important to note that, despite all its minor flaws, eddie-ui remains a remarkable piece of software. Unlike the ‘flashy’ software from major VPN companies, the graphical user interface of the open-source eddie-ui is designed first and foremost with the aim of providing maximum freedom for the end user: it offers a vast range of configuration and customisation options, even in its mobile versions. All these graphical user interface controls, which allow for very fine-grained configuration of the underlying VPN client software (OpenVPN + WireGuard), must certainly have required a great deal of development time. I think that this freedom of choice for the end user is a hallmark of the eddie/AirVPN team’s ethical commitment. This is the spirit of free software as taught by Richard Stallman and the Free Software Foundation.
• Money: Companies with plenty of money tend to completely rewrite their software and graphical user interfaces in Rust, which automatically eliminates certain programming errors that can occur in C++. But AirVPN is a small organisation that has no intention of becoming a start-up funded by private equity.
• Vibe coding: LLMs are powerful tools for computer programming. But they must be used wisely and with great caution. Starting to have an LLM agent do all the work from A to Z by giving it interface objectives amounts to taking the very high risk of no longer manually checking the underlying code (see the French case of Benjamin Code), and of introducing security vulnerabilities. Just a few days ago, on 30 August 2026, reputable figures such as the Debian developers decided to authorise the use of LLMs in the Debian project, in accordance with a clearly defined code of conduct that may evolve (General resolution: LLM usage in Debian: Results). The eddie/AirVPN developers are also serious people, but they’re a small team → Please don’t put pressure on them. They’re professionals and they’re evolving just like everyone else. They know how they need to work...

[spinmaster 31]

I do still have this error from time to time, after multiple connects so that I have to quit and restart Eddie. After a clean restart of Eddie, it works for most of the time until I do a lot of additional connects. I am on macOS 26.5.2

Is there any indication on why and when this error could occur?

 

 

[George123 6]

On 8/25/2026 at 10:49 AM, FerretMaster said:

Does not work on macOS Tahoe..
"Unable to obtain elevated privileges (Required): Unable to Start (Client not allowed: integrity check failed)
At least the old version could be made to work by changing permissions on wg/wireguard. This one doesn't work at all. ;-(

I have the same issue on macOS 15.17.9.

Please, please Clodo... can we get a macOS Eddie that is functional out of the box, without having to faff around changing permissions in the Terminal just to get it to work? 

I really want to use Eddie for the fastest server selection, and Network Lock, but these permissions issues have been going on for quite some time. See also https://github.com/AirVPN/Eddie/issues/142 which has received no response at all from the developer since January 2025. 

I can't imagine this would take long to fix?
 

[OWild 7]

On 9/2/2026 at 1:40 AM, vhorfurz said:

Please do something to fix this privilege escalation bug with pkexec.

@Staff
I have similar issue, since with 2.26 version the "Don't ask privilege escalation every run" option in preferences doens't work no more.

Back to 2.24.6 solve the issue (I have to delete my /home/.config/eddie profile)

Operating System: Debian GNU/Linux 13
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.13.0
Qt Version: 6.8.2
Kernel Version: 6.12.57+deb13-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-2500K CPU @ 3.30GHz 💪 Edited ... by OWild
issue partially solved

[Clodo 182]

On 9/4/2026 at 4:34 PM, spinmaster said:

I do still have this error from time to time, after multiple connects so that I have to quit and restart Eddie. After a clean restart of Eddie, it works for most of the time until I do a lot of additional connects. I am on macOS 26.5.2

Is there any indication on why and when this error could occur?

 

 

Please, when happen, open a ticket and paste the Log > Lifebelt > Upload report url, thanks

[Riesengebirge 0]

I tried to go back to version 2.24.6, so I uninstalled the program, made sure there were no leftovers and installed that version. I was unable to start Eddie again - I kept getting this window asking for a password, and it isn't my account's password. The only thing that made the program work again was to reinstall version 2.26.2. Windows 10 LTSC Enterprise 64-bit.

[OWild 7]

7 hours ago, Riesengebirge said:

I tried to go back to version 2.24.6, so I uninstalled the program, made sure there were no leftovers and installed that version. I was unable to start Eddie again - I kept getting this window asking for a password, and it isn't my account's password. The only thing that made the program work again was to reinstall version 2.26.2. Windows 10 LTSC Enterprise 64-bit.

@Riesengebirge the answer is here :
 

On 9/7/2026 at 8:59 PM, OWild said:

Back to 2.24.6 solve the issue (I have to delete my /home/.config/eddie profile)

I didn't find any other solution. I guess you can find where is the eddie profile in windows 10 blablabla and then delete it.
Or you can try the 2.27 (beta) version.

[Riesengebirge 0]

19 hours ago, OWild said:

@Riesengebirge the answer is here :
 
I didn't find any other solution. I guess you can find where is the eddie profile in windows 10 blablabla and then delete it.
Or you can try the 2.27 (beta) version.

I install Eddie in D:\Net\AirVPN. I try to keep programs out of the Windows directories as much as possible. Anyways, I checked the C drive for any leftovers and also deleted what was left in my install folder. Nothing helped. Installing 2.27 beta will probably work - as reinstalling 2.26.2 did - but I should definitely be able to install the immediate previous version of a program without going through this much trouble. Edited ... by Riesengebirge

[Staff 10640]

34 minutes ago, Riesengebirge said:

not being able to install the immediate previous version of a program is simply ridiculous.

Hello!

The problem is different. You pretend a downward compatibility of a configuration file with a previous software version and this is not guaranteed in general. This is the problem. You can downgrade at will Eddie, but remember that you must purge the higher version of the configuration file because sometimes it may contain new supported options, directives, fields for new features and so on that can't be parsed by the older software. This is true for any software, not only for Eddie, and it is not at all ridiculous, it is correct and sometimes strictly necessary for a natural evolution of any software relying on a configuration file. According to nowadays conventions and Microsoft recommendations the configuration file is stored by default in the AppData directory of the user who installed Eddie. See also:
https://eddie.website/support/data-path/
 

Quote

I've been using Windows since 95 and have never seen anything like this. 

You think you have never met this case in 31 years of Windows usage exactly because you've been using Windows for 31 years. 😋 Forgive us, this was irresistible... 

Kind regards
 

[Riesengebirge 0]

19 hours ago, Staff said:

Hello!

The problem is different. You pretend a downward compatibility of a configuration file with a previous software version and this is not guaranteed in general. This is the problem. You can downgrade at will Eddie, but remember that you must purge the higher version of the configuration file because sometimes it may contain new supported options, directives, fields for new features and so on that can't be parsed by the older software. This is true for any software, not only for Eddie, and it is not at all ridiculous, it is correct and sometimes strictly necessary for a natural evolution of any software relying on a configuration file. According to nowadays conventions and Microsoft recommendations the configuration file is stored by default in the AppData directory of the user who installed Eddie. See also:
https://eddie.website/support/data-path/
 
You think you have never met this case in 31 years of Windows usage exactly because you've been using Windows for 31 years. 😋 Forgive us, this was irresistible... 

Kind regards
 

You're assuming a lot, aren't you? After uninstalling v2.26.2, and before trying to reinstall the previous version, I triple checked and there were no Eddie leftover directories anywhere in the system drive. Just for the sake of clarity, I did the whole process again, and this time the v2.26.2 uninstall DID leave Eddie config directories behind. It would seem to me that your uninstaller behaves erratically at times. And yes, a well written installer should be smart enough to detect config files from previous versions and, if it's unable to gather useful info from them, at least overwrite them, resetting the config.

Were you even alive and already programming 31 years ago? Forgive me, this was irresistible... Edited ... by Riesengebirge

[Staff 10640]

4 hours ago, Riesengebirge said:

I triple checked and there were no Eddie leftover directories anywhere in the system drive. Just for the sake of clarity, I did the whole process again, and this time the v2.26.2 uninstall DID leave Eddie config directories behind. It would seem to me that your uninstaller behaves erratically at times.

Hello!

If you run Eddie's uninstaller script for Windows, it does not remove the configuration file in the user's directory. It leaves both the directory and the configuration file inside it, including default.profile. This is intentional as uninstalling a software does not mean purging all the configuration files that can be preserved. No erratic behavior has been detected, it's just a script.

Quote

a well written installer should be smart enough to detect config files from previous versions and, if it's unable to gather useful info from them, at least overwrite them, resetting the config.

This would be catastrophic in many cases. Firefox, Thunderbird, GitLab, Microsoft SQL SRS and probably hundreds of other programs do not support inverse migration (downgrade) in general, exactly for this problem. In case of a downgrade for which the configuration file becomes incompatible with the older version, deleting or overwriting the configuration files etc. will cause serious or, in case of absence of a recent backup, even dramatic inconvenience to the user.

EDIT - NOTE BY THE DECREPIT FOUNDER
In Eddie, profile preservation has an excellent side effect. The profile (encrypted or not) includes the client keys and server information, and Eddie reads them locally when it can't access the bootstrap servers. When you are in a restrictive network, or typically in specific countries (Iran, China, Russia...) the bootstrap servers or the protocol to reach them are not infrequently blocked. In such cases the user must first find another connection method, establish the connection and only then let Eddie contact the bootstrap servers to download the information that will be valuable for future connections. This is a once and for all operation that may be reproducible and performed in the face of potentially great adversity, so minimization of such a requirement is good.
 

4 hours ago, Riesengebirge said:

Were you even alive and already programming 31 years ago?

If we want to have a sad contest to see who’s the most decrepit, we have a good competitor. The founder of AirVPN built his first natural language parser in Assembly and BASIC in 1983 with a 1,500-word dictionary, pushing the limits of an 8-bit computer (a Commodore 64). Thirty-five years ago, he was already at CERN with Tim Berners-Lee who was creating HTML and testing and improving HTTP... But rest assured, he’s not the one working on Windows - it gives him an allergic reaction. 🤣 You can bet that he was behind the earlier caustic jokes about Windows. 🤔

Kind regards

 

[Riesengebirge 0]

2 hours ago, Staff said:

If we want to have a sad contest to see who’s the most decrepit, we have a good competitor. The founder of AirVPN built his first natural language parser in Assembly and BASIC in 1983 with a 1,500-word dictionary, pushing the limits of an 8-bit computer (a Commodore 64). Thirty-five years ago, he was already at CERN with Tim Berners-Lee who was creating HTML and testing and improving HTTP... But rest assured, he’s not the one working on Windows - it gives him an allergic reaction. 🤣 You can bet that the previous caustic humor on Windows came from him. 🤔

Oh, well... I guess we share the same levels of decrepitude then.  Started at 13 on a Sinclair ZX-81, but of course the Commodore 64 was THE best computer of all time. At one point, I knew by heart how many CPU cycles each 6510 instruction used and what opcode each Assembly mnemonic translated to. That being said, my advice would be to ignore current MicroSlop's development guidelines - and Linux's, for that matter - and keep all program data in its own installation directory. Edited ... by Riesengebirge