This article is derived from the plugin's already-indexed fields (wiki / faq / compatibility_json / readme), not freshly generated by AI. Source field is noted at the end of each section.

Quick start

hindsight

— source: plugin_wiki.wiki_content

Install & verify

dsh plugin --profile web add @vectorize-io/hindsight-coding-agents

Run the command above in your DSH Web Profile. Then enable the plugin in the plugin list.

— source: plugins.install

Key points

• Memory Performance & Accuracy
• Quick Start — server · clients · platforms · embedded
• Adding Hindsight to Your Agent — LLM Wrapper · integrations · coding agents · MCP
• Use Cases
• Running in Production

— source: plugin_wiki.readme_en (fallback readme_raw)

FAQ

Do I need to run any commands to initialize the memory after installation?

No. When enabled, the plugin automatically performs cold start checks, background git history fetching, and codebase structure retrieval at the start of each session. Memory is continuously supplemented in the background, with no manual commands to run.

Where is the data stored? Is it uploaded to the cloud?

Defaults to Hindsight Cloud (requires API Token), but can also be changed to a self-hosted service or local daemon (127.0.0.1:9077). Chat records and knowledge pages are written to the 'Memory Bank', isolated by repository.

Will multiple DSH sessions (different projects) mix data?

No. Each workspace is independently parsed into a Memory Bank (default naming coding-agent::<repo name>), and the plugin creates separate databases based on session.header.cwd. Sub-agent sessions won't write to the database repeatedly either.

Which layer is it installed on, does it affect all DSH profiles?

Via cordis.patch.yml mounted to the host layer, effective for all profiles; if you only want to disable it for a specific profile, change that line in that profile's own cordis.patch.yml to disabled: true.

How to disable memory for a specific repository?

Set disabled: true for the bank ID in the banks section of ~/.hindsight/coding-agent.json, or list only allowed directories in optInPaths and set optInOnly to true.

Where do the retrieved results appear?

Retrieved content is appended to the model context as a user message with source: { kind: 'plugin', form: 'recall' }; the model can also actively query using tools like hindsight_search_knowledge_pages and hindsight_reflect.

— source: plugin_wiki.faq_json

Compatibility

• DSH: 未声明
• Node: 未声明
• Platforms: macOS, Windows, Linux

— source: plugin_wiki.compatibility_json

Pitfalls

Review the upstream repo before installing. This guide is auto-derived from indexed fields and may lag the latest release. If anything contradicts the official docs, treat the upstream source as authoritative.

— source: general rule