Terminal
Nethür's xterm.js terminal, tuned for AI-agent workflows: persistent sessions, panes, scrollback and agent state.
Nethür's terminal is the same xterm.js-based terminal VS Code uses, with a few additions tuned for AI-agent workflows.
Panes & tabs
Terminals are just tabs — see Tabs, panes & split layouts. Splitting a terminal pane gives you two shells side by side.
Agent terminal tabs show the agent identity plus live state: working, waiting for input, completed, or completed-but-unread. For Claude and Codex, tab titles can also show the AI Vault conversation name (custom title / thread name) when Nethür can map the pane to that session — manual renames still win.
TUI clipboard (OSC 52)
Many terminal UIs (Zellij, tmux, Neovim, fzf, Grok) copy via OSC 52 instead of OS clipboard APIs. Nethür allows those writes by default so copy-from-remote/TUI works over SSH the same way as locally.
Toggle: Settings → Terminal → Allow TUI Clipboard Writes (OSC 52).
Search
Cmd-F opens find-in-scrollback. Match highlighting, case, regex, and match navigation are all supported.
Link actions
A plain click on a terminal link (HTTP/OSC 8 URL, file path, workspace, terminal, or task handle) opens a compact action popover instead of navigating immediately. Local web links and links owned by a capability-verified paired runtime offer Nethür Browser and System Browser; SSH-owned links and older runtimes stay system-only. Web links also get Copy link, which copies the resolved URL (including hidden OSC 8 destinations) without closing the popover — file and workspace destinations stay unchanged. Cmd-click (macOS) / Ctrl-click (Windows / Linux) still opens directly, and Shift+Cmd / Shift+Ctrl-click still uses the link-routing alternate.
Previewable HTML file links can open in Nethür from local, SSH, and paired-runtime workspaces; remote file rows also offer Download & open with default app. If a linked file is already open in a sibling workspace tab, Nethür activates that tab instead of opening a duplicate. See HTML viewers.
Turn the popover off under Settings → Browser → Show terminal link actions. With it off, opening a link requires the modifier-click.
Copy terminal context
Right-click a terminal and choose Copy Context to copy a bounded transcript from that pane. Use it when you want to paste recent agent output into another tool without starting an Nethür fork.
Themes
Terminal color themes are configurable under Settings → Terminal. Nethür ships a library of popular themes and lets you customize any of them.
Ghostty import
If you use Ghostty, Nethür can import its theme, font, and cursor config on first launch. You can re-run the import later from Settings → Terminal → Import from Ghostty.
Warp theme import
If you've collected themes in Warp, click Import themes from Warp in the terminal-theme picker under Settings → Terminal to bring them in as Nethür terminal themes. Nethür scans Warp's theme directory for the current OS (~/.warp/themes on macOS, $XDG_DATA_HOME/warp-terminal/themes on Linux, %APPDATA%\warp\Warp\data\themes on Windows) and lets you pick which YAML themes to import. The button next to it, Import from YAML, takes the same picker and points it at any folder of Warp-format .yaml/.yml files — useful when you store themes outside the default location.
Imported themes appear alongside Nethür's built-ins in the theme dropdown.
macOS and Linux shell
By default, local terminal panes on macOS and Linux open your system shell ($SHELL) as a login shell (-l). With the default arguments:
-
zsh reads
.zshenv,.zprofile,.zshrc, and.zloginin order from$ZDOTDIR, or your home directory (~) if unset. Each user file follows its system counterpart (zshenv,zprofile,zshrc,zlogin), usually under/etcor/etc/zsh. -
bash reads
/etc/profile, then the first of~/.bash_profile,~/.bash_login, or~/.profilethat exists. It does not read~/.bashrcon its own. If yourPATHor version-manager setup (nvm, asdf, mise) lives in~/.bashrc, source it from that login file, as many distributions' default~/.profileor~/.bash_profilealready do:bash [ -n "${BASH_VERSION:-}" ] && [ -f "$HOME/.bashrc" ] && . "$HOME/.bashrc"The guard keeps non-bash shells that also read
~/.profilefrom loading bash-only setup, even withset -uenabled. Add it only if the login file bash reads does not already source~/.bashrc.
When Nethür uses its bash integration wrapper, it starts bash with --rcfile instead of -l. The wrapper sources the same login files without separately sourcing ~/.bashrc; bash itself is not in login mode.
To open a different shell, choose Custom shell under Settings → Terminal → Terminal shell. Under Advanced → Custom args, enter one argument per line to replace the default -l for ordinary local panes. An empty list requests no arguments: unwrapped interactive bash then reads ~/.bashrc instead of the login files. When the terminal daemon is unavailable, Nethür's bash or zsh integration can override custom arguments and retain login startup. Agent launches, startup commands, and one-off shell choices do not use this argument setting.
Windows shell
The default shell on Windows is configurable between PowerShell, Command Prompt, and WSL under Settings → Terminal. WSL is offered automatically when wsl.exe --status succeeds. The + dropdown on the tab bar also shows a submenu so you can open a one-off tab in any shell without changing your default.
For repos on a WSL filesystem (\\wsl.localhost\...), Nethür launches through wsl.exe -d <distro>. For Windows-path repos opened in WSL, Nethür translates the cwd to /mnt/<drive>/... and drops you into a login bash.
Windows administrator mode
Open Settings → Terminal → Administrator mode to see whether the Nethür app is running as Administrator or Standard user. Unable to determine means Nethür could not read its Windows elevation status. Existing terminals can have different permissions from the app.
In the installed Windows app, choose Restart as administrator, review the confirmation, then approve Windows’ prompt using your usual account. After approval, Nethür replaces its current local terminal host. This ends that host’s terminals and running agents; restored terminal tabs open new administrator shells. SSH and WSL permissions remain controlled on their hosts. Terminals on retained older hosts keep their original permissions.
If you cancel Windows’ prompt or elevation fails, Nethür reopens with its previous permissions and retains its terminal sessions.
For a manual launch, finish your local terminal work and exit Nethür. Find Nethür in the Windows Start menu, right-click it, and choose Run as administrator. If new terminals still have ordinary permissions, use Settings → Terminal → Manage Sessions → Restart daemon. This ends terminals on the current local host; newly opened local shells inherit the administrator app’s permissions. The setting’s manual instructions include a direct link to Manage Sessions.
To check a PowerShell terminal’s own permissions, run:
([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)True means that PowerShell process has administrator permissions.
Administrator mode applies to the whole app. When running nethur commands in an
external PowerShell window, run that window with the same administrator mode as
Nethür.
To return to ordinary permissions, finish and close all local terminal sessions, exit Nethür, and launch it normally. Closing the sessions lets the retained terminal host retire after Nethür disconnects; leaving sessions running can retain an administrator host even after the app exits. The Administrator status offers Standard mode guide with these steps.
Shortcuts
Cmd-T— new terminal tab in the current worktree.Cmd-Alt-T(macOS) — new agent tab using your default agent. On Linux and Windows this chord ships unbound; assign one under Settings → Shortcuts (search for "New agent tab"). Each supported agent also has its own per-agent "New agent tab" action — bind a chord to launch a specific CLI directly without going through the default.Cmd-W— close the current tab.Cmd-\— split right.Cmd-Shift-\— split down.
Native key bindings
Nethür advertises the kitty keyboard protocol, so terminal apps see real Shift+Enter, Ctrl+Enter, and other modifier-aware keystrokes — the bindings work the same in Nethür as they do in Ghostty, WezTerm, or your native terminal.
For Japanese JIS keyboards on macOS, enable Settings → Terminal → JIS Yen (¥) to Backslash (\) if you want the physical Yen key to send a backslash in terminal sessions.
Floating terminal
The floating terminal is a global shell surface that's always one chord away, regardless of which worktree or tab you're on. It's on by default for new installs.
- Toggle it with
Cmd+Option+A(macOS) /Ctrl+Alt+A(Linux/Windows). The same chord focuses the panel if it's already open and dismisses it if it's already focused. - Click the floating button on the edge of the window, or move the trigger to the status bar under Settings → Terminal → Floating terminal.
- Set the starting working directory under the same setting (
~by default) so new floating tabs land where you expect. - The floating panel hosts its own tabs and supports orchestration setup — kick off background runs without claiming a worktree pane.
Quick Commands
Quick Commands save terminal commands you run often, such as npm run dev, pnpm test, or a project-specific setup script. They can also save reusable agent prompts for launch-time prompt agents such as Claude and Codex. Create them from Settings → Quick Commands or the tab bar's Add command button, then run them from the Quick Commands split-button in a worktree tab bar or from the terminal context menu.
Each command has a label, command text, and scope. Use Global for commands that apply everywhere, or Project to show the command only in worktrees for a specific repo. The tab-bar button opens a fresh terminal tab and runs the command; the terminal context menu can insert commands into the current terminal. Use the copy control on a command row (Settings list, tab-bar menu, or mobile Quick Commands) to put the command body on the clipboard.
When you work with a paired Remote Nethür Server (or another execution host), the picker can show local and remote collections side by side, labeled by host (for example Local Mac and Nethür Server). Saved on is where the command is stored; running a command still executes in the terminal or workspace where you invoke it — so a client-owned command can run inside a remote worktree. Older servers that do not advertise multi-host Quick Commands fall back to the local-only list.