GhostPaw Codex

io.github.GhostPawJS由 GitHub 账号 GhostPawJS 发布v0.6.4更新于 Nov 5, 2026

Local belief and memory engine with evidence, certainty, and honest revision history.

已验证STDIO仅桌面数据库知识与记忆

概览

AI 生成的概览

本地信念与记忆引擎,让助手保存带来源、确定度和修订历史的论断,并可搜索、审阅和修订这些记忆。

可以做什么
  • 按查询检索已存信念,返回排序结果与透明度元数据
  • 查看标记、状态、活动日志、趋势和近似重复对等审阅视图
  • 完整查看单条信念的确定度、新鲜度、来源、谱系和邻近信念
  • 从论断、来源和类别记录新信念,并检测重复与邻近项
  • 通过确认、纠正、合并、遗忘或延后来修订信念
  • 硬删除整条信念谱系,或将两条邻近信念标记为无关
适用场景
适合需要跨会话持久记忆、又不想只往 markdown 文件里不断追加的助手:它保留证据、确定度和修订记录,并把过时或证据薄弱的论断提示出来。最适合记忆保留在本机的本地单用户场景。
运行要求
以本地 stdio 进程运行;npm 包和库需要 Node.js 24 或更高版本,发布版二进制已内置运行时。信念默认存放在 ~/.ghostpaw/codex.db 的 SQLite 文件中,可用 GHOSTPAW_CODEX_DB 环境变量或数据库路径参数更改。无需账号、API 密钥或网络访问。
安装前请注意
retire 会硬删除整条谱系且无法撤销,soft 删除应改用 forget。remember、revise 和 dismiss 都会写入本地数据库,纠正会取代旧信念。搜索是词法匹配而非语义理解,可能漏掉改写过的说法。数据库文件保存助手记录的全部内容,应按敏感数据处理并做好备份。

安装

在 SourceWeft 中

  1. 打开 控制台中的 GhostPaw Codex,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

[GhostPaw codex: When one agent saves a wrong fact, every agent trusts it.]

@ghostpaw/codex

[npm] [CI] [site] [runtime deps] [MCP Registry] [node] [license] [@ghostpaw/codex on AI Agents Listing]

Agent memory as beliefs with a source, a certainty and a revision history.

bash
ghostpaw-codex --help

Local, evidence-backed memory for agents. One SQLite file, zero runtime dependencies.

Codex stores what an agent believes as claims with a source, a certainty, evidence counts, decay and an honest revision history. Agents search before they remember, confirm or correct instead of appending, and see which beliefs are stale, fading or weakly evidenced. It runs as a TypeScript library, an MCP server, a CLI and an Agent Skill, all generated from the same seven tools.

Website: codex.ghostpaw.dev

The release binary includes its runtime. npm and library use require Node.js 24+.

Install

Release binary (default)

Each line downloads the latest release asset, checks it against the release's SHA256SUMS and installs ghostpaw-codex into ~/.local/bin. On Linux and macOS the trailing export puts that folder on PATH for the current shell only: neither the line nor install.sh edits ~/.profile or any other shell startup file. The Windows script adds its folder to the user PATH (open a new terminal afterwards).

linux-x64:

sh
curl -fsSL https://raw.githubusercontent.com/GhostPawJS/codex/main/install.sh | sh -s -- --target linux-x64 && export PATH="$HOME/.local/bin:$PATH"

linux-arm64:

sh
curl -fsSL https://raw.githubusercontent.com/GhostPawJS/codex/main/install.sh | sh -s -- --target linux-arm64 && export PATH="$HOME/.local/bin:$PATH"

darwin-arm64:

sh
curl -fsSL https://raw.githubusercontent.com/GhostPawJS/codex/main/install.sh | sh -s -- --target darwin-arm64 && export PATH="$HOME/.local/bin:$PATH"

darwin-x64:

sh
curl -fsSL https://raw.githubusercontent.com/GhostPawJS/codex/main/install.sh | sh -s -- --target darwin-x64 && export PATH="$HOME/.local/bin:$PATH"

windows-x64 (PowerShell):

powershell
irm https://raw.githubusercontent.com/GhostPawJS/codex/main/install.ps1 | iex

To keep ~/.local/bin on PATH in new shells, append it to ~/.profile once (this is the only step that edits a startup file):

sh
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.profile

To pin a release instead of taking the latest, pass --version:

sh
curl -fsSL https://raw.githubusercontent.com/GhostPawJS/codex/main/install.sh | sh -s -- --target linux-x64 --version 0.6.0 && export PATH="$HOME/.local/bin:$PATH"
text
$ ghostpaw-codex --versionghostpaw-codex 0.6.0 (binary, linux-x64)$ ghostpaw-codex --version --short0.6.0$ ghostpaw-codex --version --json{"name":"ghostpaw-codex","version":"0.6.0","variant":"binary","target":"linux-x64"}

variant is binary, npm or library; target is null outside the release binary.

A session with the 0.5.2 linux-x64 binary against a small database of five beliefs:

[ghostpaw-codex 0.5.2: version --json, belief add, a common-word search with its low-signal warning, a distinctive-word search, alias add and the aliased search]

The same session as an animated GIF.

Other release installers:

sh
mise use -g github:GhostPawJS/codexubi --project GhostPawJS/codex --exe ghostpaw-codex --in ~/.local/bineget GhostPawJS/codex

For aqua, define a github_release package in aqua.yaml:

yaml
registries:  - name: codex    type: local    path: codex-registry.yamlpackages:  - name: GhostPawJS/[email protected]    registry: codex

codex-registry.yaml:

yaml
packages:  - type: github_release    repo_owner: GhostPawJS    repo_name: codex    asset: ghostpaw-codex-{{trimV .Version}}-{{.OS}}-{{.Arch}}.tar.gz    format: tar.gz    replacements: { amd64: x64 }    overrides:      - goos: windows        asset: ghostpaw-codex-{{trimV .Version}}-windows-{{.Arch}}.zip        format: zip    files:      - name: ghostpaw-codex

Install scripts verify SHA256SUMS. To verify a downloaded archive's build attestation:

sh
gh attestation verify <archive> -R GhostPawJS/codex

Set GHOSTPAW_VERIFY=attestation for attestation verification in install.sh. Binaries are unsigned; macOS binaries carry an ad-hoc signature. For a browser download on macOS, remove quarantine with xattr -d com.apple.quarantine /path/to/ghostpaw-codex. Linux binaries require glibc 2.28+; use npx on Alpine. See the binary build workflow.

Approximate sizes for 0.5.2 (Node 26.12.1 inside each binary):

TargetArchiveBinary
linux-x6441.7 MB tar.gz117.4 MB
linux-arm6441.2 MB tar.gz115.2 MB
darwin-arm6444.8 MB tar.gz146.7 MB
darwin-x6446.4 MB tar.gz149.5 MB
windows-x6438.4 MB zip105.6 MB

The npm package is about 920 KB unpacked and needs Node 24+. Every release is installed and run on ubuntu-24.04, macos-15 and windows-2025 by the install check.

npx / npm (for npm-based environments)

The npm package requires Node 24+:

sh
npm install -g @ghostpaw/codexnpx -y @ghostpaw/codex --help

Library (for harnesses embedding it in code)

Requires Node 24+:

sh
npm install @ghostpaw/codex
ts
import { initCodexTables, read, write } from '@ghostpaw/codex';

See Library usage.

30-second quickstart

MCP server

Every client below starts the same stdio server: ghostpaw-codex mcp. Use the full executable path if its folder is not on PATH. For npm-based environments, use npx -y @ghostpaw/codex mcp. Beliefs live in ~/.ghostpaw/codex.db unless the GHOSTPAW_CODEX_DB environment variable (absolute path) or --db <path> says otherwise.

Claude Code

bash
claude mcp add ghostpaw-codex -- ghostpaw-codex mcp

or as a plugin, which also installs the skill:

bash
/plugin marketplace add GhostPawJS/codex/plugin install ghostpaw-codex@ghostpaw-codex

Codex CLI (~/.codex/config.toml)

toml
[mcp_servers.ghostpaw-codex]command = "ghostpaw-codex"args = ["mcp"]

Cursor (.cursor/mcp.json), Claude Desktop (claude_desktop_config.json) or a project .mcp.json:

json
{  "mcpServers": {    "ghostpaw-codex": {      "command": "ghostpaw-codex",      "args": ["mcp"]    }  }}

Cline (MCP Servers → Configure MCP Servers, cline_mcp_settings.json). VS Code often starts without ~/.local/bin on PATH, so use the absolute path that echo "$HOME/.local/bin/ghostpaw-codex" prints (PowerShell: "$env:LOCALAPPDATA\Programs\ghostpaw\bin\ghostpaw-codex.exe"). Merge the entry into the existing mcpServers. Settings file locations, the cline mcp add form and checks: llms-install.md. For Cline CLI 3.x, cline config mcp lists the configured servers.

json
{  "mcpServers": {    "ghostpaw-codex": {      "command": "/absolute/path/to/ghostpaw-codex",      "args": ["mcp"],      "env": { "GHOSTPAW_CODEX_DB": "/absolute/path/to/.ghostpaw/codex.db" }    }  }}

Claude Desktop users can also install server.mcpb from the latest GitHub release. A Dockerfile is included for container hosts: docker build -t ghostpaw-codex . && docker run -i --rm -v codex:/data ghostpaw-codex.

The server speaks MCP 2026-07-28 (stateless, server/discover) and the initialize-based revisions 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05.

CLI

text
ghostpaw-codex search <query> [--limit N --min-score N --category C --source S]ghostpaw-codex review <flags|status|log|trends> [--limit N --now N]ghostpaw-codex belief add <claim> --source S --category C [--certainty N --provenance P]ghostpaw-codex belief show <beliefId>ghostpaw-codex belief retire <beliefId>ghostpaw-codex belief confirm|correct|forget|defer <beliefId> [flags]ghostpaw-codex belief merge <beliefIds...> [flags]ghostpaw-codex proximity dismiss <beliefA> <beliefB>ghostpaw-codex mcp|skill|tools|describe|call|completions|version|help

Belief additions include a nearest-belief hint when an active belief has similarity of at least 0.7; use it to confirm or merge related claims.

WARNING: belief retire hard-deletes the whole lineage (the belief and all its predecessors/successors) and cannot be undone. Use belief forget for soft removal that keeps lineage. Every retire invocation warns on stderr.

--json is accepted on every read command, including all review views, belief show, alias list, tools, describe, version, help and skill guides. Set GHOSTPAW_OUTPUT=json to opt all commands into JSON output as if --json were passed. Other values or an unset variable preserve default output, including when stdout is piped or a TTY.

Global flags can appear anywhere: --db <path>, --json, --quiet, --compact, --help/-h, --version/-V/-v, --no-color. NO_COLOR is accepted; output uses no terminal colors. Noun-verb commands print short text by default, including when stdout is piped. Search and review lists show one belief per line: id claim [certainty source strength]. Flags append reason codes; the log shows id type claim. Add, show, correct and merge show aligned detail fields and nearby beliefs. Status and trends show aligned key: value lines. --json prints the full tool result and --compact removes JSON indentation. Legacy tool invocation keeps its JSON output. --quiet prints only result ids for search, review flags and log, and the affected belief id for writes; status, trends and version print nothing.

Use help belief, belief --help or belief correct --help for schema-derived help. Each revision verb accepts only the flags it uses. Correction takes --claim; forgetting also accepts --successor-id. Deferral accepts --deferred-until as YYYY-MM-DD, DD.MM.YYYY, today, tomorrow, +3d, an ISO date-time with timezone, or epoch milliseconds. Calendar dates resolve to local end of day and must be in the future. Array flags repeat, kebab-case flags map to schema properties, and values are literal, including leading @. Use JSON stdin (-) for long input. -- ends flags. A positional -, or piped stdin with no arguments, reads a JSON object; explicit flags override its fields. Database selection uses --db, GHOSTPAW_CODEX_DB, then ~/.ghostpaw/codex.db. Opening the default database prints using default db <path> once on stderr. Suppress the notice with --quiet or GHOSTPAW_QUIET=1. Commands that do not open a database print no notice. Top-level help shows the resolved path. Version output starts with ghostpaw-codex and identifies binary target, npm or library execution.

ghostpaw-codex skill prints the full skill reference. Use ghostpaw-codex skill --list to list workflow guides and ghostpaw-codex skill capture-beliefs-well to read a guide. skill --help shows these forms; unknown guide names include a suggestion.

ExitNoun-verb result
0Success, including no_op
1Tool error
2Usage or schema error
3Clarification needed or not found
4Conflict or version mismatch
70Internal error

Errors and recovery hints go to stderr. Clarification prints the question and missing flags to stderr. With --json, usage and internal errors also print {ok:false,error:{code,message}} to stdout. Tool results retain their full shape. Legacy tools [--json], describe <tool>, call <tool> [JSON|-] and <tool_name> --parameter value keep their existing exit codes. completions bash, completions zsh and completions fish print shell scripts.

sh
ghostpaw-codex belief add "Deploys go out on Tuesdays" --source explicit --category procedure
sh
ghostpaw-codex search "when do we deploy" --json | jq '.data.results'
sh
printf '%s' '{"beliefId":1}' | ghostpaw-codex belief show - --json

File values and leading @

File input is opt-in for each CLI argument. When an argument's help lists (@file, @- stdin, @@ literal @), @path reads a UTF-8 file, @- reads stdin, and @@text passes the literal value @text.

No current Codex argument enables this option: flags and positional values keep leading @ and @@ as written. For long claims, pass a JSON object through stdin with - (see the example above).

Agent Skill

SKILL.md (repo root) and skills/codex/SKILL.md follow the Agent Skills format and ship in the npm package. Copy skills/codex/ into your agent's skills folder, or print it:

bash
ghostpaw-codex skill > SKILL.md

Library

bash
npm install @ghostpaw/codex
ts
import { DatabaseSync } from 'node:sqlite';import { initCodexTables, read, write } from '@ghostpaw/codex';
const db = new DatabaseSync('codex.db');initCodexTables(db);
const { id } = write.remember(db, {  claim: 'The API uses GraphQL with a REST fallback.',  source: 'explicit',  category: 'fact',});write.confirmBelief(db, id);write.correctBelief(db, id, {  claim: 'The API uses GraphQL exclusively; REST was retired.',  source: 'observed',  category: 'fact',});
read.recall(db, 'graphql api'); // ranked, lineage-awareread.listFlags(db);             // stale, fading, low-trust, single-evidence

Wire the same tools into any LLM SDK. Each tool carries a JSON Schema:

ts
import { tools } from '@ghostpaw/codex';
for (const tool of tools.codexTools) {  // tool.name, tool.description, tool.inputSchema, tool.handler(db, input)}

Or embed the MCP server in your own process:

ts
import { createCodexMcpServer } from '@ghostpaw/codex/mcp';const server = createCodexMcpServer({ dbPath: './codex.db' });

Docs

The live demo runs the library in your browser against an in-memory SQLite database. Each view below opens a different part of it:

  • Dashboard: integrity score and recent beliefs
  • Capture: record a belief and see close matches you already hold
  • Flags: beliefs flagged for review: confirm, correct or forget
  • Activity Log: activity log of every write

Why not MEMORY.md?

A markdown memory file works until it doesn't:

  • It only grows. Agents append, rarely delete, and the file ends up in every prompt. Codex returns the few beliefs that match a query (FTS5 bm25 plus hashed character-trigram similarity, IDF-weighted with a 55% relative cutoff).
  • Contradictions pile up. "We use REST" and "REST was retired" sit side by side. Codex detects near-duplicates on every write, and corrections supersede the old belief while keeping the lineage.
  • Everything looks equally true. A guess and a confirmed fact read the same in prose. Codex tracks source (explicit, observed, distilled, inferred), certainty and evidence count, and flags what is stale or weakly supported.
  • No time. Codex decays freshness, so old beliefs surface for review instead of quietly steering behaviour.
  • Concurrent edits. Two agents writing one file clobber each other. Codex is a SQLite database in WAL mode.

It stays local: one file you can copy, back up or inspect with any SQLite tool. No server, no API key, no network.

Tools

ToolWhat it does
search_codexLexical recall with FTS5 bm25 and character-trigram similarity
review_codexDashboards: flags, status, trends, log
inspect_codex_itemOne belief in full: metrics, lineage, nearby beliefs
remember_beliefCapture a claim with source, category and provenance
revise_beliefConfirm, correct, forget, defer or merge
retire_beliefHard-delete for privacy or cleanup
dismiss_proximityMark two nearby beliefs as intentionally distinct

Results are structured (outcome: success | no_op | needs_clarification | error) with entities, next-step hints and recovery advice. The MCP server, CLI, SKILL.md and plugin manifests are generated from this registry (npm run surfaces) and drift-checked in CI.

Performance

Measured with npm run bench on Node 24.14.0, Linux, Intel Xeon (shared cloud vCPU), 10,000 beliefs in a file-backed database:

Operationp50p95
search_codex (tool)3.6 ms5.0 ms
MCP tools/call search, stdio framing included3.8 ms4.2 ms
read.recall3.7 ms4.8 ms
inspect_codex_item3.5 ms3.8 ms
write.remember (includes proximity scan)4.5 ms5.6 ms
review_codex11.7 ms13.2 ms

Cold start (process spawn to first response, median): --version 26 ms, MCP server/discover 24 ms, first search against the 10,000-belief file 53 ms. Seeding 10,000 beliefs takes 2.2 s on disk.

Gzip sizes and cold-start medians are budgeted in budgets.json and enforced by npm run check.

The model

ConceptPurpose
BeliefA claim held with certainty, evidence, provenance, decay and revision lineage
DismissalA record that two beliefs close by character-trigram vectors are intentionally distinct
FlagA derived attention signal: stale, fading, low-trust, single-evidence or gap
ProximityLexical nearness between beliefs (character-trigram vectors), detected on write
LineageThe revision chain from corrections and supersessions, with version diffs

State is derived, never toggled: freshness, strength, review priority and flags are computed at read time.

Package surface

ImportContents
@ghostpaw/codexinitCodexTables, read, write, tools, skills, soul, all types
@ghostpaw/codex/mcpcreateCodexMcpServer, serveCodexMcp, generic MCP server helpers
ghostpaw-codex (bin)Noun-verb CLI, legacy tool forms, mcp, skill, shell completions
dist/mcp-server.jsStandalone stdio MCP server entry (used by the MCP Bundle and the Dockerfile)
SKILL.md, skills/codex/Agent Skill with 17 workflow references

ESM and CommonJS, with type declarations for both.

Documentation

DocumentAudience
HUMAN.mdDevelopers using the read / write API
LLM.mdAgent builders wiring soul, tools and skills
docs/README.mdArchitecture: model, invariants, scoring, source layout
docs/entities/Per-entity manuals with exact public API listings
CHANGELOG.mdRelease history

Development

bash
npm installnpm run check   # types, lint, zero-deps, tests, build, surfaces, size, API, consumer, startup, ratchetnpm run bench   # hot-path benchmarks at 10,000 beliefsnpm run surfaces  # regenerate SKILL.md, plugin manifests, server.json, mcpb manifest

npm run check is the single gate, locally and in CI. Size budgets (budgets.json) and the public API snapshot (api-surface.json) can only grow with an explicit approval tag in the commit message. The repo is pinned to Node 24.14.0 via .nvmrc.

Support

If this package helps your project, consider sponsoring its maintenance:

[GitHub Sponsors]


Anonyfox • MIT License

Query aliases

Search is lexical: FTS5 bm25 plus hashed character-trigram similarity, with IDF-like token weighting and a 55% relative cutoff. It does not provide semantic understanding. In corpora of at least 20 active beliefs, queries matching only common terms return at most three results with a partial_match warning.

Aliases are off by default (the table starts empty). Add directed, one-hop aliases when query vocabulary differs from stored claims:

sh
ghostpaw-codex alias add class warriorghostpaw-codex alias listghostpaw-codex alias remove class warrior

The library equivalents are write.addQueryAlias(db, term, alias, options?), write.removeQueryAlias(db, term, alias) (returns whether removed), and read.listQueryAliases(db) (sorted { term, alias, createdAt } records). Both words are normalized with normalizeClaim and must be distinct single words. Adding an existing pair preserves its creation time; options.now sets the time on first insertion. Expansion is deduplicated and never follows alias chains; the query vector uses the original query.

Provenance and revision compatibility

Belief records include provenanceSources, an append-only list of distinct origin references. Every write with --provenance adds a reference, including duplicate adds and unchanged corrections. Corrections and merges carry all sources forward. The legacy provenance field remains readable with its existing single-value behavior; use provenanceSources for the complete history.

Superseded-belief errors and belief show identify the current active successor. Library details also expose activeSuccessorId, while supersededBy retains the immediate lineage link. Correcting to the same normalized claim and metadata returns no_op. A merge into --successor-id can omit --claim.

belief --help lists belief verbs. review flags --now +8d and review flags --now 2026-11-10 accept the same date formats as deferral, including historical dates and epoch milliseconds. Relative day offsets also accept -3d and 30d. Calendar dates and relative days use local end of day.

New CLI and MCP database files use mode 0600; newly created parent directories use 0700. Existing permissions are preserved. On first upgrade, legacy active normalized duplicates consolidate into the oldest id, preserving summed evidence, source references and lineage. Later --allow-duplicate additions remain separate. Merge fan-in alone does not trigger unstable; repeated corrections still do.

Search treats punctuation literally; wrap the whole query in double quotes for a phrase. Use search --fts 'alpha OR beta' for raw FTS5 syntax, or search note --prefix "project:" to filter claims by a case-insensitive prefix after leading whitespace. A query is required with --prefix. Library recall options and search tool inputs also accept fts and prefix. Default search ranks claims whose entity before the first colon matches the leading query tokens first, ignoring case and treating spaces and hyphens alike (for example, Agentpreneur: ... for Agentpreneur state files routine memory db). This also applies with --prefix; --fts and quoted phrase ranking remain unchanged.

Review status integrity remains the percentage of active beliefs with certainty at least 0.7. The new, unconfirmed count covers beliefs with one evidence item younger than seven days; it overlaps the existing strength counts.

Review: review status --by-prefix counts active claim prefixes; review duplicates --limit 20 lists nearby active pairs immediately, honoring dismissals.

来源:README.md,提交 54fc4fe

工具

7

search_codex

Search active beliefs by natural language query. Returns ranked matches with recall scores and transparency metadata. Use when: Use this to find beliefs about a topic before acting on them. Always search before creating a new belief to avoid duplicates. Not for: Do not use this for browsing all beliefs — use review_codex with the status or flags view instead.

输入参数ftslimitquery必填prefixsourcecategoryminScore

review_codex

Load a codex review surface: flags for beliefs needing attention, status for portfolio health, log for recent activity, trends for time-based patterns, or duplicates for nearby active pairs. Use when: Use this when you need an overview of the codex state rather than a specific belief. Start with flags for maintenance, status for a dashboard, or log for recent changes. Not for: Do not use this to find a specific belief by topic — use search_codex instead. Do not use this to inspect one belief deeply — use inspect_codex_item.

输入参数nowview必填limitbyPrefix

inspect_codex_item

Inspect one belief in full detail: certainty, freshness, strength, source, category, lineage chain, proximity to similar beliefs, and version diff when applicable. Use when: Use this after finding a belief through search_codex or review_codex to understand it deeply before deciding whether to confirm, correct, or forget it. Not for: Do not use this for bulk browsing — use review_codex for lists. Do not call this without a specific belief id.

输入参数beliefId必填

remember_belief

Capture a belief from a claim, source, and category. Reuses active normalized duplicates unless allowDuplicate is set, and detects nearby beliefs. Use when: Use this when a new proposition should enter the codex. Always search first to check whether the belief already exists — prefer confirming or correcting an existing belief over creating a duplicate. Not for: Do not use this to update an existing belief. Use revise_belief with the correct, confirm, or merge action instead.

输入参数claim必填source必填category必填certaintyprovenanceallowDuplicate

revise_belief

Revise an existing belief: confirm it still holds, correct it with a new claim, merge multiple beliefs into one, forget it from active recall, or defer its next flag review. Use when: Use this after inspecting a belief to act on it. Choose the action that matches the situation: confirm for reinforcement, correct for changed understanding, merge for consolidation, forget for removal from active recall, defer for postponing review. Not for: Do not use this to create a new belief — use remember_belief. Do not use this to permanently delete a belief — use retire_belief.

输入参数claimaction必填sourcebeliefIdcategorybeliefIdscertaintyprovenancesuccessorIddeferredUntil

retire_belief

WARNING: Hard-deletes the whole lineage (the belief and all its predecessors/successors) and cannot be undone. Use belief forget for soft removal that keeps lineage. Use when: Use this only for privacy cleanup or hard erasure. The belief and all of its lineage (predecessors and successors) will be destroyed. Not for: Do not use this for normal belief lifecycle — use revise_belief with the forget action to preserve the audit trail.

输入参数beliefId必填

dismiss_proximity

Record that two beliefs are not meaningfully related despite proximity detection. Uses exponential backoff — the pair will resurface less frequently with each dismissal. Use when: Use this after inspecting two proximate beliefs and determining they are not duplicates or in conflict. The dismissal suppresses the pair in future proximity results. Not for: Do not use this if the beliefs are genuinely related — instead use revise_belief to merge, correct, or forget one of them.

输入参数beliefA必填beliefB必填

版本历史

5
  1. v0.6.4最新Nov 5, 2026
  2. v0.6.3Nov 5, 2026
  3. v0.6.2Oct 30, 2026
  4. v0.6.1Oct 29, 2026
  5. v0.3.2Oct 25, 2026

评分

已满足适用检查项的 90%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分
  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分