GhostPaw Codex

MCP文档知识

提供方 未标注

文档知识 stdio · 本地进程 会话登录 社区 / 第三方 Claude DesktopClaudeCursorVS Code
查看接入方式

为 AI 智能体提供本地记忆。信念将其来源、确定性和修订历史保存在一个 SQLite 文件中。MCP 服务器、CLI 和 Agent Skill。零依赖。

一句话选型结论

按资料字段整理

GhostPaw Codex 属于文档知识类 MCP 服务器,stdio · 本地进程,会话登录,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式stdio · 本地进程 鉴权会话登录 部署方式本地部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

stdio · 本地进程 会话登录
客户端在本机拉起子进程,数据不出本机
npm install -g @ghostpaw/codex npx -y @ghostpaw/codex --help

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Node.js 等运行时,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

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

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 使用前要准备好会话登录对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
GhostPaw Codex当前 未标注 stdio · 本地进程 本地部署 有 2026-11-20
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式会话登录远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

26.0 KB
来自项目仓库与上游目录的原文,未做删改

@ghostpaw/codex

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 --version
ghostpaw-codex 0.6.0 (binary, linux-x64)
$ ghostpaw-codex --version --short
0.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:

The same session as an animated GIF.

Other release installers:```sh
mise use -g github:GhostPawJS/codex
ubi --project GhostPawJS/codex --exe ghostpaw-codex --in ~/.local/bin
eget GhostPawJS/codex


For aqua, define a
`github_release` package in `aqua.yaml`:```yaml
registries:
  - name: codex
    type: local
    path: codex-registry.yaml
packages:
  - name: GhostPawJS/codex@v0.6.0
    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):

Target Archive Binary
linux-x64 41.7 MB tar.gz 117.4 MB
linux-arm64 41.2 MB tar.gz 115.2 MB
darwin-arm64 44.8 MB tar.gz 146.7 MB
darwin-x64 46.4 MB tar.gz 149.5 MB
windows-x64 38.4 MB zip 105.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/codex
npx -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.

Running inside sandboxed agent harnesses

Inside a Codex CLI --sandbox workspace-write session, the database and its
parent directory must be inside a writable root, including SQLite's -wal and
-shm side files. A default DB under ~/.ghostpaw outside those roots can fail
with SQLITE_CANTOPEN or EPERM (often exit 70; directory creation failures
may exit 2), even when normal shell permissions allow access. Put the DB inside the workspace with --db ./state/codex.db,
or set GHOSTPAW_CODEX_DB="$PWD/state/codex.db" for CLI/MCP use.

To use an external DB directory, add it when starting the OpenAI Codex CLI
(replace `` with its absolute path):```sh
codex exec --sandbox workspace-write --add-dir <dir-with-db> "Run the GhostPaw CLI"


Alternatively, set `sandbox_workspace_write.writable_roots` in
`~/.codex/config.toml` before starting the session:```toml
[sandbox_workspace_write]
writable_roots = [&quot;/absolute/dir-with-db&quot;]

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 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
{
  &quot;mcpServers&quot;: {
    &quot;ghostpaw-codex&quot;: {
      &quot;command&quot;: &quot;ghostpaw-codex&quot;,
      &quot;args&quot;: [&quot;mcp&quot;]
    }
  }
}

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 &quot;$HOME/.local/bin/ghostpaw-codex&quot; prints (PowerShell:
&quot;$env:LOCALAPPDATA\Programs\ghostpaw\bin\ghostpaw-codex.exe&quot;). 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 . &amp;&amp; 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 &lt;query&gt; [--limit N --min-score N --category C --source S]
ghostpaw-codex review &lt;flags|status|log|trends&gt; [--limit N --now N]
ghostpaw-codex belief add &lt;claim&gt; --source S --category C [--certainty N --provenance P]
ghostpaw-codex belief show &lt;beliefId&gt;
ghostpaw-codex belief retire &lt;beliefId&gt;
ghostpaw-codex belief confirm|correct|forget|defer &lt;beliefId&gt; [flags]
ghostpaw-codex belief merge &lt;beliefIds...&gt; [flags]
ghostpaw-codex proximity dismiss &lt;beliefA&gt; &lt;beliefB&gt;
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, --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. Except for raw belief import, 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 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.

Exit Noun-verb result
0 Success, including no_op
1 Tool error
2 Usage or schema error
3 Clarification needed or not found
4 Conflict or version mismatch
70 Internal 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, call [JSON|-]
and --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 &quot;when do we deploy&quot; --json | jq &#x27;.data.results&#x27;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&#x27;s help lists
`(@file, @- stdin, @@ literal @)`, `@path` reads a UTF-8 file, `@-` reads
stdin, and `@@text` passes the literal value `@text`.

The belief import input enables this option. Other Codex arguments do not: 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&#x27;s skills folder, or print it:```bash
ghostpaw-codex skill &gt; 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-aware
read.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 &#x27;@ghostpaw/codex&#x27;;

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&#x27;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.** &quot;We use REST&quot; and &quot;REST was retired&quot; 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

| Tool | What it does |
|---|---|
| `search_codex` | Lexical recall with FTS5 bm25 and character-trigram similarity |
| `review_codex` | Dashboards: flags, status, trends, log |
| `inspect_codex_item` | One belief in full: metrics, lineage, nearby beliefs |
| `remember_belief` | Capture a claim with source, category and provenance |
| `revise_belief` | Confirm, correct, forget, defer or merge |
| `retire_belief` | Hard-delete for privacy or cleanup |
| `dismiss_proximity` | Mark 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:

| Operation | p50 | p95 |
|---|---:|---:|
| `search_codex` (tool) | 3.6 ms | 5.0 ms |
| MCP `tools/call` search, stdio framing included | 3.8 ms | 4.2 ms |
| `read.recall` | 3.7 ms | 4.8 ms |
| `inspect_codex_item` | 3.5 ms | 3.8 ms |
| `write.remember` (includes proximity scan) | 4.5 ms | 5.6 ms |
| `review_codex` | 11.7 ms | 13.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

| Concept | Purpose |
|---|---|
| **Belief** | A claim held with certainty, evidence, provenance, decay and revision lineage |
| **Dismissal** | A record that two beliefs close by character-trigram vectors are intentionally distinct |
| **Flag** | A derived attention signal: stale, fading, low-trust, single-evidence or gap |
| **Proximity** | Lexical nearness between beliefs (character-trigram vectors), detected on write |
| **Lineage** | The 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

| Import | Contents |
|---|---|
| `@ghostpaw/codex` | `initCodexTables`, `read`, `write`, `tools`, `skills`, `soul`, all types |
| `@ghostpaw/codex/mcp` | `createCodexMcpServer`, `serveCodexMcp`, generic MCP server helpers |
| `ghostpaw-codex` (bin) | Noun-verb CLI, legacy tool forms, `mcp`, `skill`, shell completions |
| `dist/mcp-server.js` | Standalone 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

| Document | Audience |
|---|---|
| HUMAN.md | Developers using the `read` / `write` API |
| LLM.md | Agent builders wiring `soul`, `tools` and `skills` |
| docs/README.md | Architecture: model, invariants, scoring, source layout |
| docs/entities/ | Per-entity manuals with exact public API listings |
| CHANGELOG.md | Release history |

## Development```bash
npm install
npm run check   # types, lint, zero-deps, tests, build, surfaces, size, API, consumer, startup, ratchet
npm run bench   # hot-path benchmarks at 10,000 beliefs
npm 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:


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 warrior ghostpaw-codex alias list ghostpaw-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 &#x27;alpha OR beta&#x27; for raw FTS5 syntax, or
search note --prefix &quot;project:&quot; 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.

review duplicates suggests only pairs with the same normalized colon prefix or leading entity by default (case-insensitive, including multiword and hyphenated prefixes). Unprefixed claims pair with other unprefixed claims. Use review duplicates --cross-entity (crossEntity: true in review_codex) to include pairs across entities as before. Suggestions do not change beliefs; inspect each pair before merging or forgetting.

Belief JSON keeps the existing strength display tier and adds integrityTier, the certainty-only tier used by review status. Display strength is strong when certainty >= 0.4 and freshness >= 0.7; otherwise it falls back to the certainty tier. Thus certainty >= 0.7 always displays strong, even when stale. integrityTier is strong at certainty >= 0.7, fading at >= 0.4, otherwise faint. Integrity counts strong active beliefs divided by all active beliefs. Human belief show labels these as display strength and integrity tier; a fresh inferred belief at certainty 0.5 can display strong while its integrity tier is fading.

Batch import and topics

ghostpaw-codex belief import @beliefs.jsonl --json reads a UTF-8 JSON Lines
file or JSON array. Use belief import - --json (or @-) for raw stdin. Each item has
claim, source, category and optional certainty, provenance, topic,
allowDuplicate, matching belief add. --dry-run runs the same writes and
rolls back, returning provisional IDs. An empty batch succeeds without writes.

The import_beliefs tool accepts {items: [...]} or {input: &quot;JSON/JSONL text&quot;},
plus optional dryRun. Library: write.importBeliefs(db, items, {dryRun}).
The whole batch is atomic. Success returns data.items with zero-based index,
id, and duplicate when reused. Any item error rolls back the entire batch;
the tool returns error.details.items with each item's error, including rollback
status for otherwise valid items. Rolled-back IDs are omitted. Malformed JSON
is rejected before any write; malformed JSON Lines errors identify the line.
Imports preserve the normal normalized duplicate policy and provenance history.

belief add --topic work and belief correct --claim TEXT --topic work
set an exact topic label. Corrections inherit omitted topics; merges inherit
the primary belief's topic (or existing successor's) unless supplied. Duplicate
adds keep the existing ID and update topic when explicitly supplied. Topics
must be non-empty strings. Existing databases gain a nullable topic column
idempotently; unset topics are omitted from JSON, preserving existing output.
Use search QUERY --topic work, review list --topic work, or
read.listBeliefs(db, {topic: &quot;work&quot;}). Tool inputs accept the same topic field;
review_codex view list lists active beliefs by ID, default limit 20.

Unstable revision history

The unstable flag is derived at read time when a correction-connected lineage
contains more than two beliefs (normally the original plus two corrections).
Legacy supersessions without a reason also count; merge-only edges do not.
It signals revision history worth inspecting, not a false claim or low certainty.
Confirmation raises evidence and certainty but does not clear unstable, and
further corrections retain that history. Deferral hides all flags until its
expiry, then unstable returns if the history still qualifies. There is no
acknowledge/reset action: it clears only when the qualifying history no longer
exists (for example after hard deletion for an independent privacy need).
Do not delete history merely to silence the signal.

常见问题

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

在客户端按下面的安装命令接入:npm install -g @ghostpaw/codex npx -y @ghostpaw/codex --help。装完在客户端配置里引用同一个包或端点。

GhostPaw Codex 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

GhostPaw Codex 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

GhostPaw Codex 需要 API Key 吗?

资料标注需要会话登录认证,使用前准备好对应凭据,并按最小权限配置。

GhostPaw Codex 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Cline、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

GhostPaw Codex 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

GhostPaw Codex 需要什么运行环境?

属于本地进程,需要在本机装好运行环境。

GhostPaw Codex 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。