Docs

Shell integration

NOBLE learns each pane’s working directory from OSC 7 / OSC 9;9, with no setup. That is what lets splits open in the current folder, sessions restore where you left off and git status refresh after every command.

Supported shells

ShellHow
PowerShell (Windows, Linux and macOS)Your existing prompt, oh-my-posh included, is wrapped to emit OSC 9;9 and the exit code (OSC 133;D); a typed command's start is marked with OSC 133;C.
cmd.exeA PROMPT that reports the folder, unless you already have one. cmd reports no exit code, so a pane title shows only how long a command took, and cmd gets no command blocks.
bash, zsh, fish (Git Bash too)Your own ~/.bashrc, .zshrc or config.fish loads first, then a small hook reports OSC 7 and the exit code (OSC 133;D) on every prompt, and marks a typed command's start (OSC 133;C; bash 4.4 and newer). Starship, oh-my-zsh and friends keep working.
Anything elseAny shell whose prompt emits OSC 7 works too.

The hook scripts live in the data folder under shell/. To start a shell untouched, pass --norc (bash), -f (zsh) or --no-config (fish) in shell_args.

Which shell starts

With shell = "" NOBLE starts pwsh, then powershell, then cmd on Windows, and $SHELL elsewhere. The Settings shell list offers the ones it finds: pwsh, powershell, cmd and Git Bash on Windows; bash, zsh, fish, pwsh and nu on Linux and macOS.

On macOS bash, zsh, fish and PowerShell start as login shells, as in Terminal.app and iTerm2, so /etc/zprofile, ~/.zprofile and Homebrew's PATH load. Any shell_args of your own replace that. If a system zshenv sets ZDOTDIR outright, zsh cannot load NOBLE's hook, and NOBLE says so; write it as ZDOTDIR=${ZDOTDIR:-…} instead.

What a prompt tells NOBLE

Each prompt (OSC 7, OSC 9;9 or OSC 133) also means the previous command finished. NOBLE then:

Command blocks

The same marks split a pane into command blocks: each pane keeps the output range of its last 200 commands. PowerShell, bash 4.4+, zsh and fish send them. cmd.exe sends none, and bash 3.2 sends no start mark, so these actions find nothing there; WSL's bash.exe gets no integration at all.

Result badges and the live timer

The pane title shows how the last command typed at the prompt ended: ✓ 2.4s when it worked, ✗ 1 · 12s with its exit code when it failed, and · 12s in cmd.exe, which reports no exit code. The badge stays until the next command finishes. In a shell that sends command marks, a command that runs longer than 2 seconds replaces the badge with a live timer: ◷ 0:07, then ◷ 3m. The timer counts every second in its first minute and once a minute after that; on battery the first minute shows only ◷, so an idle pane redraws at most once a minute.

Progress and window title

Programs in a pane can report progress with OSC 9;4, as Claude Code does. The pane title shows the percentage (42%), a spinner while busy work has no percentage, ✗ on an error and ‖ while paused; the tab shows a busy marker. The report ends with state 0 or with the shell's next prompt.

While an agent waits for you, the terminal NOBLE runs in gets a paused progress report, and the window title reads NOBLE · ◆ 1, with the number of agents waiting. On Windows the progress report is sent only to Windows Terminal or to a terminal that sets TERM_PROGRAM; the title is sent everywhere. Both are cleared when nothing waits, and the title the terminal had before NOBLE is restored on exit.

Notifications: A background tab gets a marker: ◆ for an OSC 9 / OSC 777 notification, the bell or an agent that needs you; ✗ for a command that ended with an error; ✓ for a long command that finished; • for plain output. It clears when you open the tab. Clicking a pane's notification (a toast, or ⏎ in Show Notifications) goes to that pane; ctrl+y copies its text.