DSH Marketplace

coding-agents

vectorize-io/hindsight#coding-agents

Hindsight, agent memory that learns: long-term project memory with auto recall and retain, knowledge pages, deep reflection, and per-repo memory banks.

40,9285,532PythonMITSource

Install

Add coding-agents to DeepSeek Harness

This plugin lives in a subdirectory of a larger repository, and `dsh plugin add` cannot reach it — it forwards to pnpm, which reads everything after `#` as a git branch or commit. Clone the repository and add the plugin through DSH's plugin panel using a repository source, or ask the author to publish it to npm.

Due diligence

Before you install coding-agents

  • Source of record: vectorize-io/hindsight — present in the community registry that DSH's own plugin market installs from.
  • Licensed under MIT.
  • Detected: terminal surface, requires credentials. Read the source before granting these.
  • A listing here is not a security review. Plugins run with your agent's permissions.

The AI take

What it is — Hindsight provides long-term project memory management for coding agents.

Who it is for — Developers using AI coding assistants such as Claude Code for code development should install it. If you use a non-Python language for the agent, you can choose other implementations.

Watch out — The plugin requires an API key or token and will execute shell commands. Sandbox testing has not been performed. No obvious pitfalls found.

The verdict — Without sandbox testing results, I would not install it.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.

What coding-agents does

Memory fragments flow into separate repository chambers and through a retrieval lens toward a central node.

coding-agents is a DeepSeek Harness plugin that adds Hindsight’s long-term memory system to coding agents, with recall, retention, knowledge pages, reflection, and separate memory banks for repositories.

Hindsight can sit behind an agent through an LLM wrapper, which automatically stores and retrieves memories as the agent makes LLM calls. For more control, its clients expose retain, recall, and reflect, with a bank_id selecting the memory bank. The README documents a local Docker service at ports 8888 (API) and 9999 (UI), Python and Node.js clients, and an embedded Python mode using HindsightServer. The documented provider configuration includes HINDSIGHT_API_LLM_PROVIDER; API access requires a provider credential such as OPENAI_API_KEY or HINDSIGHT_API_LLM_API_KEY.

This is intended for agents that need project context across interactions, user or task memories, and behaviour that can change from accumulated information. It is a poor fit for a small workflow that only needs simple retrieval, since the README describes Hindsight as potentially overkill for such applications. The terminal surface is used to run its Docker, Python, and npm tooling, and the service may send memory-processing requests to the configured LLM provider, so credentials and the agent’s terminal permissions should be treated as sensitive. coding-agents also introduces a separate memory service rather than using only the harness’s existing session state.

coding-agents documentation

How it behaves

Hindsight stores information with retain, searches stored memories with recall, and generates a disposition-aware response with reflect. Each operation takes a bank_id; the README uses my-bank. Memory banks can therefore be selected per repository or other scope by the calling agent. An LLM wrapper is also available: it replaces the existing LLM client and stores and retrieves memories automatically during LLM calls.

Configuration

The Docker quick start exposes the following settings:

Setting Meaning
OPENAI_API_KEY Shell variable used in the example as the provider credential
HINDSIGHT_API_LLM_API_KEY API container variable receiving the LLM API key
HINDSIGHT_API_LLM_PROVIDER Selects the LLM provider

The README lists these provider values for HINDSIGHT_API_LLM_PROVIDER: openai, anthropic, gemini, groq, ollama, lmstudio, minimax, and atlas.

Interfaces and storage

The Docker deployment serves the API at http://localhost:8888 and the UI at http://localhost:9999. The recommended container mounts the named volume hindsight-data at /home/hindsight/.pg0. An external PostgreSQL deployment is documented through docker/docker-compose; Oracle AI Database is also listed as supported for enterprise deployments.

Python clients use Hindsight from hindsight_client, while Node.js clients use HindsightClient from @vectorize-io/hindsight-client. The README also documents embedded Python operation through HindsightServer, which starts a local server for the client to use.

Platform note

The embedded package is hindsight-all. On Intel (x86_64) Macs, the README directs users to hindsight-all-slim instead. The examples use Python packages hindsight-client and hindsight-all, or the npm package @vectorize-io/hindsight-client.

Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub

Same category

Alternatives to coding-agents

39k

OpenViking memory and context bundle for DeepSeek Harness: pre-step auto-recall and profile injection, session capture, `viking://` URI guarding, and recall/write memory tools backed by an OpenViking server.

Installed cleanly when we ran it

npm packagePythonyesterday

AI review

dsh-memory-plugin

What it is — dsh-memory-plugin is an OpenViking memory and context bundle plugin.

Who it is for — When you use the DSH plugin system, people who need OpenViking memory and context bundle are suitable to install dsh-memory-plugin. For people who do not need OpenViking as context database, they can use other plugins.

Watch out — Sandbox test passed, installed in a fresh profile and registered into profile by harness. It will execute shell commands. No obvious pitfalls found.

The verdict — I would install it because it can be registered by harness after installation in a fresh profile.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Details

typescript

agentscope-ai

3.5k

Connects DeepSeek Harness to ReMe's local-first, self-evolving personal knowledge base: automatically captures completed main-agent conversations as user-owned Markdown memory, searches conversations and source material through reme_search with BM25, optional embeddings, and wikilink expansion, and schedules daily memory consolidation.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourcePython14d ago

AI review

typescript

What it is — The plugin integrates DeepSeek Harness with ReMe's knowledge base to automatically capture main-agent conversations as user Markdown memory and schedule consolidation.

Who it is for — When managing main-agent conversations with DeepSeek Harness and wanting to capture completed dialogues as user-owned Markdown memory, this plugin provides integration. For users who do not want to share the workspace with ReMe, independent knowledge base tools offer a different perspective.

Watch out — The plugin requires manually allowing the build script when installing from source. Sandbox testing has not been completed. The plugin executes shell commands.

The verdict — If I am willing to manually allow the build script from source, I would install it because it connects conversations to persistent Markdown memory.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

ReMe

agentscope-ai

3.4k

Connects DeepSeek Harness to ReMe's local-first, self-evolving personal knowledge base: automatically captures completed main-agent conversations as user-owned Markdown memory, searches conversations and source material through reme_search with BM25, optional embeddings, and wikilink expansion, and schedules daily memory consolidation.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourcePython19d ago

AI review

ReMe

What it is — Integrates ReMe's local-first self-evolving personal knowledge base with DeepSeek Harness.

Who it is for — When running agents using DeepSeek Harness that require automatic capture of conversations as Markdown memory, this is suitable. If you do not need shared local workspace across agents, you can skip this plugin.

Watch out — No obvious pitfalls found. The plugin will execute shell commands.

The verdict — I would install it, but only if shell command execution is permitted.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

MemSearch

zilliztech

2.6k

Shared Markdown memory for DSH and other coding agents, with automatic capture, pre-step context injection, searchable recall, and memory-to-skill self-evolution through a review panel.

No one-line install — this plugin lives inside a larger repository and publishes no npm package.

GitHub sourcePython18d ago

AI review

MemSearch

What it is — MemSearch provides shared Markdown memory for DeepSeek Harness coding agents. It supports automatic capture, pre-step context injection, searchable recall, and memory-to-skill self-evolution through a review panel.

Who it is for — When building complex coding agents with DeepSeek Harness that require persistent context across sessions, MemSearch offers value. If your work involves only short-lived conversations without cross-platform memory needs, you can skip it.

Watch out — It will execute shell commands. Sandbox testing has not been done yet; no obvious issues were identified.

The verdict — I would install it because it enables memory to evolve into reusable skills, but only if you are willing to use it via subdirectory installation and accept shell command execution as a trade-off.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source

deja-vu

vshulcz

975

Memory for coding agents — Claude Code, Codex, Cursor and 17 others. Indexes the sessions they already wrote to disk, including months from before you installed it, and recalls them in any of them. No LLM, no embeddings, one local Go binary.

Installed cleanly when we ran it

GitHub sourceGo6d ago

AI review

deja-vu

What it is — Indexes the sessions coding agents have written to disk for recall in Claude Code and others.

Who it is for — Users working in Claude Code who need to recall solutions from months ago. Users whose work does not involve multi-session coding workflows also do not need it.

Watch out — Requires manual approval of the build script when installing from source. Sandbox test passed. No obvious issues found.

The verdict — I would install it because it recalls existing session history from disk without needing additional model calls.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
2Source

deja-vu

vshulcz

821

Reads the session files thirty-three other coding agents on this machine already wrote — Claude Code, Codex, Cursor, VS Code Copilot Chat, opencode, OpenClaw, Hermes, Kimi, Cline, Zed and more — including sessions from before it was installed: six tools (deja_recall, deja_session, deja_blame, deja_fix, deja_how, deja_remember), a /deja command, and optional automatic recall added to the runtime context. Local BM25 index, no LLM, no embeddings, no network (dsh plugin --profile web add dsh-deja).

Installed cleanly when we ran it

npm packageGo15d ago

AI review

deja-vu

What it is — deja-vu indexes session files from other coding agents to provide memory recall for DeepSeek Harness.

Who it is for — When using DeepSeek Harness with agents like Claude Code for code debugging tasks referencing historical solutions, users missing cross-agent recall benefit from it. If your workflow is limited to a single local agent with no cross-agent session sharing, this plugin is irrelevant.

Watch out — Sandbox testing passed in a new profile with registration in DeepSeek Harness. Index build takes about ten seconds. No obvious issues found.

The verdict — I would install it because it uses local BM25 index with no LLM, no embeddings, and no network.

Generated by grok-4.6, and a starting point rather than a verdict. Where it says a plugin installs or does not, that is from a real run in a clean profile — everything else is read off the repository. Trust the source over this.Read the source
1Source