Bring your Process Lasso setup
One click imports your prolasso.ini, including command-line patterns. Anything Corewright cannot express yet is listed, never silently dropped. Re-importing replaces only the previous import and keeps your own rules.
Every process on the right core.
Corewright is a process manager for Windows with a real rule engine. Priority, cores, I/O, GPU, memory and efficiency mode are decided by rules you can read, and put back the moment no rule wants them.
Beta 0.1 Free and open source. Get the beta or build it from source.
- Game
- Build tool
- Background
- Held back
- Kept free
Rules that own a setting, and give it back
Tools like Process Lasso set fixed values per process. Corewright decides with rules: conditions on anything you see in the process list, such as name, path, command line, parent, CPU or memory use, the foreground window, or facts pushed by other apps.
Each setting of each process belongs to the highest-priority rule that sets it, so different rules can own different settings of the same program. The first time Corewright changes a setting it remembers the original value. When no rule claims that setting any more, the original goes back. Pausing, editing rules or stopping the service reverts everything.
Sustain and release times keep rules from flapping, and the Explain view shows for every process which rule set what and which rules were overruled.
game.exe, explained
| Setting | Owned by | Now | Original |
|---|---|---|---|
| CPU priority | Your rule Games high | High | Normal |
| Cores | Autopilot game mode | CCD 0 | All |
| I/O priority | Your rule Games high | High | Normal |
| Efficiency mode | No rule | Windows decides |
When the game exits or a rule stops matching, the original column is written back.
Eight settings, one engine
- CPU priority
- Idle to high; realtime only when a rule explicitly allows it. A program that keeps changing it back is left alone after three tries.
- Cores
- All cores, P-cores or E-cores, a list like
0-7,16, or CPU-aware tokens such asvcache-ccdandbest-cores:4. - I/O priority
- Very low to high, so a backup or indexer cannot stall your disk.
- GPU priority
- The scheduling class Windows uses for the GPU. The effect depends on the driver and hardware-accelerated GPU scheduling.
- Memory priority
- Which pages Windows trims first when memory gets tight.
- Efficiency mode
- EcoQoS on or off; turning it back over hands control to Windows again.
- Hard memory cap
- A job-object commit limit. Allocations above it fail, and child processes get the same cap.
- Soft RAM cap
- A working-set limit: Windows pages out instead of failing allocations.
Critical system processes such as csrss, lsass and dwm are never touched. A process is identified by its ID and creation time, so a reused process ID can never hit the wrong program.
Autopilot knows your CPU
Corewright reads your processor once at start: the CCDs from their L3 cache groups, 3D V-Cache from the cache size, physical cores and SMT threads, P- and E-cores, and the strongest cores from the CPPC ranking, the same ★ and • Ryzen Master shows. Autopilot uses that picture to place work. It never writes to a process itself; it generates low-priority rules, so your own rules always win. It is off until you turn it on.
Game mode
Finds games in your game libraries (Steam, Epic, GOG, Xbox and others), by full screen with Direct3D or Vulkan loaded, or from your own list. The game gets priority and its CCD: the V-Cache CCD on single V-Cache parts, otherwise the fastest one. Busy background work moves off it.
Sticky placement
Background work is placed once on the cheapest CCD and stays there so its caches stay warm. It only moves when a game claims the CCD or its cores stay saturated while another CCD idles.
Balancing
Like ProBalance, but built on the rule engine: background programs that stay above a CPU threshold get lower priority until they calm down. The window you use and Windows services are never touched.
Build tools
Compilers, linkers and shader compilers carry heavy load but are not latency critical. They run below normal with low I/O priority on free cores, without efficiency mode, so builds stay fast.
Task Manager depth, rules in plain language
A local API for your other apps
A plain HTTP API on 127.0.0.1 with a bearer token that changes at every start. Read processes and system data, edit rules, or push facts that rules react to:
curl -X PUT http://127.0.0.1:47830/api/v1/facts/obs.recording \
-H "Authorization: Bearer <token>" \
-H "Content-Type: application/json" -d '{"value":"true"}'Small enough to forget
| Service, idle | 0.01 % CPU | 17 MB |
|---|---|---|
| Tray icon | no timers | 5 MB |
| Window | only while open, then it exits | |
Expensive data such as GPU counters and per-thread load is only collected while the window is open.
Looks like it came with Windows 11
Light and dark theme, your accent colour, Segoe UI Variable and Fluent icons, a title bar drawn into the app, and a tray icon with a modern menu. Settings save as you change them, the way Windows Settings does.
Get Corewright
Corewright is in beta. Rules, monitoring, Autopilot, the window and the installer work today; networking (blocking, upload limits, priority) comes with the next beta. The installer sets up the Windows service and the tray icon, and Corewright updates itself from GitHub.
Latest version
Corewright , released . Windows 10 and 11, x64.
There is no stable release yet. The beta is the newest build and installs the same way.
Want new features first? Try the beta. Every download comes with a SHA-256 checksum, and Corewright checks it before it installs an update.
Build from source
Needs the .NET 10 SDK, Node.js and the Visual Studio C++ build tools.
git clone https://github.com/rennerdo30/corewright
cd corewright
build.bat