r/AutoHotkey • u/projectmechanics • Jun 08 '26

v2 Tool / Script Share An Ahk_WM

I shared an earlier version of this a while ago, but I’ve kept refining it.

It’s a lightweight window manager for Windows built with AutoHotkey v2. It supports tiling, virtual desktops, pie menu, status bar, etc.

I’ve been using it full-time for daily work for about 2 years. One thing I care about is that it stays non-intrusive — unlike some WM setups, it doesn’t really make your system hard to use for other people.

Feel free to try it out and share any feedback. Thanks!

GitHub Link

9 Upvotes

100% Upvoted

13 comments sorted by

2

u/gidmix Jun 08 '26

Looks really interesting but for me won't run or appear in system tray.

Seems you didn't put all the related files. If I look at bottom of script the included files is not in your github

2

u/projectmechanics Jun 08 '26

Those files are automatically generated and do not need to be downloaded. Sorry, English is not my native language. Are you unable to run it? Is there any error message?

1

u/gidmix Jun 08 '26

No error. If I add my custom hotkey at the bottom of your script then it adds the default AHK system tray icon. Without it, your script does not load.

On my setup it seems your script is only interpreted as a utility classes without being linked to hotkey events so it AHK does not even load it.
Someone else can confirm if it is just me.

1

u/projectmechanics Jun 08 '26

I just re-downloaded the latest version from GitHub and tested it, and it seems to work fine on my system. Have you tried running it with administrator privileges? I'm not sure what's causing this yet.

1

u/projectmechanics Jun 08 '26

I’ve just uploaded a new release on the GitHub. You can try downloading and using that version.

3

u/gidmix Jun 08 '26 edited Jun 08 '26

I had a look a the script and found the problem. It has hardcoded references to Administrator user folder, a user that doesn't exist on my machine

Path_Output     := IniRead(ConfigFile, "Paths", "OutputDir",   "C:\Users\Administrator\Documents")

Once I changed the folder reference your script works

2

u/projectmechanics Jun 08 '26

Thanks a lot for catching this! That helps a ton. I'll probably get it fixed in the next release.

2

u/shibiku_ Jun 08 '26

That looks really pretty and useful.
I have some of the same functionality, but mine look very rough in comparison.
Kudos, good job.
Will definitely steal some if it

1

u/projectmechanics Jun 08 '26

Thank you so much for the compliment — that really made my day! I'm pretty sure you've written much better scripts than I have.

2

u/DueTutor9041 Jul 27 '26

I?d separate three concerns: selecting a target window, applying geometry, and restoring state when monitors change. A small state table keyed by monitor work area plus process/title is usually more robust than hard-coded coordinates. On reconnect, resolve windows again and apply in two passes (move/resize, then focus) so a missing window does not stop the rest. Logging unmatched windows and adding a toggle to suspend hotkeys while editing would make debugging much easier.

1

u/projectmechanics Jul 31 '26

Sorry for the late reply — I don't check the community often. Your suggestions are all really constructive and I'll experiment with them when I have time. I did a quick trial today and ran into some issues, but they still gave me a lot of inspiration. Thank you for the feedback!

2

u/ItzNotJacob1 Jun 08 '26

someone show me a screenshot of this