Settings in TIDE

C-q s opens the settings tab: every setting wdx has, its value and, under the list, what the one under the cursor does. It is wdx setting list and wdx setting set in one screen. The CLI side, and where settings live, is in Settings.

What you see

wdx tide · shop-apiOpen larger

Settings with a fixed set of values show ← →; the description of the one under the cursor is at the bottom. Click, scroll and type: it is live, and runs nothing.

Keys

Key	What it does
↑ ↓	the setting under the cursor
← →	the next value of a setting with a fixed set of them, such as color, log.level, editor or tide.theme
Enter	edit any other value in place, then Enter to save it
C-q s	open the tab, or go to it
-	close the tab

How it behaves

• Applied at once. A change is saved in ~/.wdx/config.yaml and the daemon reads it again, as wdx setting set does. TIDE’s own settings, its colors (tide.theme) and the order of the project pane’s sections (tide.section_order), apply on screen at once.
• Every setting but home can be changed here; home comes from WDX_HOME. A value the setting cannot take is refused, the reason under its row.
• When it takes effect is the setting’s: color once TIDE is reopened, terminal.shell and terminal.history_lines for new terminals.
• The same file. A change made with wdx setting set or in the file shows when the tab is next shown.
• Turning off an AI CLI with aca.<id>.enabled takes it out of the new agent form; agents already running it go on.
• Not on another node since 0.5.0. A TIDE opened with --node has no settings tab: its menu says settings are changed on that node itself, as a session reaches none of them, the hub.* settings among them.