Auto Window Manager: The Ultimate Guide to Automating Window Layouts

How to Configure Auto Window Manager for Multi-Monitor Workflows

Overview

Auto Window Manager automates window placement and sizing across multiple monitors so your apps open where you want, saving time and reducing distraction. Below is a step-by-step configuration guide and recommended rules for common multi-monitor setups.

1. Preparation

1. Confirm monitor arrangement: Physically note which monitor is primary and the relative positions (left/right/above).
2. Choose a trigger method: Decide whether you want rules applied on window open, display connect/disconnect, or manually via hotkeys.
3. List apps and roles: Assign each app a role (e.g., Editor, Browser, Terminal, Communication, Reference).

2. Basic Rules to Create

1. Primary workspace apps: Set your main editor and browser to open maximized on the primary monitor.
2. Reference/Document monitor: Place PDF readers, documentation, or chat apps on the secondary monitor in a fixed size (e.g., 40% width).
3. Terminal/Tools monitor: Reserve a third monitor (if present) for terminals, dev tools, and logs; tile these windows vertically.
4. Transient apps: Configure dialogs and small utility windows to open centered on the monitor where the mouse currently is.
5. Fullscreen exceptions: Exclude video players and games from automatic tiling rules.

3. Rule Settings (recommended values)

• Positioning: Use exact coordinates for repeatable layouts or percentages for flexible scaling (e.g., left 0%, top 0%, width 60%, height 100%).
• Window state: Set to Normal (not minimized) and choose Maximized for browsers/editors.
• Match criteria: Match by window class/process name rather than window title.
• Priority: Assign higher priority to explicit app rules; lower to generic rules like “all browsers.”

4. Multi-Monitor Specific Tips

• Per-monitor DPI scaling: Prefer percentage-based sizing to handle different DPI settings across monitors.
• Snap zones: If supported, create snap zones per monitor to quickly relocate windows with a hotkey.
• Dock and taskbar areas: Account for OS taskbars/docks by reducing height/width by their size.
• Profile switching: Create profiles for single-monitor laptop mode vs. multi-monitor docked mode and bind to display connect events.

5. Automating on Display Changes

• Enable the “apply rules on display change” option so windows reflow automatically when you dock/undock.
• Add a small delay (200–500 ms) before rules apply to allow the OS to report new display geometry.

6. Troubleshooting

• Rule not applying: Verify the match uses the app’s executable/class name and increase rule priority.
• Windows partially off-screen: Check DPI scaling and use percentage-based sizes.
• Flicker on rule apply: Add a short delay or disable animations in the manager if available.
• Conflicting rules: Audit rules by priority and remove redundant generic matches.

7. Example Rule Set (concrete)

• Editor (process: code.exe) → Primary monitor, left 0%, top 0%, width 60%, height 100%, priority 100.
• Browser (process: chrome.exe) → Primary monitor, right 40%, maximized, priority 90.
• Slack (process: slack.exe) → Secondary monitor, left 0%, top 0%, width 30%, height 100%, priority 80.
• Terminal (process: terminal.exe) → Third monitor, full height, width 40%, tile left, priority 85.
• PDF Viewer (process: sumatrapdf.exe) → Secondary monitor, centered, width 60%, height 80%, priority 70.

8. Maintenance

• Review active rules quarterly to match workflow changes.
• Export/import rule sets to back up configurations or replicate across machines.

If you want, I can generate a ready-to-import rule file for a specific Auto Window Manager app—tell me the app name, OS, monitor resolutions, and example apps/process names.