kepos-hindsight

DSH PLUGIN记忆与知识

仓库 LamplitIsles/kepos-hindsight · npm @lamplitisles/kepos-hindsight

记忆与知识 L5 · 运行验证通过 安全审查:低风险 可信度:金 可安装插件
安装这个插件

为陪伴型 DSH agent 打造的 Hindsight 记忆适配器,每轮对话自动召回并注入记忆,按会话留存完整对话,并提供只读反思工具。

一句话选型结论

按资料字段整理

kepos-hindsight 是记忆与知识类的 DSH 可安装插件,验证等级 L5 · 运行验证通过,安全审查为低风险,列出 5 项功能,有可直接复制的安装命令。验证通过不等于安全:插件会读写文件、执行命令或联网,装前先到仓库确认它做了什么;涉及密钥或系统权限的,建议先在隔离环境试装。

分类记忆与知识 收录类型可安装插件 验证等级L5 · 运行验证通过 安全审查低风险
验证等级 L5 L5 · 运行验证通过
GitHub 星标 1 复刻 0 · 未关闭 issue 未标注
最近更新 2026-09-04 创建于 2026-08-28
README 10.0 KB 正文体量,越大说明说明书写得越细

安装

可安装插件
在 DSH 里执行,装完用 dsh plugin list 确认已挂上;标了 L4 / L5 的命令已在沙盒里真实跑通
dsh plugin --profile web add @lamplitisles/kepos-hindsight@0.2.0
  1. 1
    确认版本与运行环境

    兼容的 DSH 版本为 0.2.0-rc.2 等 6 个;版本不匹配时安装会报错。

  2. 2
    执行安装命令

    在 DSH 里执行上面的命令;多包仓库要注意区分具体子包名,别装错包。

  3. 3
    确认已挂载

    用 dsh plugin list 查看列表里是否出现这个插件,出现即挂载成功。

  4. 4
    试跑并检查权限

    加载后跑一个最小用例,确认它能正常工作;同时看它申请了哪些文件、命令或网络权限。

兼容 DSH 版本0.2.0-rc.2 等 6 个版本版本不匹配时安装会报错
Node.js 要求未标注来自仓库 package.json 的 engines 字段
前置依赖无需要同时安装的同级依赖
npm 包名@lamplitisles/kepos-hindsight可用 npm view 查看包信息

能做什么

5 项功能
字段来自项目仓库与公开索引,中文说明由本站标注

kepos-hindsight:为 DeepSeek Harness 伴侣 Agent 提供关系记忆的 DSH plugin

  • 每轮自动 Hindsight 召回
  • 注入记忆上下文与本地时间
  • 按会话留存完整对话
  • 只读 hindsight_reflect 工具
  • 记忆策略由用户自持

适用场景

记忆

上游标签

agent-memorycompanion-aidsh-plugin

验证等级与安全审查

L5 · 运行验证通过
自动化流程结论,不是人工审核
验证等级L5 · 运行验证通过在 dsh 沙盒中完成安装与运行冒烟——装得上、跑得起来
安全审查低风险静态分析结论,未标注不代表已通过审查
仓库健康度稳定按仓库活跃度与最近更新时间给出
可信度金综合仓库活跃度与验证结果

上面的结论来自上游最近一次自动化验证(2026-10-08): 同一套检查会在插件发新版后重跑,页面显示的是最新一次的逐项结果。

逐项检查结果

L1 · 已找到 ✓ 通过
  • L1.0_DEFAULTED_FROM_L3 由 L3 推定 默认通过——L3 安装规范已通过(全库 L3 扫描策略)
L2 · 结构化 ✓ 通过
  • L2.0_DEFAULTED_FROM_L3 由 L3 推定 默认通过——L3 安装规范已通过(全库 L3 扫描策略)
L3 · 安装规范 ✓ 通过
  • L3.1_INSTALL_COMMAND_PARSED 安装命令已解析 方式:安装规范解析
  • L3.2_DSH_VERSION_DECLARED DSH 版本已声明 方式:DSH 版本声明
L4 · 安装已测 ✓ 通过
  • L4.1_INSTALL_EXECUTED_CONFINED 受限沙盒内执行安装 方式:沙盒安装执行
  • L4.2_INSTALL_SUCCESS 沙盒安装成功 方式:沙盒安装执行
  • L4.3_ARTIFACT_CONFIRMED 安装产物已确认 方式:沙盒安装执行
L5 · 运行已测 ✓ 通过
  • L5.1_INSTALL_PASSED_SANDBOXED 沙盒安装通过 方式:沙盒安装执行
  • L5.2_WEB_BOOT_READY Web 启动就绪 方式:Web 启动
  • L5.3_HTTP_SERVED HTTP 服务响应 方式:HTTP 请求
  • L5.4_PLUGIN_INVENTORY_ACTIVE 插件清单中已激活 方式:插件清单查询

风险详情

  • 审查结论 通过
  • 结论说明 vet 静态分析未发现可疑行为,判定为干净(clean)。
  • 风险计数 严重 0 / 高 0 / 中 0
  • 风险详情 未发现严重或警告级问题。

选择建议

装之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 验证等级 L5:安装和运行都在沙盒里跑通过,装完能直接用的概率高。
  • 静态安全审查为低风险,没有发现明显可疑行为。
  • 有可直接复制的安装命令,不用自己翻文档找入口。
  • 标注了兼容的 DSH 版本(0.2.0-rc.2 等 6 个),按版本装不容易报错。
  • 列出了 5 项功能,能直接看出它解决什么问题。

先想清楚的地方

  • 没有声明 Node.js 版本要求,版本不匹配可能装不上。
  • 验证通过不等于安全:插件会读写文件、执行命令或联网,装前先到仓库确认它做了什么。

更适合

  • 需要在记忆与知识场景里给 DSH 补能力的人。
  • 想装完就能用、不想自己排依赖的人。
  • 能接受在本地装依赖、愿意自己确认权限的人。

不太适合

  • 只使用 DSH 官方内置能力、不接受第三方插件的人。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
插件验证等级安全审查星标兼容版本安装命令
kepos-hindsight当前 L5 · 运行验证通过 低风险 1 0.2.0-rc.2 等 6 个 有
ruflo L3 · 安装规范通过 低风险 7.4 万 未标注 无
OpenViking L3 · 安装规范通过 低风险 3.9 万 未标注 无
WeKnora L4 · 沙盒安装通过 低风险 3.3 万 未标注 有
distilly L4 · 沙盒安装通过 低风险 2.5 万 未标注 有
EverOS L4 · 沙盒安装通过 低风险 1.3 万 未标注 有

仓库档案

记忆与知识
字段来自项目仓库与公开索引,中文说明由本站标注
作者 / 维护方LamplitIsles仓库 kepos-hindsight · 默认分支 未标注
分类记忆与知识memory
收录类型可安装插件声明了 dsh.bundle、可用 dsh plugin add 安装的条目
开发语言TypeScript仓库主语言
许可证Apache-2.0商用或二次分发前请确认条款原文
星标 / 复刻 / issue1 / 0 / 未标注收录时的数值,非实时
创建 / 更新2026-08-28 · 2026-09-04最后推送 未标注
本站收录2026-09-08首次进入本站目录的时间

README 全文

10.0 KB
作者原文,中文版优先;只做安全转义,不改内容

kepos-hindsight

A small Hindsight adapter for a
companion-style DSH agent. It replaces only DSH's official coding-agent
adapter. Codex can keep using the official coding-agent hooks and the same
~/.hindsight/coding-agent.json file.

The package targets the exact DSH 0.1.2-rc.1 Host and Web client contract;
use a matching rc.1 DSH runtime when installing it as a bundle.

What it does

  • Runs raw Hindsight recall on every direct user turn, with the current message
    and a small amount of prior user context.
  • Injects one Hindsight context on every direct turn: the host's current local
    time is authoritative, while recalled facts remain explicitly untrusted
    historical context. Retrieval failures time out and never block a reply.
  • Retains into one stable Hindsight document per session: dsh:.
    The first completed turn after DSH starts replaces it with the full available
    session transcript; later turns append only their JSONL delta.
  • Exposes one deliberate read-only tool: hindsight_reflect, for bank-defined
    synthesis across multiple memories when the automatically supplied raw facts
    and current conversation cannot answer the question.

It does not seed a codebase, create knowledge pages, auto-reflect, import
a bank template, or enable subagents.

Why not use the official coding-agent integration?

The official integration treats a repository or worktree as the durable thing:
it surveys code, retains coding sessions, maintains knowledge pages, recalls
past decisions, and exposes project-oriented tools. That is a good fit for an
engineering agent, but it is the wrong identity and lifecycle for one companion
continuing across unrelated conversations and workspaces.

This adapter changes the product contract rather than merely changing a prompt:

Concern Official coding-agent integration This companion adapter
Durable identity Repository/workspace One user-selected relationship bank
Automatic retrieval Coding knowledge, initial synthesis, and page guidance Raw, non-LLM recall before every direct user turn
Repetition Coding lifecycle decides when synthesis/guidance is useful Every result remains eligible on every relevant turn; no cross-turn suppression
Retention Coding sessions, repository facts, Git/doc strategies Clean user/assistant dialogue in one repairable document per chat session
Reflect Part of the coding knowledge workflow Deliberate explicit tool for questions that need synthesis
Tools Knowledge pages, project search/capture/ingest, Reflect One read-only hindsight_reflect tool
Routing Workspace-derived banks Workspace, CWD, and preset never reroute the selected bank
Policy ownership Ships coding missions and strategies Sends no strategy or mission; the bank owner defines companion memory policy
Agent topology Supports coding-agent and subagent workflows Direct companion sessions only; subagents are excluded

The practical result is continuity without coding-agent overhead: inexpensive
retrieval runs each turn, the full source dialogue is submitted as a stable
session document, and expensive Reflect synthesis happens only when requested.

See Companion memory design for the lifecycle,
failure semantics, prompt boundary, and the design principles behind these
choices.

Bank strategies and prompts

The adapter has no opinion about the bank's retain_mission,
observations_mission, or reflect_mission.

It never calls /import, does not send a Hindsight strategy, and does not
send a retain context. Configure those missions in Hindsight for the target
bank, through its normal UI or bank-config API. This keeps each companion's
memory policy entirely user-owned and prevents a DSH plugin update from
overwriting it.

The short wrapper around recalled facts is a prompt-injection boundary, not a
Hindsight strategy: recalled history is evidence, never an instruction. The
clock is generated locally for the current turn, travels in the same context,
and is excluded from the retained transcript.

Install as a local DSH bundle

pnpm install
pnpm build
dsh plugin --profile web add file:/absolute/path/to/kepos-hindsight

The bundle mounts kepos-hindsight. It does not alter the official Codex
integration. Confirm the composition before starting DSH:

dsh --profile web --dump-config

The output should include an enabled kepos-hindsight row. A running DSH host
must be restarted after changing its bundle list.

For a published release, install the public package directly:

dsh plugin --profile web add @lamplitisles/kepos-hindsight

Configuration

Endpoint, credentials, per-bank missions, and the global disabled flag stay
in the normal shared Hindsight config, ~/.hindsight/coding-agent.json.

Choose the DSH companion bank at Settings → Plugins → Hindsight memory.
It defaults to yuki-memory. This is the only routing choice: a
DSH agent, its preset, its workspace, and the current working directory never
select or remap the bank. The chosen bank is used by automatic recall,
asynchronous retain, and hindsight_reflect alike.

Saving is a live DSH setting and applies on the next turn. DSH intentionally
allows Settings RPC writes only from its loopback Web UI, so change it on the
host rather than through a Kepos-proxied mobile connection.

The optional harnesses.dsh.companion.recall extension tunes retrieval only;
it does not choose a bank or add a recall/retain switch. The official
coding-agent adapter ignores this extension.

{
"harnesses": {
"dsh": {
"companion": {
"recall": {
"budget": "low",
"maxTokens": 900,
"types": ["observation", "world", "experience"],
"preferObservations": true,
"topK": 3,
"contextTurns": 2,
"maxQueryChars": 800,
"timeoutMs": 4000
}
}
}
}
}

This example is optional: the values shown are the defaults. low recall is
retrieval rather than a Reflect LLM request. Raise its budget only after
checking that a real conversation needs broader retrieval. Automatic recall
and retain deliberately have no UI controls; the global Hindsight disabled
and retainSessions settings remain their shared service-level safeguards.

Yuki lives in DSH live config

This repository deliberately ships no Yuki persona or preset. Create and keep
the preset locally under $DSH_HOME/.agent-presets/yuki/, preferably by copying
DSH's current standard preset through DSH's preset UI and then editing the
copy. Disable or remove its delegation group for a single-session companion. The
workspace's own AGENTS.md, SOUL.md, IDENTITY.md, and USER.md remain the
source of truth for personality and relationship behavior.

Development

pnpm check
pnpm test
pnpm build

The tests use fake Hindsight HTTP responses and test-owned temporary config
directories; they never read or modify a live bank.

Maintainer releases

The release workflow publishes @lamplitisles/kepos-hindsight only for a
semantic-version tag matching v. It verifies a frozen pnpm install,
typecheck, tests, build, release preflight, and the packed DSH artifact before
the publish job can run.

First-time npm and GitHub setup

Before the first trusted release, a maintainer must:

  1. Create or claim the @lamplitisles npm scope. Temporarily set the package
    version to the distinct bootstrap prerelease 0.1.0-beta.0 (do not create
    a Git release tag), then run the matching preflight and checks:
pnpm check
pnpm test
pnpm build
GITHUB_REF_NAME=v0.1.0-beta.0 pnpm release:check
pnpm pack-smoke

While authenticated interactively on the maintainer machine, publish that
bootstrap version to npm's beta channel:

npm publish --access public --tag beta

This leaves 0.1.0 available for the first stable OIDC release.
2. In npm package settings, add a Trusted Publisher for the LamplitIsles
GitHub owner, repository kepos-hindsight, workflow
.github/workflows/release.yml, and environment npm.
3. Create the protected GitHub npm environment and apply the repository's
release approval policy (for example, required reviewers and the allowed
release tags).
4. Create the first stable release through the authorized forge command. CI
synchronizes its disposable package manifest from the tag before preflight
and publication:

og tag v0.1.0

The tag starts the OIDC-backed workflow, which publishes 0.1.0 to npm's
latest channel. Do not use a direct Git tag or push command.

Trusted Publishing uses GitHub's OIDC identity and npm provenance. Do not add
an npm authentication token or any other npm credential to this repository or
its GitHub secrets.

Routine release

Create and publish a tag after the change is ready with the repository-authorized
forge command:

og tag v0.1.0

Use a prerelease such as v0.1.1-beta.1 for beta testing. Stable tags publish
to npm's latest dist-tag; tags containing a prerelease identifier publish to
beta. CI synchronizes the package version to the tag in its disposable
verification workspace, then publishes only the verified artifact.

To reproduce the release preflight locally without publishing, use a disposable
working tree, synchronize its package manifest from the tag, then run the
check:

GITHUB_REF_NAME=v0.1.0 pnpm release:sync-version
GITHUB_REF_NAME=v0.1.0 pnpm release:check

The preflight rejects malformed or mismatched tags, non-public npm metadata,
and packed artifacts that omit the DSH entry points or include unsafe build
output. The full local verification remains:

pnpm install --frozen-lockfile
pnpm check
pnpm test
pnpm build
pnpm pack-smoke

Design and operating notes

The companion-memory notes cover
the coding/companion boundary, prompt and extraction policy, session backfill,
cold-start cost, reranking, provider migration, and related integrations.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
kepos-hindsight 怎么安装?

在 DSH 里执行 `dsh plugin --profile web add @lamplitisles/kepos-hindsight@0.2.0` 即可。对应的 npm 包名是 `@lamplitisles/kepos-hindsight`。

kepos-hindsight 的验证等级是什么意思?

L5 · 运行验证通过。在 dsh 沙盒中完成安装与运行冒烟——装得上、跑得起来

kepos-hindsight 安全吗?

低风险。vet 静态分析未发现可疑行为,判定为干净(clean)。

kepos-hindsight 装之前要先确认什么?

先看它会读写哪些文件、执行哪些命令、连接哪些网络地址;验证等级只说明装得上、跑得起来,不等于安全。涉及密钥或系统权限的,建议先在隔离环境试装。

kepos-hindsight 支持哪些 DSH 版本?

上游记录的兼容版本包括 0.2.0-rc.2、0.2.0-rc.1、0.1.7-rc.2、0.1.7-rc.1、0.1.6-alpha.2、0.1.6-alpha.1。

kepos-hindsight 用的是什么许可证?

上游标注为 Apache-2.0。商用或二次分发前请到仓库确认许可证原文。

kepos-hindsight 有哪些功能?

每轮自动 Hindsight 召回、注入记忆上下文与本地时间、按会话留存完整对话、只读 hindsight_reflect 工具、记忆策略由用户自持。

这条记录的数据可靠吗?

本站按仓库名去重后合并整理,字段以作者仓库与 npm 元数据为准;安装命令、仓库地址与 README 保持原文,带 L4 / L5 标记的安装命令已在隔离沙盒里真实跑通。

记忆与知识
按星标排序,可作替代方案

ruflo

ruflo

L3 · 安装规范通过 7.4 万 星

OpenViking

OpenViking

面向 DeepSeek Harness 的 OpenViking 记忆与上下文插件:pre-step 自动召回与画像注入、会话捕获、`vik

L3 · 安装规范通过 3.9 万 星

WeKnora

WeKnora

把 WeKnora 知识库接入 dsh 的四个只读工具:列出知识库、混合检索原文片段、按顺序还原单篇文档,以及直接取用 WeKnora 自己

L4 · 沙盒安装通过 3.3 万 星

distilly

distilly

Distilly — Distill how they think into reusable Skills for any Agent o

L4 · 沙盒安装通过 2.5 万 星

EverOS

EverOS

L4 · 沙盒安装通过 1.3 万 星

MemOS

MemOS

L4 · 沙盒安装通过 1.2 万 星

LamplitIsles 的其它插件

3 个

插件的元信息来自作者仓库;分类、验证等级与安全结论的中文说明为中文整理,最近核验 2026-10-08。