The philosophy of DeepSeek Harness is “everything is a plugin.” When developing or debugging agents, frequently using the /memory command line to view or manage memory entries is cumbersome and can introduce side effects (for example, browsing operations increase recall_count). dsh-memento-tab aims to solve these problems. It is a session-level memory tab for DeepSeek Harness, placed next to “Conversation / Trace / Context,” providing a comprehensive management interface covering /memory.

What Is It

This is a session-level memory tab for DeepSeek Harness, maintained by inxups. It is a companion plugin to dsh-memento, not a fork. It consumes only the upstream public ctx.memory and approval seams, registers its own routes and tab, and therefore upstream releases will not produce merge conflicts.

It covers the 11 verb operations of /memory and adds inline editing and export/download. It depends on the upstream ctx.memory and approval seams; if upstream is not installed, it remains inactive.

Core Features

  1. Four-tier budget card: Monitors usage across the four tiers: user / agent × user-global / workspace. Each tier has one progress bar; it turns yellow above 80% and red when full.
  2. Search and filtering: Substring search (220 ms debounce) works with track/layer filters and a “this session only” toggle.
  3. Inline edit and delete: Editing turns the entry into a text box in place; deletion uses the full entry text as a unique substring to locate the entry.
  4. Consolidate: Select at least two memory entries, pre-fill the original text and submit; the cap is read from the host’s maxMergeMatches.
  5. Pending proposals: Approve or reject. Approval re-runs the approval gate with the proposed text.
  6. Export and import:
    • Export: Supports the dsh-memento envelope format or adapter formats (such as mem0, hermes-memory-md).
    • Import: Supports preserving layer keys or rewriting layer keys according to the current session, with a maximum of 1,000 entries per operation.
  7. Audit and adapters: Displays the snapshot / recalled / write audit tail, as well as the list of adapters registered in the current build.
  8. Read path optimization: Uses store.listEntries() instead of ctx.memory.query(), does not increase recall_count, ensuring browsing traffic does not inflate recall counts.

Installation and Enablement

  1. Confirm dsh-memento is installed:
    dsh plugin --profile web add dsh-memento
  1. Install this plugin:
    dsh plugin --profile web add github:inxups/dsh-memento-tab
  1. Restart DeepSeek Harness. A fourth tab appears at the top of the session.

Typical Usage

  • Monitor usage: Check the four-tier budget card in the memory tab to confirm that usage is normal.
  • Manage entries: Use substring search to quickly locate entries, then select multiple memories to consolidate or edit inline.
  • Data migration: Click the data card to export memory to a file, or import memory files in other formats.
  • Approval flow: Click save to initiate a write approval request. In writePolicy: ask mode, writes initiated by the tab no longer trigger pop-up approval, but they are still recorded in the audit log.

Applicable Scenarios and Notes

  • Permission risk: This plugin runs with the current DSH process permissions. Writes are rejected under writePolicy: off or fine-grained policies. In writePolicy: ask mode, although pop-up approval is skipped, it relies on the x-memento-tab: 1 request header to block cross-site web requests; it cannot block local processes.
  • Route protection: Export, import, and write operation routes require the custom request header x-memento-tab: 1; otherwise they are blocked.
  • Dependency check: Routes use exact matching and do not conflict with upstream; however, they depend on the ctx.memory and approval seams and do not activate if upstream is not installed.
  • GitHub: https://github.com/inxups/dsh-memento-tab
  • Directory: https://www.skillhub.cn/plugins/inxups/dsh-memento-tab