You no longer have to wait for a completion alert before returning to a dsh-TUI task. Released on November 12, v0.20.0 adds system notifications when the agent needs tool approval, an answer or a plan review. Before enabling them, consider who else can see your screen: the alerts can contain text supplied by the model or its host.
Choose when the terminal should interrupt you
The project's release notes put all four built-in notification categories behind the same switch. In the Conversation section of settings, taskNotifications defaults to unfocused. Choose always for alerts even while focused, or off to silence these built-in notices. When an external DSH notification plugin is enabled and active, completion, approval and question alerts defer to it, while plan reviews do not. Turning this switch off does not establish that the external plugin's alerts are off too.
This is not an alarm system for every running job. Approval requests and questions from background sessions and subagents remain in their panels without sending system alerts. Our reading: the update can reduce the time an attached session sits waiting for you, but it does not replace checking the panels when several tasks are running.
Approval alerts carry the session name, tool name and reason. Questions and plan reviews include the first question's header and text, not the entire plan. Formatting is cleaned up and length is limited, but the project explicitly makes no redaction promise. Before screen sharing or a public demonstration, switch off these built-in notifications if their contents could be sensitive, and check external notification plugins separately.
Returning to the right pane is a separate option
The jumpBack option is in the same settings section and is off by default. It requires the native Windows notification channel, and real-machine testing covers only Windows Terminal 1.24. Higher versions and other terminals fall back to ordinary notifications. The feature locates a target before sending an alert and checks it again when clicked. If it cannot verify the destination, it does not jump.
Layouts that cannot be verified also receive ordinary notifications. Do not assume every alert is a shortcut back to the task that raised it.
Check the engine before updating the interface
The previous release already introduced coordinated updates for the interface, engine and global launcher. In this release, running /update inside the app aligns DSH with 0.2.2-rc.2. The release notes require Node 24.9 or later for that engine, so check node -v before proceeding.
If you already installed that engine and the v0.19.0 interface will not start, the documented recovery command is npm install -g @deepseek-ai/dsh @deepseek-harness-tui/dsh-tui@0.20.0. It does not pin the engine version: at publication, the notes placed npm's latest tag on 0.2.2-rc.1 and rc.2 on next. Do not assume this command selects the same engine as the in-app updater.
There is another check for installations sharing a session store. The new engine writes a v3 subagent catalog that older DSH versions cannot open. Updating the terminal in front of you is not enough: check the other processes that read the same sessions before allowing the new version to write shared data.