Settings

/settings opens the settings overlay. Tab and Shift+Tab switch between the General, Agent, and Status line sections; ↑/↓ move between rows and ←/→ change a value. The complete overlay keys are in Keyboard and keys.

General

Motion controls presentation only: provider output still enters the live session immediately, and a tool boundary or settled assistant message flushes the visible stream without waiting for the animation.

Agent

A non-Auto choice applies from the next turn; code, identifiers, commands, tool arguments, logs, quotations, and file contents keep their accurate forms, and an explicit language request for the current task still wins. The preference is user-level, so a resumed session uses the current value rather than a historical snapshot.

Features

Optional product features that cost context, runtime, or transcript noise. Each row turns one composition row off.

A change here applies on the next launch, and the row says so. disabled is a Loader option rather than plugin configuration, so the settings service cannot express it; these rows are written into a managed block in $OMDSH_HOME/profiles/omdsh/cordis.patch.yml instead, which is the surface the Harness reads while composing the tree. The block is delimited by comments and everything you wrote by hand around it is left alone.

Rows that back a command (session-query backs /sessions, workspace backs @ mentions) and rows that make the agent unusable (tool-fs, tool-bash, todo) are deliberately not listed. web_search is also absent: it shares its row with web_fetch, so no row-level switch can express “search off, fetch on”.

Status line

Status items are reordered and restyled in place: Space shows or hides an item, Enter starts moving one (↑/↓ reorder, ←/→ choose the column), and each item has its own color.

First line, in default order: Model (deepseek), Effort (max), Path (~/project), Git (main *1), and Session, which is off by default because the terminal window title carries the session title regardless.

Second line telemetry groups, all shown by default: Context (Ctx 1.6% · 16.4K/1M), Cache (Cache 99%), Tokens (5.9M in), Latency (TTFT 1.2s), Time (LLM 16m51s), and Activity (3 turns). When the terminal is narrow, groups degrade from the lowest priority: cache, then tokens, then latency, then durations, then activity counts.

Persistence

Settings, model preferences, and logged-in credentials are live plugin config persisted into the active Profile’s Cordis patch, $OMDSH_HOME/profiles/omdsh/cordis.patch.yml (with $DSH_HOME, then ~/.dsh, standing in for the home itself); /settings, /model, and /login all write there. A settings.yaml left by an earlier release is imported once at startup — each section written into the Profile row with the same id — and the file is then renamed to settings.yaml.imported, while a section that no longer matches a row id is logged and stays only in the renamed file. See Sessions and history for the complete file list.

Plugin settings

Beyond the overlay’s three sections, mounted Harness plugins keep their settings in that plugin’s own config on its Profile row. One decides whether the default route works at all: llm-deepseek is Messages-only and refuses a protocol key, answering protocol is not configurable; remove it and use a Messages-compatible baseURL. A custom gateway therefore has to expose a Messages-compatible endpoint, and the DeepSeek endpoint is selected by base URL rather than by a protocol switch.

Related

• Keyboard and keys — settings overlay keys and keybinding overrides
• Troubleshooting — color environments and update behavior
• Commands — /settings, /model, /login