Zen Focus Mode: PoC fork linked

[JasonBates]

Problem

I often want to concentrate on one window for a while without rearranging a useful tiled workspace. A temporary centred view would let me work in that window and return to the same tiles with one action. (I implemented a working solution on a fork that I use day to day below)

Desired behavior

Add an optional focus-mode command that users can bind to a shortcut of their choice. Invoking it for the focused window would:

• Centre that window at a comfortable width and dim the other windows with a dark, click-through backdrop. The focused window remains fully interactive.
• Keep the underlying tiling tree and tile sizes intact. Invoking the command again restores the original tiled layout; for a floating window, it restores the original frame.
• Exit when the user clicks outside the focused window, switches workspaces, or enters AeroSpace full screen. Clicking inside the focused window keeps Focus Mode active.
• Let the existing keyboard focus commands select another window in the same workspace while Focus Mode is active.

On one display, the window stays on that display. My prototype places it on the middle display in a three-display setup, or the macOS main display when there are two. The width and display choice could be configurable upstream. In my setup, Caps Lock is my AeroSpace modifier key, and I bind Caps Lock + Z to toggle Focus Mode. That is a personal binding, not a proposed default.

Animation

This schematic animation shows each of three differently placed tiles entering and leaving Focus Mode.

Working prototype

I have been using this on my Mac Studio. The working branch merges recent upstream main changes with the Focus Mode implementation. The built and tested source commit passed 397 Swift tests. My build reuses the lone-window width rules from discussion #2308, with a 66% fallback; Focus Mode itself need not depend on those rules.

Q: Would a temporary centred presentation that preserves the tiled layout fit AeroSpace? What width and multi-display behavior would make sense upstream?