AI Agent Hub
Back to plugins
🧠

dsh-palimpsest

Memory Updated 2026.09.14

Run the following command in DeepSeek Harness:

dsh plugin install cnkids/dsh-palimpsest

Paste the following prompt into your AI chat to install this plugin:

Install by running dsh plugin install cnkids/dsh-palimpsest; the plugin is open-sourced at https://github.com/cnkids/dsh-palimpsest . After installation, restart dsh web and start a new session to activate it.

About this plugin

When the context window runs out and you have to open a new conversation, the agent usually asks you to re-explain the background from scratch. dsh-palimpsest lets the agent recall on its own: list past sessions in the same working directory, search by keyword, and read a specific conversation—all without you pasting anything in. The plugin does exactly one thing: read the ink underneath the current conversation. It builds no index, writes no SQLite, and never modifies existing sessions; delete the log files and the memory is gone, with no second plaintext copy anywhere. On the security side, recalled content is always returned as tool-result data, never injected into the system prompt. Known credential patterns are masked at the output boundary, sessions tagged with private markers are fully excluded from listing and search, and every retrieval is prefixed with a statement that the content is historical data, not instructions. Search defaults to literal matching, so consecutive Chinese terms work without a tokenizer; enabling DSH's built-in FTS index is optional and not required. This plugin suits developers who work across many DSH sessions over time, care about strict data boundaries, and prefer not to maintain a separate SQLite index. The trade-off is that each search decompresses and scans session logs, making it naturally slower than pre-built index approaches in exchange for a simpler, fully controllable footprint.

Use Cases

  • Context window exhausted in a new session, agent recalls prior conversations to continue work
  • Returning to a project days or weeks later, keyword-search old discussion context
  • Privacy-sensitive workflows where no second plaintext index file is acceptable

Best For

  • Developers who work across many DSH sessions over time
  • Teams sensitive to data boundaries who want no extra plaintext copies
  • Users who prefer lightweight zero-dependency plugins with no maintenance burden