Big8: Add an AI Metaphysics Assistant to DSH (Feng Shui · Physiognomy · Bazi · Divination)
## Introduction The philosophy of DSH (DeepSeek Harness) is "everything is a plugin"; the framework itself is only responsible for scheduling, and specific capabilities are filled by skill packages. Most skills in the community are concentrated in engineering scenarios like coding and information retrieval. If you want the agent to smoothly handle some life-oriented requests—such as a user uploading a floor plan to ask about feng shui, or providing a birthday to calculate the Eight Characters—it is far more convenient to install a ready-made skill according to the Agent Skills standard than to write calendar conversion and prompts from scratch. Below is an introduction to Big8, maintained by kobenfang. ## What is this? Big8 is a skill package that adheres to the Agent Skills open standard (SKILL.md + YAML frontmatter), maintained by kobenfan.
Read Moredsh-simple-cli: Add a Claude Code-like terminal chat to DeepSeek Harness
# Foreword Developers who work in the command line for a long time often have this requirement: input a sentence directly in the terminal to see the model's response in a streaming format, the tool execution process in real-time, and manually confirm sensitive operations—instead of switching to a browser or assembling outputs from headless calls. DeepSeek Harness (hereinafter referred to as dsh) supports specifying a profile at startup (e.g., `dsh --profile cli`). The dsh-simple-cli introduced below is a CLI profile that runs entirely within the terminal: once installed, use the `dsh-cli` command to converse with the Agent, resembling the interface of Claude Code. # What is dsh-simple-cli
Read Moredsh-cost-balance-pro: Session cost/balance statistics bar below the input box
dsh-cost-balance-pro is a DSH web plugin (Author: kingcharleslzy-ai, MIT License) that displays session costs and account balance in real-time via a statistics bar below the input box. Clicking it expands details such as cache hit rate and token counts. Regarding DeepSeek's peak-valley billing starting from August 17, 2026, the plugin automatically switches pricing based on the current time period.
Read Moredsh-tidewatch: DeepSeek Peak and Valley Tiers and Session Cost Floating Badge
# Introduction Since August 17, 2026, DeepSeek has implemented time-of-use pricing, with off-peak rates at half the price of peak rates. Running the same task during peak hours costs twice as much as during off-peak hours. The challenge lies in the fact that when writing code, you may not remember which tier you are currently in. Additionally, the web interface of DeepSeek Harness (hereinafter referred to as DSH) does not have a built-in feature to display the current tier and the session cost. DSH's philosophy is "everything is a plugin," so this gap in the presentation layer is perfectly suited for a plugin to fill. The dsh-tidewatch introduced below is such a badge: it floats next to the input box, displaying the peak/off-peak status, a countdown timer, and the session cost. # What is dsh-tidewatch? Maintained by KhalilYamber, MIT license.
Read Moredsh-usage-vendor-stats: DeepSeek Harness API usage statistics by vendor dimension
When running agents in DeepSeek Harness (hereinafter referred to as DSH), multiple vendors are often connected: the official API, huoshan, hebox, tokenrhythm, etc. While persistent session logs always carry token accounting and provider/model sources, there is no default view that directly answers questions such as "how much was used by each vendor during this period, what is the cache hit rate, and the approximate cost calculated at unit price." The existing `dsh-usage-stats` plugin aggregates usage by workspace but lacks a vendor dimension. The `dsh-usage-vendor-stats` introduced below fills this gap by performing usage statistics with the vendor as the primary dimension. dsh-usag...
Read Moredsh-side-chat: Open native parallel sessions alongside the main dialogue of DeepSeek Harness
# Introduction When running long tasks with DeepSeek Harness (hereinafter referred to as DSH), a common scenario arises: the main conversation is editing code or executing commands, and you suddenly want to ask an unrelated question or have another session look up a file. Opening a new session requires rebuilding the context from scratch, while inserting the question into the main conversation disrupts the flow of the current task. dsh-side-chat addresses this scenario by opening a side chat side-by-side with the main conversation; both sides function as complete DSH sessions without interrupting each other. Following DSH's philosophy that "everything is a plugin," it is loaded as a Web Plugin without modifying the DSH core. # What is this dsh-side-chat is a DSH plugin maintained by KarlOfLaw, licensed under the MIT License.
Read More@kelearns/dsh-token-usage: Add a token usage heatmap to the dsh web GUI
# Introduction When running agents with DSH, conversation logs are stored under `$DSH_HOME/sessions`, with token consumption scattered across individual sessions. To answer questions like "How many tokens were used daily this month?" or "Which model was used the most?", you must manually decompress zstd-compressed JSONL files and calculate line by line. While writing a script to do this isn't difficult, you have to re-run it every time you want to view the data. @kelearns/dsh-token-usage brings this functionality into the GUI: a GitHub-style contribution graph displaying daily, weekly, and cumulative token usage. DSH follows the philosophy that "everything is a plugin." This plugin is mounted via the official plugin mechanism and does not require modifying the DSH source code. Below, we introduce its features, installation method, and data interface.
Read Moredsh-session-archive: Retrieve archived sessions from DeepSeek Harness
# Introduction The core philosophy of DeepSeek Harness (DSH) is "everything is a plugin," delegating capabilities not covered by the host to plugins. There is a significant gap in the Web profile: once a session is archived, it disappears from all interfaces, including workspace grouping and search, and DSH itself does not provide an entry point to view or restore these sessions. Consequently, archiving becomes a one-way operation; accidentally archived sessions cannot be recovered, and there is no way to verify the content of a specific archived session. The `dsh-session-archive` introduced below fills this gap: it adds an entry in the sidebar to list globally archived sessions from the registry, supporting preview, recovery (unarchiving), and deletion.
Read Moredsh-session-nav: Add Codex-style session navigation to DeepSeek Harness Web
# Introduction When running long sessions with DeepSeek Harness (hereinafter referred to as DSH), it is often necessary to return to a previous turn. With a large number of turns, it is easy to get lost while scrolling up and down in the Chat tab, and switching to the Trajectory tab requires finding the position again. Moreover, older turns may not have been loaded into the Chat view, making them inaccessible by scrolling. DSH's philosophy is "everything is a plugin," and such interface layer supplements are ideally suited for community plugins to handle. Below, I introduce karmiy/dsh-session-nav, a DSH Web plugin that provides Codex-style navigation on the left side of the conversation. # What is it? dsh-session-nav is maintained by karmiy, licensed under the MIT License, and is positioned as "DeepSeek Ha..."
Read Moredsh-balance: Display account balance next to the DSH input box model seat
# Introduction When using DSH for daily conversations, after switching models or service providers, it is often desired to know how much remaining balance is in the account. The current approach involves opening a separate browser, logging in to the corresponding service provider's console to check, which constitutes an interruption for every switch. dsh-balance brings this action into the input box: the balance is displayed as a short text snippet next to the model slot in the composer, and becomes visible after selecting the model. DSH's philosophy is "everything is a plugin," and this requirement is perfectly handled by a plugin. Below is an introduction to its implementation, installation method, and precautions. # What is it? @kkbsgg/dsh-balance is a DeepSeek Harness (DSH) plugin maintained by kkbsgg, currently version 0.2.0, with an MIT license. It
Read Morekeel: A DSH plugin that makes agents define specs before writing code
When using harnesses like dsh (DeepSeek Harness)—which adopts a "everything is a plugin" approach—to run coding tasks, the common problem is not that the model cannot write code, but that it starts writing immediately upon receiving requirements. When requirements are vague, the implementation direction can drift, leading to the highest rework costs; treating "I assume" as fact builds solutions on quicksand, and doing too much work during the implementation phase allows the scope to creep further away. While writing specifications into system prompts is a common approach, constraints often remain at the "self-discipline" level and lack a hard gatekeeping mechanism. The philosophy of Keel is to prioritize writing specifications and validating assumptions, with implementation not beginning until the specifications pass the gate. During implementation, rules are used to prevent over-engineering, and change requests are used to prevent scope creep. Before delivery, acceptance criteria are audited item by item. Discipline is achieved by constraining agent behavior through skills and performing deterministic checks via tools, rather than relying on...
Read More@kidli1412/dsh-session-cost: View session costs and balance in real-time on the DSH Web stats panel
# Introduction When running sessions with the DSH (DeepSeek Harness) Web client, the built-in statistics row below the input box only displays the number of turns, duration, and token count. It is only by checking the official platform that you know exactly how much this round cost; you won't usually keep an eye on your remaining balance, often only noticing when a request fails due to insufficient funds. `@kidli1412/dsh-session-cost` solves these two problems by incorporating the estimated token cost for the current session (priced in CNY per model entry) and the DeepSeek API balance into the built-in statistics row. Below is an introduction to its implementation, installation, and configuration. # What is it?
Read Moredsh-usage-record: Add a question navigation rail to the DSH Web chat area
# Introduction When using DSH Web for long conversations, a common annoyance is the difficulty of revisiting a previous query. Because the chat area uses virtualized rendering, scrolling past a section means earlier content isn't loaded yet, so scrolling back requires waiting. The left sidebar session list is cluttered with "new sessions," making it hard to distinguish between them based solely on titles. dsh-usage-record addresses these two issues: it adds a vertical navigation rail to the left of the chat area, where each line corresponds to a prompt, and clicking jumps directly to it. It also automatically generates session titles based on prompt content. The following sections introduce its features, installation, and precautions. # What is it? dsh-usage-record is a DSH client plugin (web platform only) maintained by kkishapppy.
Read Moreclaude2dsh: Migrate Claude Code sessions, skills, and memory to DSH native sessions
`claude2dsh` is an MIT-licensed DSH plugin (version 0.2.0-rc.5 candidate) maintained by kirkchinese. It is used to migrate Claude Code's sessions, skills, global instructions, and project memories into DSH-native continuous sessions, and can also export DSH sessions back to Claude Code JSONL. Core commands include session import (returning counts for categories such as previewed, imported, and skipped), skill and global instruction migration, and converting project memories into DSH skill packs. All of these can be performed via a browser UI wizard started by `dsh web`. Installation requires Node.js >= 22.19.0, pnpm, and the dsh CLI. Regarding security design, the source Claude directory defaults to only...
Read Moredsh-auto-open-web: Open DSH Web GUI in a standalone application window
# Introduction After running `dsh web` in the terminal to launch the Web profile, DSH defaults to opening a standard tab in the system's default browser to host the GUI. This tab gets mixed in with your daily browsing, lacks an independent window identity in the taskbar, and makes switching between tasks or finding it inconvenient. DSH's philosophy is "everything is a plugin," and this issue can be solved by a plugin as well: dsh-auto-open-web is a resident plugin. Once the HTTP service is bound and the actual listening port is acquired, it automatically opens the GUI in an independent application window (or a browser `--app` window). It also provides a configuration card in Settings → Plugin Configuration. The following sections introduce its behavior, configuration, and installation methods. # What is dsh-auto-open-web
Read Moredsh-prism: Adds a "Simplified Mode" to the DSH Interface
# Preface The philosophy of DeepSeek Harness (hereinafter referred to as DSH) is "everything is a plugin." This design offers sufficient flexibility, but it also presents a usability threshold on the interface. During a single task, the model sequentially calls a chain of tools, causing the native interface to scroll through a long list of tool cards where terminology, parameters, and status are intermingled. New users attempting to get started struggle to discern "what exactly happened in this turn," while veteran users familiar with the system require complete information and do not wish for the interface to be oversimplified. The native interface offers only one mode of interpretation, leaving both groups to compromise on a single presentation. dsh-prism addresses this issue by adding two modes to DSH's Web UI: "Simplified" for those seeking efficiency, and "Native" to restore the original experience for experts. It features one-click switching and can be uninstalled without leaving a trace when no longer needed. The following sections introduce its features, installation, and usage.
Read Moredsh-opencode-go-usage: Real-time display of OpenCode Go subscription usage in the bottom-right corner of the DSH Web GUI
dsh-opencode-go-usage is a DSH Web plugin (v0.1.0, MIT License) maintained by kkishapppy. It permanently displays the percentage usage and reset countdown for the Scroll, Weekly, and Monthly tiers of the OpenCode Go subscription in the bottom-right corner of the DSH Web GUI. It automatically refreshes every 60 seconds and immediately refreshes when the window is brought back to the foreground. The plugin consists of two parts: a server-side component that proxies the usage interface and manages the API key (parsed via the DSH credential service, with configurable credential names and cache durations), and a browser-side component responsible for rendering the widget. The widget's style automatically adapts to light and dark themes based on DSH theme tokens. The API key exists only on the server side and is not exposed to the browser. Installation requires a single command and simple configuration, making it suitable for users utilizing the OpenCode Go subscription.
Read Moredsh-bundle-manager: DSH Third-Party Plugin Runtime Mount Manager
# Introduction The philosophy of DeepSeek Harness (DSH) is "everything is a plugin." However, following the official design, bundles written to `dsh.profile.bundles` are loaded upon process startup and remain resident. To temporarily disable a third-party plugin, one must modify the profile manifest and restart the process. Simultaneously, DSH has a key architectural requirement: optional third-party plugins can only be placed in `dependencies` and must not be written into `dsh.profile.bundles`. In other words, the official static layer does not provide a location for enabling or disabling these plugins at runtime. `dsh-bundle-manager` fills this gap: it mounts within the process via the Loader API.
Read Moredsh-settings-ui: DeepSeek Harness Plugin Unified Settings Page UI Suite
# Introduction DSH's philosophy is "everything is a plugin," meaning that as the number of plugins grows, the number of settings interfaces will inevitably increase as well. Writing settings interfaces for plugins is a repetitive task: components must be built from scratch, styles need tuning, and a complete suite of state logic—handling load/save/busy/error/saved indicators and revision conflicts—must be managed. Since every plugin develops its own independently, the styles often fail to align with the official settings pages, resulting in a fragmented user experience when switching between different plugins. `dsh-settings-ui` addresses this issue by extracting the settings page UI and state logic into a reusable service. Plugins can utilize ready-made components, declarative forms, and a settings state machine via `ctx.settingsUi`, eliminating the need to hand-code the UI. Below is an introduction...
Read Moredsh-llm-kiro: DeepSeek Harness LLM Provider Plugin for Reusing Existing Kiro Credentials
`dsh-llm-kiro` is a Kiro LLM provider plugin for DSH (DeepSeek Harness) maintained by joshryandavis (MIT,
Read Moredsh-token-heatmap: Daily token usage heatmap for the DSH Web interface
# Introduction DSH's philosophy is "everything is a plugin," and Web interface capabilities can be supplemented by plugins on demand. However, for daily users of `dsh web`, token usage data is scattered across event logs in various sessions. There is no ready-made entry point to answer questions like "how much was used today" or "how much has been accumulated this month." Below is an introduction to `@kidli1412/dsh-token-heatmap`, a DSH Web GUI plugin: it renders a GitHub-style daily token usage heatmap below the input box on the new session screen, displaying today's, monthly, and cumulative statistics in a single row. It is ready to use out of the box. # What is it? One-sentence positioning: Displays the current calendar year (optional year) below the input box on the new session screen.
Read Moredsh-launch: Delegating long-running services to independent broker processes for supervision
# Introduction In DSH conversations, a common problem encountered when the model starts a dev server is that once a conversation round ends or the session closes, the service is terminated. The root cause is that PowerShell background jobs are bound to the scope of the owning session. When the session or round ends, `dsh-jobs-local` cancels the assigned tasks, so the service simply fails to survive to the next round. `dsh-launch` is designed to address this issue: it delegates the service supervision to a dedicated detached broker process, ensuring the service continues running even after the conversation round ends, the session closes, or even if DSH itself restarts. Below, we introduce its mechanism, features, and usage. # What is it? `dsh-launch` is Khellendro.
Read Moredsh-complete-notify: Add task completion sounds and notifications to DSH.
# Introduction When running tasks with DSH (DeepSeek Harness), a common workflow involves handing off the task to an agent and switching to other tasks. The difficulty lies in not knowing when the task will conclude: it may have finished early waiting for your feedback, or be blocked midway requiring approval. Constantly staring at the page wastes attention. `dsh-complete-notify` addresses this issue: it plays a sound and displays a notification when the task completes. It utilizes a toast notification when the page is in the foreground and switches to a system notification when in the background. The following sections introduce its positioning, features, installation, and configuration. # What is this? `dsh-complete-notify` is a DSH plugin maintained by kaixinbaba, licensed under the MIT license. One-sentence positioning: it plays a sound and pops up a small notification when the task is complete.
Read Moredsh-sidebar-panel: Adding a persistent right-side panel to DSH Web
# Introduction In the DSH (DeepSeek Harness) web interface, there are several types of information that are not easily visible during normal use: context window usage, session costs, files in the workspace, and modified files in the session. Although the details column on the right carries some of this content, it is automatically collapsed when switching or creating new sessions, requiring manual reopening each time. The dsh-sidebar-panel approach is to add a panel collapse button in the top-right corner of the session header, place the Overview, Files, Changes, and Tools tabs into the right details column, and make the panel persistent—switching or creating new sessions does not automatically collapse it, and the collapsed state is also remembered. # What is it dsh-sidebar-panel is DSH We...
Read More