dsh-btw: DSH Session Management and Configuration Plugin
DeepSeek Harness plugin `dsh-btw` is designed to optimize session management and configuration experience for the DSH client. Key features include: supporting references to historical content in conversations; forking temporary sessions from selected messages with automatic archiving; logically splitting context via a “New Context” action, retaining records but not sending them to the model; and visually displaying advanced Provider configuration options. Installation requires Git commands and a service restart, and is supported on DSH version 0.1.5-rc.2 or later.
Read Moredsh-btw: Agent Supplementary Notes Queue
`dsh-btw` is a non-intrusive plugin for DeepSeek Harness that queues supplementary notes via the `/btw` command, ensuring they are processed only after the agent completes its current turn. Its core capabilities include a non-blocking queue, FIFO mechanism, language independence, and stateless design. After installation, the web app must be restarted for the plugin to take effect. Note that this plugin has been superseded by official built-in functionality and is typically needed only when explicit command usage or non-Web configuration files are required.
Read Moredsh-btw: Global /btw Command Plugin for DeepSeek Harness
`dsh-btw` is a global command plugin for DeepSeek Harness that implements a temporary Q&A feature similar to `/btw` in Claude Code. It does not pollute the session history; answers are rendered only and not written into the message stream. It supports reusing the current model routing, automatically includes the most recent 40 messages as read-only context, and offers zero runtime dependencies and cancellability. Be aware of pnpm version compatibility issues during installation.
Read MoreBTW Side Question Panel
`dsh-btw` is a DeepSeek Harness Web client plugin designed to address the issue where temporary follow-up questions in a conversation pollute the main session context. It provides an isolated temporary Q&A environment through an independent branch session and a floating sidebar. Users can invoke the panel with a keyboard shortcut, ask questions using completed answers as reference context, and switch models independently without affecting the progress or state of the main conversation. The plugin runs entirely on the client side and requires a service restart to take effect.
Read Moredsh-btw: A command for safely asking context questions outside the main conversation
The `dsh-btw` plugin is designed for DeepSeek Harness to address context pollution and token waste caused by inserting “side questions” during main task execution. It provides a `/btw` command that launches a one-shot subagent to inherit the main session context and render answers directly, fully isolated from the main conversation flow, thereby preserving prefix caching and saving tokens. The article details installation via NPM or GitHub, along with configuration options and considerations for `fork`/`spawn` providers.
Read Moredsh-btw — Add Native Claude Code /btw Side Questions + /remember Session Notes to DeepSeek Harness
The DeepSeek Harness plugin `dsh-btw` is designed to help developers quickly ask side questions and take notes within the main conversation. It includes two core slash commands: `/btw` for background side questions that do not interrupt the main flow and are not persisted to disk, and `/remember` for session memos with persistent storage support. The plugin is a zero-dependency bundle, installable via link, and supports configuration validation and data cleanup.
Read Moredsh-btw: Use /btw to bypass questions in dsh web without interrupting the main task
# Introduction When running long tasks with agents, you likely encounter this scenario: halfway through a task, you suddenly want to ask, "What was the name of that config file?" If you send the question directly to the main input box, it enters the main conversation, causing the currently running task to pause and process this interruption—a small question that could be answered in a few seconds disrupts the entire main thread. Claude Code solved this problem with the `/btw` command: questions are routed via a side channel, while the main thread continues running. `dsh-btw` brings this capability to the web interface of DeepSeek Harness (dsh). The philosophy behind dsh is "everything is a plugin," and `/btw` is a community-driven supplement to this. Below is an introduction to its positioning, features, installation, and usage. # What is dsh-btw?
Read MoreDSH-BTW: DSH Bypass Q&A Plugin
`dsh-btw` is a side-channel Q&A plugin for DSH, designed to address the need for ad-hoc questions during the main task without disturbing the main model's context. Through the `/btw` command and a centered pop-up panel, it provides an independent session branch for read-only Q&A. Core features include: incremental synchronization of the main conversation history for multi-turn dialogue, clearing branches, and independent maintenance per session; branches respond in read-only mode, with the tool allowlist restricted to read, glob, grep, read_image, and web_search, rejecting operations such as file writing and command execution; branches do not enter the main LLM context and are not displayed as sub-agents. Installation requires the dsh CLI and pnpm to be installed locally, followed by executing specific commands to add the plugin and restarting the `dsh web` process. The applicable scenario is for DSH Web users to retain read-only retrieval capabilities while avoiding pollution of the main context.
Read Moreiyllyt/dsh-btw: Adding a /btw Bypass Question Plugin for DSH
dsh-btw is an unofficial community plugin for DeepSeek Harness (DSH) designed to address the "in-between" issue where users need to confirm current context details while the main Agent is busy. It allows users to submit one-off quick questions via the `/btw` command during parallel execution of main tasks, with responses displayed in a temporary panel and not recorded in the main session history. The plugin reuses the model configuration and context of the parent session but does not execute tools or engage in multi-turn follow-up questions, making it unsuitable for tasks requiring tool permissions, such as reading new files, executing commands, or performing online searches. Its core advantages include session isolation, privacy protection, and a cache protection mechanism. Users can choose from three archiving modes: private-jsonl (default, local private storage), memory, or none, and can abort requests by closing the panel. The plugin adopts a modular design for easy integration and extension.
Read More