Groupy 2 Feature Request – Automatic Grouping for Specific PWAs

from Stardock Forums

Currently, Groupy can auto-group apps based on their executable (e.g., all windows running under chrome.exe). This works for traditional programs, but it’s too broad for Progressive Web Apps (PWAs), which all run under the same executable.

Feature request: Add the ability to automatically group windows belonging to specific PWAs together.
Example use case: I’d like all Claude PWA windows to automatically group together, without also grouping unrelated Chrome browser windows.

 

This would make Groupy much more PWA-friendly and let users keep workflows tidy when working with multiple web apps installed as standalone PWAs.

groupy
9,543 views 2 replies
Reply #1 from Stardock Forums Top

Hello,
I have forwarded your request to the Stardock Support Team for their review and recommendations. We really do appreciate your feedback, Thanks

Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

Hi, I just wanted to chime in on this. This sort of works in Groupy2 (I am using version 2.3) but you have to manually edit the resulting .groupy config file to make it work.

If you take several PWAs and group them, and then save the group it puts in invalid values for CommandLine, WorkingDirectory and Target.

If you go and manually put in values that look like this (your username, browser and --app-id will be different of course), then it will launch the PWAs properly.

CommandLine=--profile-directory=Default --app-id=khfmdegfjbimhnepdonglmgmglmgkcdb

WorkingDirectory=C:\Users\pnmye\AppData\Local\BraveSoftware\Brave-Browser\Application\

Target=C:\Users\pnmye\AppData\Local\BraveSoftware\Brave-Browser\Application\chrome_proxy.exe

But because of what the original poster said (all of the apps are identified as brave.exe or chrome.exe), Groupy2 will pick random other Chrome or Brave windows from the desktop and put them into the group, instead of some of the PWAs it just launched. 

So I think there are two things that need to be fixed...

One is that the UI doesn't capture the right data to put in the config file (if you just take what the UI puts in there, it simply gives an error when you try to launch and fails to launch any of the PWAs entirely). 

And secondly, Groupy2 needs to be able to differentiate properly between Brave/Chrome windows by using some other data. Looking for something like the Window Title would probably work just fine. 

Is there not a way in the config file to indicate how to properly match a Window aside from solely looking at the OwnerProcess?

Here's an example of one of my PWAs that is partially working (as described above). If anyone has any advice on what other config values we might be able to inject in here to get this working, that would be a step in the right direction.

[GroupyEntry2]

OwnerProcess=C:\Users\pnmye\AppData\Local\BraveSoftware\Brave-Browser\Application\brave.exe

APPID=Brave._crx_khfmdegfjbdonglmgmglmgkcdb

NewTabName=

RunElevated=0

NoPatternMatching=0

CommandLine=--profile-directory=Default --app-id=khfmdegfjbimhnepdonglmgmglmgkcdb

WorkingDirectory=C:\Users\pnmye\AppData\Local\BraveSoftware\Brave-Browser\Application\

Target=C:\Users\pnmye\AppData\Local\BraveSoftware\Brave-Browser\Application\chrome_proxy.exe

SoundPackager - Customize the Windows sound scheme