dsh-context README

The project's README from github.com/bowenliang123/dsh-context. As one markdown file: README.md.

Social preview

dsh-context

npm version GitHub stars dshfind

The best DeepSeek Harness plugin for Agent's context insights and management.

dsh-context provides full context lifecycle management features.

Install / Update

Install dsh-context plugin from DeepSeek Harness:

dsh plugin --profile web add dsh-context

Or update the dsh-context plugin:

dsh plugin --profile web update dsh-context@latest

Then start the web UI with dsh web. No build step, no restart.

Use it

Three surfaces, one story — what your agent is carrying, how it got there, and what it did with it:

Where What you get
Context tab The full dashboard: stats, composition, per-request trend, events, file activity, and the agent network — in every session.
/context command A centered modal with the same composition and context browser, without leaving the chat.
Settings → Plugin configuration Per-user defaults: trend granularity & mode, File Activity sort.

📊 The Context tab

Open any session and click the Context / 上下文 tab:

Context panel overview

Card The question it answers
Context Stats Turns, steps, live tool calls & images, context-event tallies — plus a list-price cost estimate (hover the ? for per-1M rates).
Token Stats Where the billed tokens went: cache read/write, uncached input, output — around the cache-hit ring.
Timing Stats How active time split across model calls, tool runs, and overhead.
Current Context What's in the window right now.
Context Trend Every request's size — and its story.
Context Browser What any request was actually assembled from.
Context Events When and why the window changed.
File Activity What the agent did to your files.
Agent Network The whole agent family, live.

The headline occupancy and composition read the same official token-meter projections as the chat composer's context ring (contextPressure / contextBreakdown), so the figures always match what the ring tells you.

🧱 Current Context — who ate the budget

Current Context card

A six-color stacked bar against the model's full window (hatching = free headroom): system prompt, tool schemas, user messages, injected context, assistant replies, tool results — each with its ≈token figure and share. When a conversation starts degrading, this is where you see which part is responsible.

📈 Context Trend — every request, sized and explained

Context Trend with the step brief

One stacked bar per model request — finer than per-message — so you watch the window grow turn by turn:

Context Trend in Delta mode

🧭 Context Browser — open the box of any request

Pick Live (next request) or any retained step, and browse what that request was assembled from: six collapsible categories expand into one row per element with its token price, and every element expands again into its actual content — the system prompt, each tool's JSON schema, message text, reasoning, tool arguments, and tool outputs.

Tool schemas with source chips, filter, and sort

A tool result expanded with Raw/Markdown toggle

An image payload rendered as a thumbnail card

⚡ Context Events — when and why the window changed

Context Events with a compaction

Every injection, compaction, prune, model switch, and plan-mode toggle — labeled with its producer (instruction file, plugin id, skill name), its net token delta (compactions show what they reclaimed), turn/step, and time. The Inject / Compact / Prune / Switch / Mode chips filter the log by kind.

📁 File Activity — what the agent did to your files

File Activity

One row per touched file — read, written, or searched — aggregated up to whichever step you pick on the trend chart:

🕸 Agent Network — the family portrait

Agent Network with two subagents

The current agent, its parents, and every subagent — one node per agent, colored edges for the lineage, multi-level delegation on one map. Each ring is that session's composition scaled to its window occupancy; hover for tokens, requests, billing, and active time; click to jump into that session's own Context tab. Running agents breathe with a green pulse.

⌨️ /context command

Type /context (or pick it from the / menu) and press Enter:

Slash menu with the context command

A centered dialog opens with the Current Composition card and the Context browser — the same composition bar, per-step picker, and vs previous turn diff badges as the tab:

The /context modal

⚙️ Settings

In Settings → Plugins → Plugin configuration, the Context card holds this plugin's per-user preferences — default trend granularity (Step/Turn), default trend mode (Total/Delta), and the File Activity default sort. In-chart and in-card toggles stay per-view and never overwrite the stored preference.

The Context settings card

Good to know

Like it?

If dsh-context helped you understand what your agent is carrying around, a ⭐ on GitHub is much appreciated — and issues/PRs are welcome!

License

Apache-2.0

dsh-context (bowenliang123/dsh-context)

i18n
Searching Database…

What is this?dsh-context is a plugin for DeepSeek Harness (dsh) that gives full visibility into an AI agent's context window — a dashboard tab, a sidebar panel, and a /context slash command showing token stats, context composition, trends, compaction/prune events, file activity, and the agent family tree.
Is this a standalone app, or does it plug into something else?It's a plugin that extends DeepSeek Harness's own web UI — adding a Context tab, a right-sidebar panel, and a /context slash command — rather than a separate application.
Do I need DeepSeek Harness already set up?Yes — this is purely a plugin for DeepSeek Harness, and it requires @deepseek-ai/dsh version 0.1.2-rc1 or later.
Are the token figures shown exact numbers?Most category breakdowns use dsh's own fixed-density token-estimation heuristic (the same one as its built-in token meter), while provider-reported actual prompt/output/cache numbers are shown alongside pinned trend details for comparison.
What does the Context Trend chart show?One stacked bar per model request showing how the context window grew or shrank turn by turn, with compaction and prune events pinned exactly where they happened, plus a plain-language step brief explaining what entered and left.
What is the Agent Network view for?It maps the current agent together with its parents and every subagent as a family tree, with live rings showing each session's token usage, requests, billing, and active time so multi-agent delegation is visible at a glance.
Can I use the UI in Chinese?Yes, dsh-context ships with both English and Simplified Chinese (简体中文) translations.
Why would I need this instead of the built-in context ring?The built-in composer ring only shows overall occupancy, while dsh-context breaks that same data down per request, per tool call, and per file, and adds history (trend, events, diffs) so you can see exactly what caused a context change.
Size
14.9 MB
Stars
2.2K
Age
2mo
Commits · 90 Days