# Forceworkspace dispatcher would be great **URL:** \ **Category:** Bugs / FRs / Support\ **Tags:** hyprland, feature, window-management\ **Created:** [August 4, 2025, 6:39pm UTC](http://forum.hypr.land/t/forceworkspace-dispatcher-would-be-great/493 "2025-08-04T18:39:24Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![symphonic-navigator](http://forum.hypr.land/letter_avatar_proxy/v4/letter/s/db5fbb/32.png) [@symphonic-navigator](http://forum.hypr.land/u/symphonic-navigator)\ **Post date:** [August 4, 2025, 6:39pm UTC](http://forum.hypr.land/t/forceworkspace-dispatcher-would-be-great/493/1 "2025-08-04T18:39:24Z")
`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. ---
**Author:** ![vaxry](http://forum.hypr.land/user_avatar/forum.hypr.land/vaxry/32/3_2.png) [@vaxry](http://forum.hypr.land/u/vaxry)\ **Post date:** [August 5, 2025, 8:31am UTC](http://forum.hypr.land/t/forceworkspace-dispatcher-would-be-great/493/2 "2025-08-05T08:31:56Z")
You have this enabled ![20250805_10h31m43s](http://forum.hypr.land/uploads/default/original/1X/47c2b8d59b7d2db7a515022ff1a261ae086ea2fb.png) ---
**Author:** ![symphonic-navigator](http://forum.hypr.land/letter_avatar_proxy/v4/letter/s/db5fbb/32.png) [@symphonic-navigator](http://forum.hypr.land/u/symphonic-navigator)\ **Post date:** [August 5, 2025, 3:56pm UTC](http://forum.hypr.land/t/forceworkspace-dispatcher-would-be-great/493/3 "2025-08-05T15:56:41Z")
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. ---
**Author:** ![vaxry](http://forum.hypr.land/user_avatar/forum.hypr.land/vaxry/32/3_2.png) [@vaxry](http://forum.hypr.land/u/vaxry)\ **Post date:** [August 7, 2025, 5:49pm UTC](http://forum.hypr.land/t/forceworkspace-dispatcher-would-be-great/493/4 "2025-08-07T17:49:16Z")
why not just disable this option? ---
**Author:** ![symphonic-navigator](http://forum.hypr.land/letter_avatar_proxy/v4/letter/s/db5fbb/32.png) [@symphonic-navigator](http://forum.hypr.land/u/symphonic-navigator)\ **Post date:** [August 9, 2025, 5:30pm UTC](http://forum.hypr.land/t/forceworkspace-dispatcher-would-be-great/493/5 "2025-08-09T17:30:27Z")
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. ---
**Author:** ![vaxry](http://forum.hypr.land/user_avatar/forum.hypr.land/vaxry/32/3_2.png) [@vaxry](http://forum.hypr.land/u/vaxry)\ **Post date:** [August 12, 2025, 7:18pm UTC](http://forum.hypr.land/t/forceworkspace-dispatcher-would-be-great/493/6 "2025-08-12T19:18:45Z")
`hyprctl --batch 'keyword binds:workspace_back_and_forth 0; dispatch workspace 1; keyword binds:workspace_back_and_forth 1'` should work ---
**Author:** ![symphonic-navigator](http://forum.hypr.land/letter_avatar_proxy/v4/letter/s/db5fbb/32.png) [@symphonic-navigator](http://forum.hypr.land/u/symphonic-navigator)\ **Post date:** [August 13, 2025, 9:24am UTC](http://forum.hypr.land/t/forceworkspace-dispatcher-would-be-great/493/7 "2025-08-13T09:24:51Z")
Yes, it does. Stupid of me not to think about, thank you very much, thats of course a great solution even! 🙂