API/Command to Query Current Split Orientation

[zwo-bot]

Background

Coming from i3, one of the features I miss in AeroSpace is the visual indication of the next split direction. In i3, the window border highlights (right border for horizontal split, bottom border for vertical split) provide immediate visual feedback about where the next window will be placed.

Current Limitation

AeroSpace currently provides split commands (split horizontal, split vertical, split opposite) but there's no way to:

• Query the current split orientation of a container
• Determine what the next split direction will be
• Build visual indicators or status bar widgets showing the split state

Proposed Solution

Add a command or API endpoint to query the current split orientation, for example:

Option 1: Dedicated query command

aerospace query split-orientation
# Output: horizontal | vertical

Option 2: Include in tree query (Issue #16)
When the tree query command is implemented, include split orientation as part of the container/node information:

aerospace list-windows --json
# Include "split_orientation" field in output

Option 3: Extend existing commands

aerospace list-windows --format "%{split-orientation}"

Use Cases

1. Status Bar Integration: Update menu bar tools (SketchyBar, Übersicht, etc.) to display the current split mode

   alt-h = ['split horizontal', 'exec-and-forget update-statusbar-split-indicator horizontal']

2. Visual Notifications: Show macOS notifications or overlays indicating split direction

3. Smart Scripts: Build automation scripts that adjust behavior based on current split orientation

4. i3-like Border Indicators: Enable third-party tools to provide visual border highlights showing split direction

Related Issues

• Support tree CLI command to return the whole tree #16 - Tree query command (would naturally include this information)
• Feature Request: Option to alternate layouts when opening windows #228 - Alternating layouts (requires knowing current orientation)
• Feature: on-focus-changed callback #230 - on-focus-changed callback (already implemented ✅)

With #230 implemented and this feature, it would be possible to create reactive visual indicators that update automatically when focus or split orientation changes.

Proposed Implementation

Since this likely depends on or relates to Issue #16 (tree query command), this could be:

• A subset/simpler version of the tree query focused on split orientation only
• Included as part of the tree query implementation
• A separate lightweight query specifically for this purpose

Alternative Workarounds Considered

Currently, the only workaround is to manually track split state by adding notifications to each keybinding:

alt-h = ['split horizontal', 'exec-and-forget osascript -e "display notification \"Horizontal\" with title \"Split Mode\""']

This approach:

• ❌ Doesn't work with split opposite (can't determine what "opposite" means without knowing current state)
• ❌ Loses track if windows are rearranged
• ❌ Doesn't persist across AeroSpace restarts
• ❌ Only knows split commands explicitly triggered by keybindings

Summary

An API to query split orientation would enable users (especially those coming from i3) to build visual feedback systems and create a more intuitive tiling experience. This feature would complement the existing split commands and align well with the planned tree query functionality.

[alewis001]

Does #1161 do what you need? The work has been done, it's just not in a release yet.

[zwo-bot]

@alewis001 Thanks. To my understanding no, as it only will show the layout for the existing windows. What i suggest is somethin that can determine what will be the orientation of the next window that will be created (i.e. after running split opposite). Correct me if i misunderstood.

[alewis001]

will show the layout for the existing windows.

That's correct.

What i suggest is somethin that can determine what will be the orientation of the next window that will be created (i.e. after running split opposite).

Ah ok. I think I'm demonstrating my lack of experience with i3 😄

[nikitabobko]

Created an issue #1772