workspace dispatcher does back and forth when set up this way, but it would really benefit the system, especially with automatic laptop handling scripts, if we could force a workspace instead of flipping out of it when its already on screen. 
Intended behaviour:
forceworkspace 1 simply ensures workspace 1 is visible, even if it still is.
Yes. Thats why I request this feature.
I would like to have a simple way to “switch to workspace 1” on startup with a tool I currently invent to allow for “scenario roaming” with Hyprland.
The tool I’m currently implementing is about “enabling quasi-clamshell” mode on laptops (you can leave the laptop open and still have its screen and keyboard backlight off) but will be about true “scenario roaming” with auto-detect / multiple modes and all that later.
why not just disable this option?
Yes, I did that for a while, but found out that I like it actually.
My use case for this option is, for example, to have (at work) my browser with TeamCity on workspace 10 and then a lot of Rider and vscode instances on the other workspaces.
But yes, if this would be disruptive to implement or ultra low priority - I can totally live with as it is for now, of course.
hyprctl --batch 'keyword binds:workspace_back_and_forth 0; dispatch workspace 1; keyword binds:workspace_back_and_forth 1' should work
Yes, it does. Stupid of me not to think about, thank you very much, thats of course a great solution even!
