Settings

Read when wdx starts; an invalid one fails every command. The home is read from the environment, the rest from <home>/config.yaml, where log.level is written as “log: {level: debug}”. wdx setting list shows them, and wdx setting set changes one and has the daemon apply it at once; after editing the file by hand, run wdx daemon restart. wdx setting write lists every setting in the file, as wdx update does with a new release’s.

--no-input and --color override no_input and color for one command. NO_COLOR set to anything, or TERM=dumb, turns color off where it is auto.

Setting	Default	Description
home (WDX_HOME)	/home/you/.wdx	directory holding the config file, database, logs and cloned projects
no_input	false	never prompt, as --no-input does: true or false
color	auto	color text output: auto (only on a terminal, unless NO_COLOR is set), always or never
log.level	info	lowest level logged: debug, info, warn, error
log.retention_days	7	days of log files kept besides today’s
otel.endpoint	http://localhost:4318	OpenTelemetry collector the daemon sends its metrics to over OTLP/HTTP, such as the one wdx observe starts; empty sends none
otel.interval_seconds	15	seconds between two sends of the metrics
update.channel	stable	releases wdx update installs: stable, or dev for the newest release of either kind
update.base_url	https://github.com/srjn45/wdx/releases/download	where wdx update downloads releases, laid out as GitHub Releases; file://<repo>/dist for local builds
terminal.shell		absolute path of the shell terminals run; empty runs the user’s login shell, /bin/sh when the system names none
terminal.history_lines	100000	lines of each terminal’s history kept on disk, which wdx terminal attach scrolls back through; 0 keeps none, since terminal output can hold secrets
terminal.history_tail	1000	lines of a terminal’s history wdx terminal history prints when not told how many; at most 10000
editor	vi	terminal editor TIDE edits a file with: vi, vim, nvim, nano, hx, emacs
tide.section_order	awdpc	the sections TIDE’s left pane shows, in their order, a letter each: a agents, w worktrees, d docs, p plans, c code; those left out are hidden
tide.theme	slate	the theme of colors TIDE paints its panes in: slate, for a dark terminal, is the only one so far; with color off TIDE paints none
context.threshold.warning	200000	tokens in an agent’s context from which TIDE and wdx agent show its size as a warning, in yellow, and below which in green; a whole number below context.threshold.critical
context.threshold.critical	400000	tokens in an agent’s context from which TIDE and wdx agent show its size as critical, in red; a whole number above context.threshold.warning
docs.git_path		directory of each project’s repository, relative to its main checkout, that the daemon keeps the project’s docs written into, read-only, on every change, as wdx doc sync-to-git does once; empty for none
plan.parallel	3	the most tasks each plan runs at once, each an agent in a worktree of its own, unless wdx plan run --parallel says otherwise; from 1 to 20
hub.remote_access	false	whether your other nodes on the hub may open sessions into this one, each with a code from this node’s authenticator (wdx hub code setup): true or false; false closes every session into it at once
hub.session_idle_timeout	1h	how long a session into this node lasts unused before it is closed, a duration such as 30m or 2h, of at least 1m
aca.claude_code.enabled	true	whether new agents may run claude_code, when it is installed: true or false
aca.antigravity.enabled	true	whether new agents may run antigravity, when it is installed: true or false
aca.cursor.enabled	true	whether new agents may run cursor, when it is installed: true or false
aca.codex.enabled	true	whether new agents may run codex, when it is installed: true or false

wdx setting list shows each setting’s value and where it came from; wdx setting set --name <key> --value <value> changes one in ~/.wdx/config.yaml. See wdx setting.