TUI settings
Customize input layout, mouse interaction, keybindings, status placement, and terminal activity reports.
Open /settings and choose tui settings to control the main input chrome, mouse interaction, and where status information appears. Changes apply immediately and are saved in $ZOT_HOME/config.json.
Config keys
{
"tui_click_to_position": true,
"tui_input_style": "block",
"tui_status_position": "below_input",
"tui_working_position": "above_input"
}Mouse cursor and text selection
Enable **click to position cursor** under /settings > **tui settings**. A stationary left click in the main input moves the cursor, including wrapped lines and Unicode text. Click-drag selects visible chat or input text without moving the editor cursor. The selection stays highlighted after release and is not copied automatically.
Display updates pause until the selection is dismissed so streaming cannot move selected text. The agent continues working, and the view catches up when the selection clears. Mouse interaction is ignored while a dialog owns input. Without a selection, ctrl+c and esc retain their usual behavior.
ctrl+shift+c and cmd+c can also copy if your terminal forwards the chord to zot. Terminal-native copy shortcuts that the emulator consumes cannot copy zot's highlighted selection. Use ctrl+c for explicit copying in zot.
Clipboard copy uses pbcopy on macOS, PowerShell on Windows, or wl-copy, xclip, or xsel on Linux. Over SSH, or when local copying fails, zot sends an OSC 52 clipboard request instead. Your terminal or multiplexer must allow it, and zot cannot verify that the request succeeded.
Program status
In interactive mode, zot reports activity through the Program Status Protocol (OSC 7501). Supporting terminals and dashboards can show whether it is working, waiting for input, finished, or failed. This is separate from the visible status bar and is controlled by an environment variable, not a /settings toggle.
By default, zot queries the terminal for support and sends reports only after an acknowledgement. Automatic detection is skipped for non-TTY input/output and detected tmux or screen sessions. You can override detection for a single run:
ZOT_PROGRAM_STATUS=1 zot # force reporting without detection
ZOT_PROGRAM_STATUS=0 zot # disable queries and reportsForcing reports does not make a multiplexer forward them. Closing zot clears its reported status. Reporting is limited to the interactive client and work submitted there, not background agents or work submitted by other attached clients. Print, JSON, RPC, and bot modes do not emit these terminal sequences.
Messages use only explicit session names, dialog titles, and the first error line. Transcript text, tool previews, dialog bodies, and model output are not used as status messages. Prompt-derived session-picker titles are excluded. Names update after renaming through /sessions, and switching sessions clears the previous outcome. Legacy branch names are omitted because older rename records may contain generated prompt excerpts. Rename such a branch again to report an explicit name.
Message control characters become spaces. Text is limited to 2048 UTF-8 bytes without splitting characters, then base64-encoded for the wire format. Reports also identify the application as zot.
Custom shortcuts
Bind key chords to slash commands or navigation actions with keymap in $ZOT_HOME/config.json. There is no /settings row for this yet. Edit the file and restart zot. Each key is a case-insensitive chord made of at least one modifier (ctrl, alt or option, shift, cmd or super) plus a single character or a named key (enter, tab, space, esc, backspace, delete, up, down, left, right, home, end, pageup, pagedown). A string value invokes a slash command. Built-in commands, extension commands, and /skill:<name> all work. An object value configures a navigation action.
{
"keymap": {
"alt+n": "/new",
"ctrl+s": "/settings",
"ctrl+g": "/git-tools:status",
"alt+r": "/skill:code-review",
"ctrl+n": { "action": "next", "context": "navigation" },
"ctrl+p": { "action": "previous", "context": "navigation" }
}
}Slash-command shortcuts run in the main interactive input and use the same dispatch path as typing the command. They do not apply while a dialog, extension panel, or tool confirmation has focus. The example alt+n binding starts a fresh persisted session, but /new is unavailable when zot runs with --no-session.
Navigation objects support "next" and "previous" with the required context "navigation". They act like Down and Up in built-in lists and scrollable views, including model, session, settings, and confirmation dialogs, and in slash, file, and path suggestion popups. Navigation remains available while editing a list's filter. In confirmations, these actions move the selection without answering the request.
Text-only subviews and the main editor without a popup ignore navigation actions. They do not edit text, browse prompt history, or scroll the main chat. Extension panels control their own navigation and do not use these actions. There are no default ctrl+n or ctrl+p aliases. Add the entries above to enable them, or choose other modified chords. Existing arrow keys continue to work.
Unbindable chords, invalid command strings, unsupported actions or contexts, and the reserved ctrl+c, ctrl+d, and esc chords are skipped and reported above the transcript at startup (the notice clears with /clear). Unmodified keys such as enter or g cannot be rebound. Malformed binding values, wrong field types, or unknown object fields cause a config parse error. /help lists the active bindings under custom keys.