Poe Lurker: a trade manager that floats over Path of Exile

A companion app rather than a modification of the game

Poe Lurker is described as a simple trade manager meant to ease the trading experience in Path of Exile, and the repository topics place it in the world of lurkers and overlays, alongside trade managers. The shape of the tool is that of a separate desktop application that draws on top of the running game, so the player keeps one window for the game and another for the parts of trading that would otherwise require leaving the game.

The technical choice behind that overlay is worth naming, because it explains both what the tool can do and where it breaks. The project credits Winook for the thread level hook, and a hook of that kind works by injecting into the game process and intercepting its threads so the overlay can follow the game's state. That is what lets an external window stay in sync with what is happening on screen, and it is also why the tool is tied to a specific game client and a specific Windows build.

The user interface itself is not hand rolled. The project credits MahApps.Metro for the modern UI, which is a WPF control library, so the application is a .NET desktop app rather than a native C++ overlay. That choice is what makes the MIT licensed source readable and forkable for anyone who wants to change the interface.

The install path is a Windows setup executable

There is no package manager entry and no source build described in the repository documentation. The usage section lists two requirements: install .NET 8 or later, and download and run the setup executable `PoeLurkerSetup.exe`, which the repository links from the latest release download path.

So a first run is: have the .NET 8 runtime present on the machine, download `PoeLurkerSetup.exe` from the project's releases, run it, and start the application alongside Path of Exile. The repository also links a Cheat Sheet document in the `assets` folder and a User Guide hosted as a slide deck, which together cover what the tool does once it is running.

What the documentation does not cover is worth knowing up front. There is no description of supported Windows versions, no list of game versions the overlay is known to work with, and no statement about what happens when the game updates underneath a running instance. The animation referenced in the repository, `assets/Incoming.gif`, shows the overlay reacting to an incoming request, which hints at the interaction model but does not document the compatibility matrix.

Some features sit behind a Patreon tier

The funding model is stated plainly in the repository introduction. If you use Poe Lurker, the project asks you to consider signing up for a small monthly Patreon donation, and says that even $2 helps. In return, donors become Lurker Pro users and enable what the project calls extra features in the application.

This is the part of the project that deserves a clear answer before adoption. The MIT licence covers the source code, so anyone can read it, fork it, and build their own copy with every feature present. What the licence does not do is give you access to the developer's private builds, support, or any hosted service that might sit behind the Patreon tier, because the documentation does not describe such a service.

The project also links a Discord server and a PayPal donation route alongside Patreon. The practical distinction for a reader is simpler: the base application is free and open source, and a paid tier exists as a way to fund the work and to enable extra features in the official build.

The repository layout tells you how it is built

The top level of the repository is a .NET solution in practice. There is `Lurker.sln` as the solution file, a `src` directory for the code, a `test` directory, a `global.json` that pins the SDK version used by the build, and an `appveyor.yml` file for continuous integration. Code style is enforced through `PoeLurker.ruleset` and a `stylecop.json`, and an `.editorconfig` handles formatting. A `WoshVsPowerTools-Settings.json` file points at Visual Studio tooling conventions, and the `.gitlurker` file is the Git LFS pointer file.

That last detail matters for anyone planning to fork the project. Large binaries such as `LurkerIcon.png`, `ItemStash.gif`, `SystemTray.png` and `TrayIcon.ico` are tracked through Git LFS, so a clone without an LFS client will not produce a working build.

The presence of a `test` directory and a ruleset for style analysis is a decent signal for a project of this size, since it means the build is expected to be checked, but the repository does not publish a coverage report or a test count, so there is no way to judge the depth of the suite from the outside.

Code signing, release history and the current state

Windows binaries that are not signed trigger SmartScreen warnings, so the project links SignPath.io for free code signing. That arrangement explains why the official download is a signed setup executable rather than a raw build, and it is worth noting that a fork built by someone else will not carry that signature.

The release history is short and readable. Version 2.2.0 was tagged on 2025-10-25, V2.2.1 on 2025-10-31, and v2.2.2 on 2025-11-15, so three releases landed inside three weeks in late 2025 and then nothing further was tagged. The last push was on 2026-05-18, which means work has continued on the default branch `main` without a new version tag since November 2025.

That gap is the single most important maintenance fact here. The repository is not archived, so it is not dead, but a game companion app that is several months past its last tagged build is a different proposition from one with a release every few weeks. For a tool whose value depends on keeping pace with the game client, that is worth checking before you make it part of your trading routine, and it is why the project points at a Discord server where the maintainer and users are likely to discuss current compatibility.

The licence is MIT, with the licence file at the repository root, so forking and redistribution are both straightforward for a desktop utility.

Editorial conclusion

Poe Lurker suits a Windows player or a trading group that wants stash and trade management in a separate overlay and is willing to install a signed setup executable alongside a .NET 8 runtime. It does not suit Linux or macOS users, and it is a poor fit for anyone who needs every feature without a subscription, since Lurker Pro features are unlocked through Patreon. Before installing, check that the latest release still matches your game client, read the Cheat Sheet in the `assets` folder for what the free tier covers, and confirm the .NET 8 dependency on your machine before you download `PoeLurkerSetup.exe`.

Frequently asked questions

Official sources

1. C1rdec/Poe-Lurker on GitHub
2. Issues
3. License: MIT
4. README
5. Releases