dsh-open-terminal

Working inside dsh-TUI often means compiling, debugging, or running scripts in a system terminal, yet the TUI owns the full screen and context-switching breaks your flow. dsh-open-terminal solves this with a single /term command that spawns a new system terminal window in the current or any specified directory, leaving the TUI completely undisturbed.

/term works the way you expect it to: no argument opens the current working directory; a precise path (relative, absolute, or ~-expanded) launches immediately; a fuzzy fragment triggers a case-insensitive, CJK-aware, Unicode-normalised folder search across the workspace, with multi-match results presented in the host's native TUI picker—arrow keys to navigate, Enter to open. The cross-platform terminal chain covers Windows (Windows Terminal, PowerShell, cmd), macOS (Terminal.app), Linux (GNOME Console, kitty, Alacritty, and a dozen more, falling back in order), and WSL (Linux chain first, then a Windows-side Terminal fallback). Every launch flag follows the terminal's own documentation, guaranteeing a true new window rather than attaching to the TUI's console.

Everything runs on the UI command plane: no model message is produced, no tokens are billed, nothing enters the KV cache—it is a pure fire-and-forget hand-off. A configuration key lets you override the built-in chain with a custom template (for example, a specific Git Bash profile or terminal of choice), and all messages follow the host's language setting automatically. It is built for developers who live in dsh-TUI and need to hop into a terminal frequently, especially those juggling Windows, macOS, Linux, and WSL environments day to day.