Configuration reference

Look up setting names, accepted values, and defaults. For your first file, use Quick start.

Source version: v0.5.7. Newer settings may not exist in older releases.

Keybindings are different

A custom config must contain [settings] and [keys]. Omitted settings use defaults, but [keys] replaces the bundled keymap. An empty table registers no keyboard shortcuts.

Find a setting

Category	What you can change
General	Animation, focus, pointer behavior, activation, dragging
Layouts	Mode, gaps, Traditional, BSP, Stack, Master-stack
Scrolling	Column widths, focus navigation, column gestures
Gestures	Trackpad workspace navigation
User interface	Menu bar, stack indicators, Mission Control
Virtual workspaces	Names, count, navigation, per-workspace layouts
App rules	Match windows and control placement
Keybindings	Keyboard shortcuts and command syntax
Modifiers	Reusable shortcut combinations
Startup commands	Launch helpers and event subscriptions

How to use this reference

1. Open the category that matches what you want to change.
2. Merge the example into the matching table in your config. Do not repeat an existing table header.
3. Change the value, save, and run rift-cli execute config reload if hot reload is disabled or the change does not appear.

Read defaults and types

• Default applies when the containing table exists but the field is omitted. Notes explain exceptions when a whole table is omitted. The bundled config may set a different value.
• Not set means an optional field is omitted. Its description explains any inherited value. TOML has no null.
• Required means you must supply the field when using its containing table.
• Boolean means true or false, without quotes. Text values need quotes; lists use square brackets.

The JSON Schema supports editor autocomplete and checks names, types, and some bounds. Use config reload to also check shortcuts, commands, and relationships between settings.