What can you do with this server?

With this server, you can persist, retrieve, audit, and lifecycle-manage local, SQLite-backed coding-agent memory through six MCP tools. * mem_save — save verified evidence, observations, observation reviews/promotions, or directly promoted durable memories such as decisions, conventions, failures, discoveries, and handoffs. * mem_recall — search promoted project memory with current or historical temporal scope and compact or context-return modes. * mem_context — build bounded project-wide or session-specific continuity briefings, prioritizing handoffs. * mem_get — expand a selected memory, summary, observation, or evidence record, optionally including predecessor lineage. * mem_project — inspect project views without mutation: list aliases, view timelines, briefings, history, summaries, and observations. * mem_session — record verified root lifecycle events and versioned summaries for enroll, recover, capture root, checkpoint pre-compact, guide post-compact, and finalize.

How do I use Thoth-Mem?

1. Click on "Deploy Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@Thoth-Mem recall the auth pattern from last session" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

de en es ja ko ru zh

Thoth-Mem

by EremesNG

Overview Schema Source Related Servers Discussions Admin

TypeScript

Local

thoth-mem

Persistent memory your coding agents can share — and you can audit.

Local, SQLite-first memory for OpenCode, Codex, Claude Code, and Pi. Six focused MCP tools. Zero model calls required.

npm version CI status Node.js 22.12 or newer MIT license

Overview • Install • How it works • Use • Tools • Benchmarks • Runtime • Troubleshooting • Development

WARNING

thoth-mem is under active development. Core concepts, memory protocols, and integration contracts are still evolving. Expect major breaking changes before a stable release.

91.9%	6	4	0
LongMemEval-S RecallAny@5	focused MCP tools	native harnesses	model calls required

Why thoth-mem

Coding agents lose the decisions that matter between sessions: why an approach was chosen, which failure already occurred, what the next safe action is, and which evidence supports the current answer. Static instruction files help with rules, but they do not provide temporal history, scoped retrieval, or attributable provenance.

thoth-mem gives every supported harness one durable local memory without turning memory into an opaque second agent.

Design choice	What it gives you
SQLite is the source of truth	One local, inspectable ledger with rebuildable FTS5 retrieval.
Evidence before memory	Immutable supporting records remain separate from promoted conclusions.
Temporal history	Corrections and supersession preserve how project knowledge changed.
Progressive retrieval	Start compact, add context only when useful, expand selected records last.
Scoped identity	Projects and root sessions are explicit; memory does not guess ownership.
A deliberately small API	Six workflow-level MCP tools instead of a sprawling CRUD surface.

NOTE

No embedding model, vector extension, graph engine, LLM, network service, HTTP server, or dashboard is required.

Related MCP server: LumenCore

Install

Requirements: Node.js >=22.12.0 and a supported harness. Pi setup has no version allowlist or upper version limit: it checks package-manager capabilities and verifies the installed extension and resources. New Pi releases do not require a version override. The reproducible SDK test baseline is @earendil-works/pi-coding-agent 1.0.1; passing setup is not certification of every runtime behavior on future releases.

thoth-mem installs memory tooling and lifecycle integration—not agents or subagents. Add --plan --json to any managed npx setup command to preview its changes without writing.

Harness	Native integration	Install
Claude Code	Marketplace plugin, native hooks, six-tool MCP registration, and memory skill	`claude plugin marketplace add https://github.com/EremesNG/thoth-plugins.git --scope userclaude plugin install thoth-mem@thoth-plugins --scope user`Managed: `npx --yes thoth-mem@latest setup claude`
Codex CLI	Marketplace plugin, native hooks, six-tool MCP registration, and memory skill	`codex plugin marketplace add https://github.com/EremesNG/thoth-plugins.gitcodex plugin add thoth-mem@thoth-plugins`Managed: `npx --yes thoth-mem@latest setup codex`
OpenCode	Native npm plugin, lifecycle adapter, six-tool MCP surface, and memory skill	`npx --yes thoth-mem@latest setup opencode`
Pi	Native package extension, five model-facing tools, lifecycle adapter, and one package-relative six-tool MCP child	`npx --yes thoth-mem@latest setup pi`

IMPORTANT

Managed setup is global/user-native, idempotent when already current, and requests a host restart after a changed install. Project-scoped copied bundles, broad manager-cache edits, legacy fallback, and fragment migration are intentionally unsupported.

How it works

flowchart LR
  subgraph Hosts[Native harnesses]
    O[OpenCode]
    C[Codex]
    A[Claude Code]
    P[Pi]
  end

  O & C & A & P --> H[Lifecycle adapters]
  H --> S[MemoryService]
  S --> L[(Immutable SQLite ledger)]
  S --> F[(Rebuildable FTS5 index)]
  L & F --> R[Bounded progressive context]
  R --> O & C & A & P

Native adapters map each harness into the same project and root-session contract.
Evidence is immutable; session events receive a database-ordered sequence.
Observations stay outside durable memory until a verified review accepts them and an explicit promotion materializes the proposed memory.
Recall combines project isolation, temporal truth, lexical ranking, and a strict character budget.
Every harness receives the same bounded context without introducing another model into the loop.

Pi delivers recovery once as a persisted hidden message on the first root prompt after startup, resume, new, fork, or successful compaction. Reload skips delivery when the active branch already has recovery after its latest compaction. OpenCode adds a persisted synthetic text part to the first root message per plugin process (including resume) and the first after compaction. Neither host puts recovery in the system prompt or refreshes it per prompt, preserving system-prompt cache stability. If memory is unavailable, both deliver locally verified identity first and retry on later root prompts until one verified recovery block is delivered.

Automatic capture is limited to verified root prompts and checkpoint evidence, including available host compaction text. It excludes assistant reasoning, arbitrary tool traffic, delegated/subagent output, filesystem sweeps, and full transcripts. Private blocks and recognizable credentials are filtered before content-dependent keys or persistence; do not submit secrets.

IMPORTANT

thoth-mem never silently promotes an observation into durable memory. Rejection is terminal, corrections append successors, and provenance remains available through stable IDs.

Use the memory

Optional agent instructions

Optionally paste this snippet into your AGENTS.md or CLAUDE.md for proactive memory use. thoth-mem never writes it or edits those files.

## Memory (thoth-mem)
- Before exploring or planning any non-trivial task, run `mem_recall` with the task's key terms. Don't wait to be asked.
- When a decision is accepted, a root cause is verified, an approach fails, or a non-obvious convention is found, save it with `mem_save` right away.
- If a recovered handoff's pending action is done, close it: save the outcome under the same `topic_key`.
- Before ending meaningful unfinished work, save one handoff (`topic_key: handoff/<workstream>`).
- Skip memory for trivial or purely conversational turns.

Check adoption

Run thoth-mem adoption --project <exact-key-or-alias> [--json] [--data-dir <dir>] against an existing database for a read-only baseline. It never creates or migrates a database. It reports open handoffs with ages in seconds, replaced handoffs (superseded by another handoff), and closed handoffs (superseded by a non-handoff under the same topic key). Session totals include zero-save sessions and per-session counts of distinct agent explicit_save/handoff evidence IDs; automatic captures and unattributed evidence are excluded. Recall usage is not measured.

Retrieve progressively

mem_recall mode=compact
        ↓
mem_recall mode=context  or  mem_context
        ↓
mem_get only for selected stable IDs

Choose tools by intent

Intent	Tool
Save evidence or durable knowledge	`mem_save`
Find current or historical project memory	`mem_recall`
Recover a bounded project or session briefing	`mem_context`
Expand one selected record with optional predecessor history	`mem_get`
Inspect timelines, summaries, observations, or project state	`mem_project`
Record verified root lifecycle events and supported summaries	`mem_session`

The MCP server exposes exactly these six tools. Pi exposes every tool except mem_session as a native model-facing tool; mem_session is hook-owned and called only by the extension through its MCP child. OpenCode additionally exposes the read-only native thoth_mem_root_identity tool; it is session metadata, not a memory operation. Generic MCP connections attribute sessionless saves to a server-assigned connection session, not a verified native root session.

Tool text is valid JSON capped at 20,000 characters and matches structuredContent. Oversized results clip long strings, then drop trailing array items if needed, with payload_truncated first in warnings; irreducible results return output_too_large. Narrow requests when needed. Pi never slices tool text: unexpected over-cap text becomes a thoth-mem.pi.output_truncated JSON notice with narrowing guidance.

Use mem_project with action=timeline when you need to understand how promoted knowledge changed, rather than which memories best match a query.
mem_get returns the selected record once; lineage is empty unless history: true, then contains only predecessors, newest first. Evidence has no lineage; mem_project action=history still starts with the selected record.
At checkpoint_pre_compact or finalize, the core validates a submitted summary or deterministically derives or reuses one from the session's evidence, without model or network calls. Pi, Claude Code, and OpenCode also forward available host compaction text as checkpoint evidence without requiring prior pre-compaction; recognized headings yield a cited harness summary, never promoted memory.
Derived summaries omit a compaction's objective, next-action, pending, and blocker claims after a later substantive root prompt (at least 40 code points after whitespace collapse) or support for a memory-derived claim. Decisions, completed work, and changed surfaces remain eligible; persisted summaries at their activity watermark are not regenerated.
Sessions have no lifecycle state and always accept new activity. All summaries share one versioned lineage per session: a new summary supersedes the current one when its coverage end is at least the current one's; a lower end is rejected as late. Derivation reuses a current summary that already covers the latest activity.
Pi uses per-run lifecycle keys so quitting after resume derives a summary covering new activity at exit. Codex and Claude Code may replay an earlier finalize receipt on resume; lazy derivation at the next recovery covers new activity when that session is selected as the previous session. See native lifecycle for this known limitation.
Automatic recovery, including after compaction, shows the newest open handoff, then the previous session's summary, then other project memories within the existing caps. It never shows the current session's own summary; explicit session reads still can.
Observation candidates remain outside memory and FTS until a verified root review accepts them and a separate explicit promotion materializes their exact proposed memory.

LongMemEval-S

The public results use the immutable cleaned LongMemEval-S corpus and its 470 eligible non-abstention questions. The runtime remains lexical and local: no embeddings, models, or evaluation-time network calls.

Lexical strategy	RecallAny@5	Recall@5	RecallAll@5	NDCG@10	MRR	Retrieval p95	Role
`all-prefix-v1`	61/470 (13.0%)	9.8%	6.6%	0.1045	0.1287	1.1471 ms	Archived control
`any-prefix-v1`	388/470 (82.6%)	67.7%	54.0%	0.6965	0.7947	1.4437 ms	Bounded candidate
`all-then-any-prefix-v1`	446/470 (94.9%)	87.9%	78.7%	0.8538	0.8717	3.9512 ms	Broad quality reference
`strict-selected-any-cap5-rrf-v1`	419/470 (89.1%)	79.7%	68.3%	0.7700	0.8177	2.0552 ms	Archived E0 candidate
`strict-selected-any-cap5-stable-v1`	432/470 (91.9%)	84.8%	75.5%	0.8165	0.8538	9.3504 ms	Current default

RecallAny@5: questions with at least one gold session in the first five results.
Recall@5: fractional coverage across all gold sessions.
RecallAll@5: questions whose every gold session appears in the first five.
NDCG@10 / MRR: ranking quality and first-gold position.
Retrieval p95: environment-sensitive; compare latency only within the same report.

The first four rows come from the immutable Top-5 lexical comparison. The current-default row comes from the passing stable optimization round, which preserved complete ordered output while reducing p95 by 28.3% from its stable baseline. Every listed run records zero errors and zero model, LLM, or evaluation-time network calls.

The dataset is pinned to revision 98d7416c24c778c2fee6e6f3006e7a073259d48f and SHA-256 d6f21ea9d60a0d56f34a05b609c79c88a451d2ae03597821ea3d5a9678c3a442. Evaluation runs offline through the real built MemoryService, with one isolated SQLite database per question. Gold IDs and oracle data never enter indexed text or ranking.

Protocol sources: LongMemEval repository, official cleaned dataset, and pinned dataset revision.

Runtime data and migration

All harnesses resolve one data directory in this order: an explicit command value, THOTH_MEM_DATA_DIR, strict provider configuration, then ~/.thoth-mem. The database is always memory.sqlite inside the selected directory.

Git repositories keep a stable project ID in the shared Git common directory: worktrees share memory, while independent clones remain separate. Folder renames do not change the display name; use thoth-mem project rename --project <exact-key-or-alias> --name <display-name> [--data-dir <dir>] to change it explicitly.

The provider file lives below XDG_CONFIG_HOME/thoth-mem/config.json when XDG configuration is set, or below ~/.config/thoth-mem/config.json otherwise. Malformed, unreadable, schema-invalid, or missing-runtime configuration fails closed.

Hosts automatically migrate supported older schemas to revision 12 at startup; thoth-mem migrate completes pending migrations manually and reports the changes. On large databases, backups and migration can exceed host timeouts; use that manual path instead. Revision 12 creates or verifies memory.sqlite.pre-v12.bak, rechecks the revision and live source under an immediate write-excluding lock, removes session state and end-time columns, and merges existing summaries into one version lineage per session while keeping IDs. Integrity and foreign-key checks must pass; a mismatched backup or source drift fails closed before mutation.

Older databases first apply the revision-10 Pi harness migration (memory.sqlite.pre-v10.bak) and revision-11 empty-session cleanup (memory.sqlite.pre-v11.bak) as needed. That cleanup removes only unreferenced non-import host sessions and their lifecycle receipts that cite neither evidence nor a summary; all other sessions, receipts, evidence, and memories are preserved.

Stop every process that may hold the target database, then import the conventional ~/.thoth/thoth.db:

thoth-mem import-legacy

For a nonstandard source or explicit mapping:

thoth-mem import-legacy --source ./legacy.sqlite --map ./mapping.json --data-dir ./current-memory
thoth-mem import-legacy --json

For a reviewable two-step workflow, write a plan, inspect it, then apply it:

thoth-mem import-legacy plan --source ./legacy.sqlite --target ./current-memory/memory.sqlite --plan ./import-plan.json
thoth-mem import-legacy apply --plan ./import-plan.json --report ./import-report.json

Add --map ./mapping.json to plan for explicit mapping. apply uses the target recorded in the plan; existing plan and report output files are refused.

The importer fingerprints its inputs, creates a verified backup and isolated candidate when needed, and publishes only after integrity checks pass. Keep the legacy database, verified backup, and recovery bundle until the migrated runtime has been independently validated.

Troubleshooting

If memory stays unavailable after an upgrade, look for these host diagnostics:

Pi: thoth-mem degraded: pi_mcp_startup_timeout — the memory server did not start in time; if memory stays unavailable, run `thoth-mem migrate` (at most once per session). Other failures retain codes such as pi_lifecycle_request_failed.
OpenCode logs: OpenCode lifecycle degraded: node_lifecycle_timeout — memory did not respond in time; if memory stays unavailable, run `thoth-mem migrate` (once per plugin session), or OpenCode lifecycle degraded: node_lifecycle_nonzero_exit — <bounded stderr tail>.
Codex / Claude Code hook stderr: thoth-mem public plugin: Lifecycle failed: SQLite migration revision A→B failed: …, including the observed failure and the thoth-mem migrate recommendation.

A timeout alone does not prove a migration is pending. To complete any pending migrations outside host time limits, run:

npx --yes thoth-mem@latest migrate

With an installed command, use thoth-mem migrate; with a package checkout, use node <package>/dist/index.js migrate. Add --data-dir <dir> to select the directory containing your existing memory.sqlite; otherwise the runtime data selection above applies. A missing database is an error, not a new database.

Output such as Migration: 11 → 12 shows the revision change; Backup created: or Backup verified: names the retained backup. Sessions removed: and Lifecycle receipts removed: count only the empty-session cleanup, not evidence or memories; Duration: is elapsed milliseconds. Add --json for the thoth-mem.migrate.v1 envelope with revisions, backups, removal counts, durationMs, and alreadyCurrent. It is safe to rerun: an already-current database reports a no-op (alreadyCurrent: true) without changing the source database or its sidecars.

Keep memory.sqlite.pre-vN.bak backups until recovery is verified. To restore one, first stop all hosts and thoth-mem processes, move the current memory.sqlite and any memory.sqlite-wal / memory.sqlite-shm files aside, then copy the chosen backup to memory.sqlite. Restoring loses changes made after that backup; an older schema will migrate again on the next writable open. Prefer a clean host exit (in Pi, /quit) over killing its terminal.

Killed processes may leave memory.sqlite.pre-vN.bak.<pid>.<uuid>.tmp files. They are unpublished backup candidates, not retained backups; delete them only when no thoth-mem process is running.

Development

Clone, build, local host wiring, verification, benchmark reproduction, and repository layout live in the development guide.

Task-specific engineering, persistence, privacy, lifecycle, and testing guidance starts at the agent context index.

Available Tools

6 tools

mem_contextC

Build bounded handoff-first continuity. project_key required; root_session_key and harness together for session context, neither for project context.

Name	Required	Description
`harness`	No	Verified native harness.
`project_key`	Yes	Verified project_key, copied verbatim; never derived.
`budget_chars`	No
`correlation_id`	No
`finalize_answer`	No
`root_session_key`	No	Verified root session key.

TDQS

C2.8/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description bears the full burden. It implies a build/continuity operation but does not state whether it writes data, what side effects or permissions exist, whether it is idempotent, or what the result contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact sentences with no filler, and the required-parameter guidance is front-loaded. The only weakness is that the opening sentence is so terse and jargon-heavy that it obscures meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a six-parameter tool with no annotations and no output schema, the description is too thin. It explains the session/project context split but omits behavioral details, output expectations, and several parameter meanings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds important conditional semantics for project_key, root_session_key, and harness, including the session-vs-project mode distinction. However, with only 50% schema description coverage, it leaves budget_chars, correlation_id, and finalize_answer unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description says it builds 'bounded handoff-first continuity,' which gestures at context creation but is vague jargon rather than a clear verb+resource statement. It also does not distinguish this tool from siblings such as mem_recall, mem_session, or mem_project.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It specifies project_key is required and explains that root_session_key plus harness together select session context while neither selects project context. That is useful conditional guidance, but it gives no explicit when-to-use-this-tool-vs-alternatives guidance or exclusions relative to sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

mem_getB

Expand one selected record from a prior tool result.

Name	Required	Description
`id`	Yes	Memory, summary, observation, or evidence id.
`history`	No	Include predecessors; evidence has none.
`correlation_id`	No

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not state that this is a read-only retrieval, does not explain what expansion returns, does not mention the optional history behavior, and gives no permission or side-effect context. The word 'expand' hints at non-destructive retrieval but that is the only signal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single focused sentence with no wasted words, front-loading the core action. It is perhaps too terse for the gaps it leaves, but structurally it is efficient and readable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no annotations and no output schema, the description is the only source of behavioral context, and it says nothing about return shape, history semantics, or the undocumented correlation_id. For a retrieval tool that may return variable content, this leaves the agent without enough to call it confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%: the schema documents 'id' and 'history' with useful detail, while 'correlation_id' is undocumented. The description's only contribution is that 'id' refers to a record from a prior tool result, which adds marginal context beyond the schema. Baseline 3 fits given the partial coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'expand' plus the object 'one selected record from a prior tool result' makes the purpose reasonably clear: fetch the full detail of a single record referenced by a previous result. It does not differentiate itself from the sibling mem_recall, so an agent cannot tell from the text alone which retrieval tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'from a prior tool result' implies the context of use — after another tool has returned a record stub — which gives some usage guidance. However, it never states when to use this vs. mem_recall or mem_context, and offers no exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

mem_projectC

Read-only project views. list: no fields required; returns at most 256 exact aliases/project with aliasCount/aliasesTruncated. timeline: project_key required; accepts only since, until, cursor, limit, budget_chars. briefing/summaries/observations: project_key required; optional session filter selects summaries/observations, not briefing's project-wide memories. history: id required from a prior result.

Name	Required	Description
`id`	No
`limit`	No	Timeline/observations: 1-100 items.
`since`	No	Inclusive lower ISO-8601 instant; <= until.
`state`	No
`until`	No	Inclusive upper ISO-8601 instant.
`action`	Yes
`cursor`	No	Unchanged nextCursor; preserve project_key, since, until.
`harness`	No
`temporal`	No	Summaries/observations: current=latest summaries/correction leaves; history=predecessors.
`project_key`	No	Verified project_key, copied verbatim; never derived.
`budget_chars`	No	Aggregate chars; timeline: positive integer clamped to 1024-20000.
`root_session_key`	No	Session filter; pair with harness.

TDQS

C2.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are present, so the description carries the full burden. It does disclose read-only behavior and several useful constraints: list returns at most 256 aliases with aliasCount/aliasesTruncated, timeline accepts only a specific set of filters, and a session filter affects summaries/observations but not briefing. However, permissions, return shapes for most actions, and error behavior are not described.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the read-only nature. It is dense and semicolon-delimited, making it harder to scan than a bulleted structure, but every clause conveys actionable information with little waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has six actions and twelve parameters with no output schema, yet the description explains return values only for list. It does not explain when to use briefing versus summaries or observations, what those actions return, or how temporal/state/harness parameters affect behavior. Significant gaps remain for an agent to invoke the tool correctly across all actions.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, so the schema already documents many parameters. The description adds action-specific constraints not obvious from the schema: timeline accepts only since/until/cursor/limit/budget_chars, list requires no fields and returns a capped alias set, history id must come from a prior result, and the session filter behavior varies by action. It leaves state, harness, temporal, and root_session_key semantics largely unaddressed beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

Starts with 'Read-only project views,' which is a vague resource description, then lists action names and parameter requirements. The action list gives some clarity about what the tool can do, but the overall purpose ('project views') is not concretely defined and the tool is not distinguished from siblings like mem_context or mem_recall.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides per-action parameter requirements (e.g., timeline requires project_key and accepts only certain filters), but gives no guidance on when to use this tool versus alternatives or which action to choose for a given intent. There are no exclusions or alternative-tool references.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

mem_recallB

Call at the start of non-trivial repository work before exploring, with task key terms, unprompted. Search promoted project memory before expanding selected records.

Name	Required	Description
`mode`	No	compact (default): snippets; context: selected content.
`limit`	No
`query`	Yes	Non-empty task search terms.
`temporal`	No	current (default) or historical guidance.
`project_key`	Yes	Verified project_key, copied verbatim; never derived.
`budget_chars`	No
`correlation_id`	No
`finalize_answer`	No

TDQS

B3.3/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden; it does disclose a two-stage retrieval workflow (search snippets, then expand selected records) and that results are pre-promoted memory. However, it says nothing about what finalize_answer, correlation_id, or budget_chars do, what the response looks like, or whether the operation has any side effects. Useful workflow context, but not enough for an 8-parameter tool without annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with the imperative and timing front-loaded; nothing is filler. The phrase 'with task key terms, unprompted' is slightly awkward but still parses as useful guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 8 parameters, no annotations, and no output schema, the description covers purpose and timing but omits the semantics of most parameters and the shape of results. An agent would need to open the schema and still lack clarity on finalize_answer and correlation_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

At 50% schema coverage, the description must compensate, and it only hints at 'query' ('with task key terms') and implicitly at mode via 'expanding selected records'. The remaining parameters (project_key, limit, temporal, budget_chars, correlation_id, finalize_answer) get no explanation in the description beyond the schema's own text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific action (search promoted project memory) and adds scope ('promoted', 'project memory') that is more than a restatement of the tool name. It doesn't explicitly contrast with siblings like mem_context or mem_get, leaving the agent to infer the boundary.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives a clear trigger ('at the start of non-trivial repository work, before exploring') and says to call it unprompted, plus a follow-up step ('before expanding selected records'). It stops short of naming which sibling to use instead when the task isn't repository work.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

mem_saveA

Save unprompted as soon as decisions, root causes, failed approaches, or non-obvious conventions are verified. Save durable discoveries and continuation handoffs. Direct promoted memory (not handoff): memory.content uses labeled Result, Rationale, Scope, Caveat / safe action lines; omit inapplicable Scope/Caveat and never invent details. Handoffs: Objective, Completed, First pending action, Blockers, Key files/checks; require a stable workstream topic_key; close a finished handoff by saving its outcome under the same topic_key. Send exactly one branch: evidence, observation, observation_review, or observation_promotion. Supply root_session_key and harness together or omit both.

Name	Required	Description
`memory`	No	Direct promoted memory; requires evidence without metadata.
`harness`	No	Verified native harness.
`evidence`	No	Compact factual evidence; metadata requires event_key + session pair and forbids memory.
`event_key`	No	Stable idempotency key.
`observation`	No	Supported candidate, not promoted; requires event_key. Session scope needs session pair + coverage; project scope forbids coverage.
`project_key`	Yes	Copy opaque project_key verbatim from verified native identity; never derive from names, paths, remotes, branches, worktrees, host IDs, listings, or recalled content.
`project_name`	Yes	Display/creation name, not identity; prefer persisted lifecycle/project name.
`root_session_key`	No	Verified root session key; blank is absent.
`observation_review`	No	Review supported observation; requires event_key + session pair.
`observation_promotion`	No	Promote accepted observation without new prose; requires event_key + session pair.

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden well: it discloses branch mutual exclusivity, the root_session_key/harness all-or-nothing pairing constraint, and the requirement of a stable topic_key to close a handoff. It does not say what happens on supersede/dedup or what the call returns, leaving those gaps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the trigger condition, and every clause carries a rule rather than filler. Density is high and semicolon-chained, with terse terms like 'safe action lines' that take re-reading, but nothing is expendable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 10-parameter, deeply nested write tool with no annotations and no output schema, the description covers branch selection and the session-pair constraint but omits return behavior, supersede semantics, and how the four branches relate to each other downstream. Adequate to make a correct call, not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning the schema cannot express: the labeled Result/Rationale/Scope/Caveat shape of memory.content and the Objective/Completed/First pending action/Blockers structure of a handoff. It leaves supersedes_id, outcome, and the memory-vs-evidence relationship to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The imperative verb 'Save' plus enumerated resource types (decisions, root causes, failed approaches, conventions, handoffs) makes clear this tool persists memory. It does not explicitly contrast itself with the read-oriented siblings (mem_get, mem_recall, mem_context), but the write framing is unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Strong trigger guidance: 'Save unprompted as soon as... verified', plus durable discoveries and continuation handoffs. It also gives branch-selection rules ('Send exactly one branch'). It never names a sibling tool as an alternative or states a when-not-to-save condition, which keeps it off a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

mem_sessionB

Record verified root lifecycle events, never ordinary saves. guide_post_compact content carries host compaction text.

Name	Required	Description
`content`	No
`harness`	Yes	Verified native harness.
`summary`	No	Session summary.
`event_key`	Yes	Stable lifecycle key; retries must resend identical content/summary.
`operation`	Yes	Root lifecycle operation.
`project_key`	Yes	Verified project_key, copied verbatim; never derived.
`project_name`	Yes	Display/creation name, not identity; prefer persisted lifecycle/project name.
`root_session_key`	Yes	Stable verified root session key.

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden, but it only says these are lifecycle events and that guide_post_compact content carries host compaction text. It does not disclose mutation semantics, idempotency expectations, permission/auth requirements, or what happens for each lifecycle operation beyond what the schema implies.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences, front-loads the core action, and contains no filler. It is efficient, though its brevity contributes to gaps elsewhere rather than being a structural flaw itself.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a complex tool with eight parameters, nested summary objects, six lifecycle operations, and no annotations or output schema. The description does not explain the lifecycle operations, what is recorded or changed, retry behavior, or the relationship between required fields, leaving too much for the agent to infer.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is high at 88%, so the schema already documents most parameters. The description adds one valuable clarification: content for guide_post_compact carries host compaction text, but it does not add meaning for the other parameters or nested summary fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: 'Record verified root lifecycle events,' and explicitly distinguishes this from 'ordinary saves,' which helps separate it from mem_save. It is less clear about what a root lifecycle event is, but the operation enum and sibling contrast keep the purpose identifiable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives one useful exclusion, 'never ordinary saves,' which points agents away from mem_save for normal persistence. However, it does not explain when to use enroll, recover, capture_root, checkpoint_pre_compact, guide_post_compact, or finalize, so operation selection remains implied by the schema rather than guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

6 tool updatesv0.6.2Oct 25, 2026

Changedmem_context2 fields changed
- removedInput schema / properties / project_key / minLength
```
Removed value: -1
```
- removedInput schema / properties / root_session_key / minLength
```
Removed value: -1
```

Changedmem_get1 field changed

changedInput schema / properties / history / description

Previous value: -"true: include predecessor lineage; evidence has no lineage."New value: +"Include predecessors; evidence has none."

Changedmem_project20 fields changed

removedInput schema / properties / action / description
```
Removed value: -"Project view."
```

changedInput schema / properties / budget_chars / description

Previous value: -"Aggregate character budget for timeline/briefing/summaries/observations; timeline clamps positive integers to 1024-20000."New value: +"Aggregate chars; timeline: positive integer clamped to 1024-20000."

changedInput schema / properties / cursor / description

Previous value: -"Timeline nextCursor, unchanged; keep project_key, since, until unchanged."New value: +"Unchanged nextCursor; preserve project_key, since, until."

removedInput schema / properties / cursor / maxLength
```
Removed value: -4096
```
removedInput schema / properties / cursor / minLength
```
Removed value: -1
```
removedInput schema / properties / harness / description
```
Removed value: -"Native harness for session filter."
```
removedInput schema / properties / id / description
```
Removed value: -"Prior-result record id."
```
removedInput schema / properties / id / minLength
```
Removed value: -1
```

changedInput schema / properties / limit / description

Previous value: -"Maximum items for timeline/observations."New value: +"Timeline/observations: 1-100 items."

removedInput schema / properties / limit / exclusiveMinimum
```
Removed value: -0
```
removedInput schema / properties / limit / maximum
```
Removed value: -100
```
removedInput schema / properties / project_key / minLength
```
Removed value: -1
```

changedInput schema / properties / root_session_key / description

Previous value: -"Verified session filter; pair with harness or omit both."New value: +"Session filter; pair with harness."

removedInput schema / properties / root_session_key / minLength
```
Removed value: -1
```

changedInput schema / properties / since / description

Previous value: -"Timeline inclusive lower ISO-8601 instant; <= until."New value: +"Inclusive lower ISO-8601 instant; <= until."

removedInput schema / properties / since / minLength
```
Removed value: -1
```
removedInput schema / properties / state / description
```
Removed value: -"Observations state filter."
```

changedInput schema / properties / temporal / description

Previous value: -"Summaries/observations only: current=latest summaries/correction leaves; history=older summaries/observation predecessors."New value: +"Summaries/observations: current=latest summaries/correction leaves; history=predecessors."

changedInput schema / properties / until / description

Previous value: -"Timeline inclusive upper ISO-8601 instant."New value: +"Inclusive upper ISO-8601 instant."

removedInput schema / properties / until / minLength
```
Removed value: -1
```

Changedmem_recall4 fields changed

changedInput schema / properties / mode / description

Previous value: -"compact (default): bounded snippets; context: selected content."New value: +"compact (default): snippets; context: selected content."

removedInput schema / properties / project_key / minLength
```
Removed value: -1
```
removedInput schema / properties / query / minLength
```
Removed value: -1
```

changedInput schema / properties / temporal / description

Previous value: -"current (default): current guidance; history: historical records."New value: +"current (default) or historical guidance."

Changedmem_save58 fields changed

removedInput schema / properties / evidence / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "content": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "kind": {
-        "enum": [
-          "root_prompt",
-          "explicit_save",
-          "checkpoint",
-          "handoff",
-          "legacy_prompt",
-          "legacy_observation",
-          "session_summary"
-        ],
-        "type": "string"
-      },
-      "source_ref": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "content"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "content": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "kind": {
-        "const": "explicit_save",
-        "type": "string"
-      },
-      "metadata": {
-        "additionalProperties": false,
-        "properties": {
-          "observation_validation": {
-            "additionalProperties": false,
-            "properties": {
-              "method": {
-                "maxLength": 500,
-                "minLength": 1,
-                "type": "string"
-              },
-              "observation_id": {
-                "maxLength": 200,
-                "minLength": 1,
-                "type": "string"
-              },
-              "result": {
-                "enum": [
-                  "passed",
-                  "failed"
-                ],
-                "type": "string"
-              }
-            },
-            "required": [
-              "observation_id",
-              "result",
-              "method"
-            ],
-            "type": "object"
-          }
-        },
-        "required": [
-          "observation_validation"
-        ],
-        "type": "object"
-      },
-      "source_ref": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "content",
-      "metadata"
-    ],
-    "type": "object"
-  },
-  {
-    "additionalProperties": false,
-    "properties": {
-      "content": {
-        "minLength": 1,
-        "type": "string"
-      },
-      "kind": {
-        "const": "handoff",
-        "type": "string"
-      },
-      "metadata": {
-        "additionalProperties": false,
-        "properties": {
-          "observation_review_attestation": {
-            "additionalProperties": false,
-            "properties": {
-              "method": {
-                "maxLength": 500,
-                "minLength": 1,
-                "type": "string"
-              },
-              "observation_id": {
-                "maxLength": 200,
-                "minLength": 1,
-                "type": "string"
-              },
-              "reviewer": {
-                "maxLength": 200,
-                "minLength": 1,
-                "type": "string"
-              },
-              "verdict": {
-                "enum": [
-                  "accepted",
-                  "rejected"
-                ],
-                "type": "string"
-              }
-            },
-            "required": [
-              "observation_id",
-              "verdict",
-              "reviewer",
-              "method"
-            ],
-            "type": "object"
-          }
-        },
-        "required": [
-          "observation_review_attestation"
-        ],
-        "type": "object"
-      },
-      "source_ref": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "kind",
-      "content",
-      "metadata"
-    ],
-    "type": "object"
-  }
-]

addedInput schema / properties / evidence / properties

Added value: +{
+  "content": {
+    "type": "string"
+  },
+  "kind": {
+    "enum": [
+      "root_prompt",
+      "explicit_save",
+      "checkpoint",
+      "handoff",
+      "legacy_prompt",
+      "legacy_observation",
+      "session_summary"
+    ],
+    "type": "string"
+  },
+  "metadata": {
+    "properties": {
+      "observation_review_attestation": {
+        "properties": {
+          "method": {
+            "type": "string"
+          },
+          "observation_id": {
+            "type": "string"
+          },
+          "reviewer": {
+            "type": "string"
+          },
+          "verdict": {
+            "enum": [
+              "accepted",
+              "rejected"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "observation_id",
+          "verdict",
+          "reviewer",
+          "method"
+        ],
+        "type": "object"
+      },
+      "observation_validation": {
+        "properties": {
+          "method": {
+            "type": "string"
+          },
+          "observation_id": {
+            "type": "string"
+          },
+          "result": {
+            "enum": [
+              "passed",
+              "failed"
+            ],
+            "type": "string"
+          }
+        },
+        "required": [
+          "observation_id",
+          "result",
+          "method"
+        ],
+        "type": "object"
+      }
+    },
+    "type": "object"
+  },
+  "source_ref": {
+    "type": "string"
+  }
+}

addedInput schema / properties / evidence / required
```
Added value: +[
+  "kind",
+  "content"
+]
```
addedInput schema / properties / evidence / type
```
Added value: +"object"
```
removedInput schema / properties / memory / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / memory / properties / content / minLength
```
Removed value: -1
```
removedInput schema / properties / memory / properties / title / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / observation / properties / claim / maxLength
```
Removed value: -4000
```
removedInput schema / properties / observation / properties / claim / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / properties / concepts / items / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation / properties / concepts / items / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / properties / concepts / maxItems
```
Removed value: -16
```
removedInput schema / properties / observation / properties / coverage / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / observation / properties / coverage / properties / from_sequence / exclusiveMinimum
```
Removed value: -0
```
removedInput schema / properties / observation / properties / coverage / properties / from_sequence / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / observation / properties / coverage / properties / to_sequence / exclusiveMinimum
```
Removed value: -0
```
removedInput schema / properties / observation / properties / coverage / properties / to_sequence / maximum
```
Removed value: -9007199254740991
```
removedInput schema / properties / observation / properties / files / items / maxLength
```
Removed value: -500
```
removedInput schema / properties / observation / properties / files / items / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / properties / files / maxItems
```
Removed value: -16
```
removedInput schema / properties / observation / properties / generator / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / observation / properties / generator / properties / config_hash / pattern
```
Removed value: -"^[0-9a-f]{64}$"
```
removedInput schema / properties / observation / properties / generator / properties / name / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation / properties / generator / properties / name / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / properties / generator / properties / version / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation / properties / generator / properties / version / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / properties / predecessor_id / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation / properties / predecessor_id / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / properties / proposed_memory / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / observation / properties / proposed_memory / properties / content / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / properties / proposed_memory / properties / title / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / properties / support_ids / items / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation / properties / support_ids / items / minLength
```
Removed value: -1
```
removedInput schema / properties / observation / properties / support_ids / maxItems
```
Removed value: -16
```
removedInput schema / properties / observation / properties / support_ids / minItems
```
Removed value: -1
```
removedInput schema / properties / observation / properties / title / maxLength
```
Removed value: -500
```
removedInput schema / properties / observation / properties / title / minLength
```
Removed value: -1
```
removedInput schema / properties / observation_promotion / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / observation_promotion / properties / observation_id / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation_promotion / properties / observation_id / minLength
```
Removed value: -1
```
removedInput schema / properties / observation_review / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / observation_review / properties / observation_id / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation_review / properties / observation_id / minLength
```
Removed value: -1
```
removedInput schema / properties / observation_review / properties / policy / additionalProperties
```
Removed value: -false
```
removedInput schema / properties / observation_review / properties / policy / properties / id / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation_review / properties / policy / properties / id / minLength
```
Removed value: -1
```
removedInput schema / properties / observation_review / properties / policy / properties / version / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation_review / properties / policy / properties / version / minLength
```
Removed value: -1
```
removedInput schema / properties / observation_review / properties / reason / maxLength
```
Removed value: -1000
```
removedInput schema / properties / observation_review / properties / reason / minLength
```
Removed value: -1
```
removedInput schema / properties / observation_review / properties / support_ids / items / maxLength
```
Removed value: -200
```
removedInput schema / properties / observation_review / properties / support_ids / items / minLength
```
Removed value: -1
```
removedInput schema / properties / observation_review / properties / support_ids / maxItems
```
Removed value: -16
```
removedInput schema / properties / observation_review / properties / support_ids / minItems
```
Removed value: -1
```
removedInput schema / properties / project_key / minLength
```
Removed value: -1
```

changedInput schema / properties / project_name / description

Previous value: -"Display/creation metadata only, not identity; prefer the persisted name from lifecycle/project output."New value: +"Display/creation name, not identity; prefer persisted lifecycle/project name."

removedInput schema / properties / project_name / minLength
```
Removed value: -1
```

Changedmem_session27 fields changed
- removedInput schema / properties / event_key / minLength
```
Removed value: -1
```
- removedInput schema / properties / project_key / minLength
```
Removed value: -1
```
- changedInput schema / properties / project_name / description
```
Previous value: -"Display/creation metadata only, not identity; prefer the persisted name from lifecycle/project output."New value: +"Display/creation name, not identity; prefer persisted lifecycle/project name."
```
- removedInput schema / properties / project_name / minLength
```
Removed value: -1
```
- removedInput schema / properties / root_session_key / minLength
```
Removed value: -1
```
- removedInput schema / properties / summary / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / summary / properties / claims / items / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / summary / properties / claims / items / properties / content / minLength
```
Removed value: -1
```
- changedInput schema / properties / summary / properties / claims / items / properties / support_ids / description
```
Previous value: -"Distinct evidence ids inside coverage from this project_key + root_session_key/harness session; never memory, summary, or observation ids."New value: +"Distinct same-session evidence ids within coverage; no memory/summary/observation ids."
```
- removedInput schema / properties / summary / properties / claims / items / properties / support_ids / items / maxLength
```
Removed value: -200
```
- removedInput schema / properties / summary / properties / claims / items / properties / support_ids / items / minLength
```
Removed value: -1
```
- removedInput schema / properties / summary / properties / claims / items / properties / support_ids / maxItems
```
Removed value: -16
```
- removedInput schema / properties / summary / properties / claims / items / properties / support_ids / minItems
```
Removed value: -1
```
- removedInput schema / properties / summary / properties / claims / maxItems
```
Removed value: -32
```
- removedInput schema / properties / summary / properties / claims / minItems
```
Removed value: -1
```
- removedInput schema / properties / summary / properties / coverage / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / summary / properties / coverage / properties / from_sequence / exclusiveMinimum
```
Removed value: -0
```
- removedInput schema / properties / summary / properties / coverage / properties / from_sequence / maximum
```
Removed value: -9007199254740991
```
- changedInput schema / properties / summary / properties / coverage / properties / to_sequence / description
```
Previous value: -"Last sequence: >= from_sequence and >= the current summary's ending sequence for this session."New value: +">= from_sequence and the previous summary end."
```
- removedInput schema / properties / summary / properties / coverage / properties / to_sequence / exclusiveMinimum
```
Removed value: -0
```
- removedInput schema / properties / summary / properties / coverage / properties / to_sequence / maximum
```
Removed value: -9007199254740991
```
- removedInput schema / properties / summary / properties / generator / additionalProperties
```
Removed value: -false
```
- removedInput schema / properties / summary / properties / generator / properties / config_hash / pattern
```
Removed value: -"^[0-9a-f]{64}$"
```
- removedInput schema / properties / summary / properties / generator / properties / name / maxLength
```
Removed value: -200
```
- removedInput schema / properties / summary / properties / generator / properties / name / minLength
```
Removed value: -1
```
- removedInput schema / properties / summary / properties / generator / properties / version / maxLength
```
Removed value: -200
```
- removedInput schema / properties / summary / properties / generator / properties / version / minLength
```
Removed value: -1
```

6 tool updatesv0.6.1Oct 21, 2026

Changedmem_context3 fields changed

changedInput schema / properties / harness / description

Previous value: -"Native harness for root_session_key; supply both for session context, or omit both for project context."New value: +"Verified native harness."

changedInput schema / properties / project_key / description

Previous value: -"Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content."New value: +"Verified project_key, copied verbatim; never derived."

changedInput schema / properties / root_session_key / description

Previous value: -"Optional verified root session key; supply with harness for session context, or omit both for project context."New value: +"Verified root session key."

Changedmem_get2 fields changed

changedInput schema / properties / history / description

Previous value: -"Set true to expand predecessor lineage for memory, summary, or observation records; evidence ids have no lineage."New value: +"true: include predecessor lineage; evidence has no lineage."

changedInput schema / properties / id / description

Previous value: -"Memory, summary, observation, or evidence id returned by a prior tool result."New value: +"Memory, summary, observation, or evidence id."

Changedmem_project12 fields changed

changedInput schema / properties / action / description

Previous value: -"Inspect project views without mutation. action=\"list\": no fields required. action=\"timeline\": project_key required; optionally since, until, cursor, limit, and budget_chars. action=\"briefing\", \"summaries\", or \"observations\": project_key required; optionally supply both root_session_key and harness to select that session's summaries/observations (briefing still includes project-wide memories). action=\"history\": id required from a prior result. temporal filters summaries/observations, not timeline. list returns at most 256 exact aliases per project plus aliasCount and aliasesTruncated metadata."New value: +"Project view."

changedInput schema / properties / budget_chars / description

Previous value: -"Optional aggregate character budget for timeline, briefing, summaries, or observations; timeline clamps a positive integer to 1024-20000 characters."New value: +"Aggregate character budget for timeline/briefing/summaries/observations; timeline clamps positive integers to 1024-20000."

changedInput schema / properties / cursor / description

Previous value: -"Unchanged nextCursor from a prior mem_project action=\"timeline\" result; keep project_key, since, and until unchanged."New value: +"Timeline nextCursor, unchanged; keep project_key, since, until unchanged."

changedInput schema / properties / harness / description

Previous value: -"Native harness for the optional root_session_key filter; supply both or omit both. Not accepted for action=\"timeline\"."New value: +"Native harness for session filter."

changedInput schema / properties / id / description

Previous value: -"Required for action=\"history\"; send a record id returned by a prior tool result."New value: +"Prior-result record id."

changedInput schema / properties / limit / description

Previous value: -"Maximum items (1-100) for action=\"timeline\" or \"observations\"."New value: +"Maximum items for timeline/observations."

changedInput schema / properties / project_key / description

Previous value: -"Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content. Required for action=\"timeline\", \"briefing\", \"summaries\", or \"observations\"; not required for \"list\" or \"history\"."New value: +"Verified project_key, copied verbatim; never derived."

changedInput schema / properties / root_session_key / description

Previous value: -"Optional session filter for action=\"briefing\", \"summaries\", or \"observations\"; supply with harness or omit both."New value: +"Verified session filter; pair with harness or omit both."

changedInput schema / properties / since / description

Previous value: -"Optional inclusive lower ISO-8601 instant for action=\"timeline\" only; must be <= until."New value: +"Timeline inclusive lower ISO-8601 instant; <= until."

changedInput schema / properties / state / description

Previous value: -"Optional state filter for action=\"observations\"."New value: +"Observations state filter."

changedInput schema / properties / temporal / description

Previous value: -"Filter summaries/observations: current selects current summary versions or observation correction-chain leaves; history includes older summary versions or selects observation predecessors. Not accepted for action=\"timeline\"."New value: +"Summaries/observations only: current=latest summaries/correction leaves; history=older summaries/observation predecessors."

changedInput schema / properties / until / description

Previous value: -"Optional inclusive upper ISO-8601 instant for action=\"timeline\" only; must be >= since."New value: +"Timeline inclusive upper ISO-8601 instant."

Changedmem_recall4 fields changed

changedInput schema / properties / mode / description

Previous value: -"compact (default) returns bounded snippets; context adds selected memory content."New value: +"compact (default): bounded snippets; context: selected content."

changedInput schema / properties / project_key / description

Previous value: -"Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content."New value: +"Verified project_key, copied verbatim; never derived."

changedInput schema / properties / query / description

Previous value: -"Non-empty search string for promoted project memory."New value: +"Non-empty task search terms."

changedInput schema / properties / temporal / description

Previous value: -"current (default) searches current guidance; history includes historical records."New value: +"current (default): current guidance; history: historical records."

Changedmem_save10 fields changed

changedInput schema / properties / event_key / description

Previous value: -"Stable event key for idempotency; required for observation, observation_review, observation_promotion, and evidence with metadata."New value: +"Stable idempotency key."

changedInput schema / properties / evidence / description

Previous value: -"Direct evidence { kind, content }; optionally add memory for a promoted save. Structured metadata forbids memory and requires event_key, root_session_key, and harness."New value: +"Compact factual evidence; metadata requires event_key + session pair and forbids memory."

changedInput schema / properties / harness / description

Previous value: -"Native harness for root_session_key; supply both or omit both. Required wherever root_session_key is required."New value: +"Verified native harness."

changedInput schema / properties / memory / description

Previous value: -"Promoted memory for direct evidence only; requires evidence without metadata. Do not combine with observation, observation_review, or observation_promotion."New value: +"Direct promoted memory; requires evidence without metadata."

changedInput schema / properties / observation / description

Previous value: -"Submit a supported candidate without promotion; requires event_key. Session scope also requires root_session_key, harness, and coverage."New value: +"Supported candidate, not promoted; requires event_key. Session scope needs session pair + coverage; project scope forbids coverage."

changedInput schema / properties / observation_promotion / description

Previous value: -"Promote one accepted observation without new prose; requires event_key, root_session_key, and harness. Send no other operation branch or memory."New value: +"Promote accepted observation without new prose; requires event_key + session pair."

changedInput schema / properties / observation_review / description

Previous value: -"Review one supported observation; requires event_key, root_session_key, and harness. Send no other operation branch or memory."New value: +"Review supported observation; requires event_key + session pair."

changedInput schema / properties / project_key / description

Previous value: -"Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content."New value: +"Copy opaque project_key verbatim from verified native identity; never derive from names, paths, remotes, branches, worktrees, host IDs, listings, or recalled content."

changedInput schema / properties / project_name / description

Previous value: -"Creation/display metadata only; never participates in project identity equality. Prefer the database-persisted name returned by lifecycle or project output."New value: +"Display/creation metadata only, not identity; prefer the persisted name from lifecycle/project output."

changedInput schema / properties / root_session_key / description

Previous value: -"Verified root session key; supply with harness or omit both. Required for session-scoped observations, observation_review, observation_promotion, and evidence with metadata; blank counts as absent."New value: +"Verified root session key; blank is absent."

Changedmem_session15 fields changed

changedInput schema / properties / event_key / description

Previous value: -"Stable lifecycle event key; retries for the same operation must resend identical content/summary."New value: +"Stable lifecycle key; retries must resend identical content/summary."

changedInput schema / properties / harness / description

Previous value: -"Verified native harness for root_session_key in project_key."New value: +"Verified native harness."

changedInput schema / properties / operation / description

Previous value: -"Lifecycle operation; summary is allowed only for checkpoint_pre_compact (checkpoint) or finalize (final)."New value: +"Root lifecycle operation."

changedInput schema / properties / project_key / description

Previous value: -"Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content."New value: +"Verified project_key, copied verbatim; never derived."

changedInput schema / properties / project_name / description

Previous value: -"Creation/display metadata only; never participates in project identity equality. Prefer the database-persisted name returned by lifecycle or project output."New value: +"Display/creation metadata only, not identity; prefer the persisted name from lifecycle/project output."

changedInput schema / properties / root_session_key / description

Previous value: -"Stable verified root session key; required with harness for every operation."New value: +"Stable verified root session key."

changedInput schema / properties / summary / description

Previous value: -"Optional only for operation=\"checkpoint_pre_compact\" (kind=\"checkpoint\") or operation=\"finalize\" (kind=\"final\"). coverage starts at 1 and to_sequence must advance the current summary for this session and kind. support_ids must be evidence ids from this project_key + root_session_key/harness session inside coverage. Canonical submission limit: 20000 UTF-16 units."New value: +"Session summary."

changedInput schema / properties / summary / properties / claims / description

Previous value: -"1-32 atomic supported claims; keep the canonical summary within 20000 UTF-16 units."New value: +"Supported claims; canonical summary <=20000 UTF-16 units."

changedInput schema / properties / summary / properties / claims / items / properties / content / description

Previous value: -"Atomic claim content; at most 2000 code points after privacy filtering."New value: +"Atomic claim; <=2000 code points after privacy filtering."

changedInput schema / properties / summary / properties / claims / items / properties / support_ids / description

Previous value: -"1-16 distinct evidence ids from this project_key + root_session_key/harness session inside summary.coverage; never memory, summary, or observation ids."New value: +"Distinct evidence ids inside coverage from this project_key + root_session_key/harness session; never memory, summary, or observation ids."

changedInput schema / properties / summary / properties / coverage / description

Previous value: -"Inclusive session evidence coverage; start at 1 and advance to_sequence for this session and summary kind."New value: +"Inclusive session evidence range."

changedInput schema / properties / summary / properties / coverage / properties / from_sequence / description

Previous value: -"Inclusive first session event sequence; must start at 1."New value: +"First event sequence: 1."

changedInput schema / properties / summary / properties / coverage / properties / to_sequence / description

Previous value: -"Inclusive last session event sequence; must be >= from_sequence and exceed the current summary ending sequence for this session and kind."New value: +"Last sequence: >= from_sequence and >= the current summary's ending sequence for this session."

removedInput schema / properties / summary / properties / kind

Removed value: -{
-  "description": "Send checkpoint for operation=\"checkpoint_pre_compact\" or final for operation=\"finalize\".",
-  "enum": [
-    "checkpoint",
-    "final"
-  ],
-  "type": "string"
-}

changedInput schema / properties / summary / required

Previous value: -[
-  "kind",
-  "coverage",
-  "generator",
-  "claims"
-]New value: +[
+  "coverage",
+  "generator",
+  "claims"
+]

6 tool updatesv0.5.6Oct 4, 2026

Changedmem_context13 fields changed

addedInput schema / properties / budget_chars
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / correlation_id
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / finalize_answer
```
Added value: +{
+  "type": "boolean"
+}
```

addedInput schema / properties / harness

Added value: +{
+  "description": "Native harness for root_session_key; supply both for session context, or omit both for project context.",
+  "enum": [
+    "opencode",
+    "codex",
+    "claude",
+    "pi",
+    "mcp",
+    "cli",
+    "import"
+  ],
+  "type": "string"
+}

removedInput schema / properties / limit

Removed value: -{
-  "description": "Number of observations to retrieve (default: 20)",
-  "type": "number"
-}

removedInput schema / properties / max_chars

Removed value: -{
-  "description": "Output character budget; 0 disables the context cap",
-  "minimum": 0,
-  "type": "number"
-}

removedInput schema / properties / project

Removed value: -{
-  "description": "Filter by project name",
-  "type": "string"
-}

addedInput schema / properties / project_key

Added value: +{
+  "description": "Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content.",
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / recall_query

Removed value: -{
-  "description": "Optional query to append fused recall evidence without changing base context sections",
-  "type": "string"
-}

addedInput schema / properties / root_session_key

Added value: +{
+  "description": "Optional verified root session key; supply with harness for session context, or omit both for project context.",
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / scope

Removed value: -{
-  "description": "Filter by scope",
-  "enum": [
-    "project",
-    "personal"
-  ],
-  "type": "string"
-}

removedInput schema / properties / session_id

Removed value: -{
-  "description": "Filter to a specific session",
-  "type": "string"
-}

addedInput schema / required
```
Added value: +[
+  "project_key"
+]
```

Changedmem_get10 fields changed

removedInput schema / properties / after

Removed value: -{
-  "description": "Timeline observations after the focus item (default: 5)",
-  "maximum": 20,
-  "minimum": 0,
-  "type": "number"
-}

removedInput schema / properties / before

Removed value: -{
-  "description": "Timeline observations before the focus item (default: 5)",
-  "maximum": 20,
-  "minimum": 0,
-  "type": "number"
-}

addedInput schema / properties / correlation_id
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / history

Added value: +{
+  "description": "Set true to expand predecessor lineage for memory, summary, or observation records; evidence ids have no lineage.",
+  "type": "boolean"
+}

changedInput schema / properties / id / description

Previous value: -"Record ID to retrieve, interpreted according to kind"New value: +"Memory, summary, observation, or evidence id returned by a prior tool result."

changedInput schema / properties / id / type

Previous value: -"number"New value: +"string"

removedInput schema / properties / include_timeline

Removed value: -{
-  "description": "Include surrounding observations in the same session",
-  "type": "boolean"
-}

removedInput schema / properties / kind

Removed value: -{
-  "description": "Memory kind to retrieve (defaults to observation)",
-  "enum": [
-    "observation",
-    "prompt"
-  ],
-  "type": "string"
-}

removedInput schema / properties / max_length

Removed value: -{
-  "description": "Max characters to return (default: 50000)",
-  "minimum": 100,
-  "type": "number"
-}

removedInput schema / properties / offset

Removed value: -{
-  "description": "Character offset for large content (default: 0)",
-  "minimum": 0,
-  "type": "number"
-}

Changedmem_project26 fields changed

changedInput schema / properties / action / description

Previous value: -"Project view to return"New value: +"Inspect project views without mutation. action=\"list\": no fields required. action=\"timeline\": project_key required; optionally since, until, cursor, limit, and budget_chars. action=\"briefing\", \"summaries\", or \"observations\": project_key required; optionally supply both root_session_key and harness to select that session's summaries/observations (briefing still includes project-wide memories). action=\"history\": id required from a prior result. temporal filters summaries/observations, not timeline. list returns at most 256 exact aliases per project plus aliasCount and aliasesTruncated metadata."

changedInput schema / properties / action / enum

Previous value: -[
-  "list",
-  "summary",
-  "graph",
-  "topics",
-  "topic",
-  "health"
-]New value: +[
+  "list",
+  "timeline",
+  "briefing",
+  "history",
+  "summaries",
+  "observations"
+]

addedInput schema / properties / budget_chars

Added value: +{
+  "description": "Optional aggregate character budget for timeline, briefing, summaries, or observations; timeline clamps a positive integer to 1024-20000 characters.",
+  "type": "number"
+}

removedInput schema / properties / continuation

Removed value: -{
-  "description": "Opaque continuation token returned by graph navigation views",
-  "type": "string"
-}

addedInput schema / properties / cursor

Added value: +{
+  "description": "Unchanged nextCursor from a prior mem_project action=\"timeline\" result; keep project_key, since, and until unchanged.",
+  "maxLength": 4096,
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / focus_node_id

Removed value: -{
-  "description": "Graph focus node id for navigation=neighborhood, currently obs:<id>",
-  "type": "string"
-}

addedInput schema / properties / harness

Added value: +{
+  "description": "Native harness for the optional root_session_key filter; supply both or omit both. Not accepted for action=\"timeline\".",
+  "enum": [
+    "opencode",
+    "codex",
+    "claude",
+    "pi",
+    "mcp",
+    "cli",
+    "import"
+  ],
+  "type": "string"
+}

addedInput schema / properties / id

Added value: +{
+  "description": "Required for action=\"history\"; send a record id returned by a prior tool result.",
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / include_superseded

Removed value: -{
-  "description": "Explicit history opt-in; honored by navigation=superseded only",
-  "type": "boolean"
-}

changedInput schema / properties / limit / description

Previous value: -"Maximum items to return"New value: +"Maximum items (1-100) for action=\"timeline\" or \"observations\"."

addedInput schema / properties / limit / exclusiveMinimum
```
Added value: +0
```
changedInput schema / properties / limit / maximum
```
Previous value: -500New value: +100
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```

changedInput schema / properties / limit / type

Previous value: -"number"New value: +"integer"

removedInput schema / properties / max_chars

Removed value: -{
-  "description": "Response character budget; 0 is supported for action=summary only",
-  "maximum": 20000,
-  "minimum": 0,
-  "type": "integer"
-}

removedInput schema / properties / navigation

Removed value: -{
-  "description": "Graph navigation mode for action=graph; defaults to ledger",
-  "enum": [
-    "ledger",
-    "neighborhood",
-    "lineage",
-    "community",
-    "superseded"
-  ],
-  "type": "string"
-}

removedInput schema / properties / observation_id

Removed value: -{
-  "description": "Observation id for lineage or superseded graph navigation",
-  "exclusiveMinimum": 0,
-  "maximum": 9007199254740991,
-  "type": "integer"
-}

removedInput schema / properties / project

Removed value: -{
-  "description": "Project name. Required except action=list and optional for action=topics or health",
-  "type": "string"
-}

addedInput schema / properties / project_key

Added value: +{
+  "description": "Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content. Required for action=\"timeline\", \"briefing\", \"summaries\", or \"observations\"; not required for \"list\" or \"history\".",
+  "minLength": 1,
+  "type": "string"
+}

removedInput schema / properties / relation

Removed value: -{
-  "description": "Graph relation filter for action=graph",
-  "enum": [
-    "HAS_TYPE",
-    "IN_PROJECT",
-    "HAS_TOPIC_KEY",
-    "HAS_WHAT",
-    "HAS_WHY",
-    "HAS_WHERE",
-    "HAS_LEARNED"
-  ],
-  "type": "string"
-}

addedInput schema / properties / root_session_key

Added value: +{
+  "description": "Optional session filter for action=\"briefing\", \"summaries\", or \"observations\"; supply with harness or omit both.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / since

Added value: +{
+  "description": "Optional inclusive lower ISO-8601 instant for action=\"timeline\" only; must be <= until.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / state

Added value: +{
+  "description": "Optional state filter for action=\"observations\".",
+  "enum": [
+    "pending",
+    "accepted",
+    "rejected",
+    "promoted"
+  ],
+  "type": "string"
+}

addedInput schema / properties / temporal

Added value: +{
+  "description": "Filter summaries/observations: current selects current summary versions or observation correction-chain leaves; history includes older summary versions or selects observation predecessors. Not accepted for action=\"timeline\".",
+  "enum": [
+    "current",
+    "history"
+  ],
+  "type": "string"
+}

removedInput schema / properties / topic_key

Removed value: -{
-  "description": "Topic key for action=topic or graph filtering",
-  "type": "string"
-}

addedInput schema / properties / until

Added value: +{
+  "description": "Optional inclusive upper ISO-8601 instant for action=\"timeline\" only; must be >= since.",
+  "minLength": 1,
+  "type": "string"
+}

Changedmem_recall20 fields changed

addedInput schema / properties / budget_chars
```
Added value: +{
+  "type": "number"
+}
```
addedInput schema / properties / correlation_id
```
Added value: +{
+  "type": "string"
+}
```

removedInput schema / properties / debug

Removed value: -{
-  "description": "Include retrieval defaults and semantic input sources",
-  "type": "boolean"
-}

addedInput schema / properties / finalize_answer
```
Added value: +{
+  "type": "boolean"
+}
```

removedInput schema / properties / hyde

Removed value: -{
-  "description": "Request HyDE query expansion when configured",
-  "type": "boolean"
-}

removedInput schema / properties / limit / description

Removed value: -"Maximum evidence items (default: 5)"

removedInput schema / properties / limit / maximum
```
Removed value: -20
```
removedInput schema / properties / limit / minimum
```
Removed value: -1
```

changedInput schema / properties / mode / description

Previous value: -"compact returns evidence lines; context includes retrieved text"New value: +"compact (default) returns bounded snippets; context adds selected memory content."

removedInput schema / properties / project

Removed value: -{
-  "description": "Optional project filter",
-  "type": "string"
-}

addedInput schema / properties / project_key

Added value: +{
+  "description": "Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content.",
+  "minLength": 1,
+  "type": "string"
+}

changedInput schema / properties / query / description

Previous value: -"Recall/search query"New value: +"Non-empty search string for promoted project memory."

removedInput schema / properties / scope

Removed value: -{
-  "description": "Optional scope filter",
-  "enum": [
-    "project",
-    "personal"
-  ],
-  "type": "string"
-}

removedInput schema / properties / session_id

Removed value: -{
-  "description": "Optional session filter",
-  "type": "string"
-}

addedInput schema / properties / temporal

Added value: +{
+  "description": "current (default) searches current guidance; history includes historical records.",
+  "enum": [
+    "current",
+    "history"
+  ],
+  "type": "string"
+}

removedInput schema / properties / time_from

Removed value: -{
-  "description": "Optional inclusive created_at lower bound",
-  "type": "string"
-}

removedInput schema / properties / time_to

Removed value: -{
-  "description": "Optional inclusive created_at upper bound",
-  "type": "string"
-}

removedInput schema / properties / topic_key

Removed value: -{
-  "description": "Optional exact topic_key filter",
-  "type": "string"
-}

removedInput schema / properties / type

Removed value: -{
-  "description": "Optional observation type filter",
-  "enum": [
-    "decision",
-    "architecture",
-    "bugfix",
-    "pattern",
-    "config",
-    "discovery",
-    "learning",
-    "session_summary",
-    "manual"
-  ],
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "query"
-]New value: +[
+  "project_key",
+  "query"
+]

Changedmem_save19 fields changed

removedInput schema / properties / content

Removed value: -{
-  "description": "Memory content, prompt text, session summary, or text containing a Key Learnings section",
-  "type": "string"
-}

addedInput schema / properties / event_key

Added value: +{
+  "description": "Stable event key for idempotency; required for observation, observation_review, observation_promotion, and evidence with metadata.",
+  "type": "string"
+}

addedInput schema / properties / evidence

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "content": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "kind": {
+          "enum": [
+            "root_prompt",
+            "explicit_save",
+            "checkpoint",
+            "handoff",
+            "legacy_prompt",
+            "legacy_observation",
+            "session_summary"
+          ],
+          "type": "string"
+        },
+        "source_ref": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "content"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "content": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "kind": {
+          "const": "explicit_save",
+          "type": "string"
+        },
+        "metadata": {
+          "additionalProperties": false,
+          "properties": {
+            "observation_validation": {
+              "additionalProperties": false,
+              "properties": {
+                "method": {
+                  "maxLength": 500,
+                  "minLength": 1,
+                  "type": "string"
+                },
+                "observation_id": {
+                  "maxLength": 200,
+                  "minLength": 1,
+                  "type": "string"
+                },
+                "result": {
+                  "enum": [
+                    "passed",
+                    "failed"
+                  ],
+                  "type": "string"
+                }
+              },
+              "required": [
+                "observation_id",
+                "result",
+                "method"
+              ],
+              "type": "object"
+            }
+          },
+          "required": [
+            "observation_validation"
+          ],
+          "type": "object"
+        },
+        "source_ref": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "content",
+        "metadata"
+      ],
+      "type": "object"
+    },
+    {
+      "additionalProperties": false,
+      "properties": {
+        "content": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "kind": {
+          "const": "handoff",
+          "type": "string"
+        },
+        "metadata": {
+          "additionalProperties": false,
+          "properties": {
+            "observation_review_attestation": {
+              "additionalProperties": false,
+              "properties": {
+                "method": {
+                  "maxLength": 500,
+                  "minLength": 1,
+                  "type": "string"
+                },
+                "observation_id": {
+                  "maxLength": 200,
+                  "minLength": 1,
+                  "type": "string"
+                },
+                "reviewer": {
+                  "maxLength": 200,
+                  "minLength": 1,
+                  "type": "string"
+                },
+                "verdict": {
+                  "enum": [
+                    "accepted",
+                    "rejected"
+                  ],
+                  "type": "string"
+                }
+              },
+              "required": [
+                "observation_id",
+                "verdict",
+                "reviewer",
+                "method"
+              ],
+              "type": "object"
+            }
+          },
+          "required": [
+            "observation_review_attestation"
+          ],
+          "type": "object"
+        },
+        "source_ref": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "content",
+        "metadata"
+      ],
+      "type": "object"
+    }
+  ],
+  "description": "Direct evidence { kind, content }; optionally add memory for a promoted save. Structured metadata forbids memory and requires event_key, root_session_key, and harness."
+}

addedInput schema / properties / harness

Added value: +{
+  "description": "Native harness for root_session_key; supply both or omit both. Required wherever root_session_key is required.",
+  "enum": [
+    "opencode",
+    "codex",
+    "claude",
+    "pi",
+    "mcp",
+    "cli",
+    "import"
+  ],
+  "type": "string"
+}

removedInput schema / properties / kind

Removed value: -{
-  "description": "Write mode. Defaults to observation",
-  "enum": [
-    "observation",
-    "prompt",
-    "session_summary",
-    "passive_learnings"
-  ],
-  "type": "string"
-}

addedInput schema / properties / memory

Added value: +{
+  "additionalProperties": false,
+  "description": "Promoted memory for direct evidence only; requires evidence without metadata. Do not combine with observation, observation_review, or observation_promotion.",
+  "properties": {
+    "content": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "kind": {
+      "enum": [
+        "decision",
+        "convention",
+        "architecture",
+        "discovery",
+        "failure",
+        "project_structure",
+        "handoff",
+        "preference"
+      ],
+      "type": "string"
+    },
+    "outcome": {
+      "enum": [
+        "unknown",
+        "succeeded",
+        "failed",
+        "mixed"
+      ],
+      "type": "string"
+    },
+    "supersedes_id": {
+      "type": "string"
+    },
+    "title": {
+      "minLength": 1,
+      "type": "string"
+    },
+    "topic_key": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "title",
+    "content"
+  ],
+  "type": "object"
+}

addedInput schema / properties / observation

Added value: +{
+  "additionalProperties": false,
+  "description": "Submit a supported candidate without promotion; requires event_key. Session scope also requires root_session_key, harness, and coverage.",
+  "properties": {
+    "claim": {
+      "maxLength": 4000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "concepts": {
+      "items": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 16,
+      "type": "array"
+    },
+    "coverage": {
+      "additionalProperties": false,
+      "properties": {
+        "from_sequence": {
+          "exclusiveMinimum": 0,
+          "maximum": 9007199254740991,
+          "type": "integer"
+        },
+        "to_sequence": {
+          "exclusiveMinimum": 0,
+          "maximum": 9007199254740991,
+          "type": "integer"
+        }
+      },
+      "required": [
+        "from_sequence",
+        "to_sequence"
+      ],
+      "type": "object"
+    },
+    "files": {
+      "items": {
+        "maxLength": 500,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 16,
+      "type": "array"
+    },
+    "generator": {
+      "additionalProperties": false,
+      "properties": {
+        "config_hash": {
+          "pattern": "^[0-9a-f]{64}$",
+          "type": "string"
+        },
+        "kind": {
+          "enum": [
+            "root_agent",
+            "harness",
+            "model"
+          ],
+          "type": "string"
+        },
+        "name": {
+          "maxLength": 200,
+          "minLength": 1,
+          "type": "string"
+        },
+        "version": {
+          "maxLength": 200,
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "name"
+      ],
+      "type": "object"
+    },
+    "kind": {
+      "enum": [
+        "decision",
+        "constraint",
+        "fact",
+        "procedure",
+        "result",
+        "failure",
+        "preference"
+      ],
+      "type": "string"
+    },
+    "predecessor_id": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "proposed_memory": {
+      "additionalProperties": false,
+      "properties": {
+        "content": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "kind": {
+          "enum": [
+            "decision",
+            "convention",
+            "architecture",
+            "discovery",
+            "failure",
+            "project_structure",
+            "handoff",
+            "preference"
+          ],
+          "type": "string"
+        },
+        "outcome": {
+          "enum": [
+            "unknown",
+            "succeeded",
+            "failed",
+            "mixed"
+          ],
+          "type": "string"
+        },
+        "title": {
+          "minLength": 1,
+          "type": "string"
+        },
+        "topic_key": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "kind",
+        "title",
+        "content"
+      ],
+      "type": "object"
+    },
+    "scope": {
+      "enum": [
+        "session",
+        "project"
+      ],
+      "type": "string"
+    },
+    "support_ids": {
+      "items": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 16,
+      "minItems": 1,
+      "type": "array"
+    },
+    "title": {
+      "maxLength": 500,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "kind",
+    "scope",
+    "title",
+    "claim",
+    "proposed_memory",
+    "support_ids",
+    "generator"
+  ],
+  "type": "object"
+}

addedInput schema / properties / observation_promotion

Added value: +{
+  "additionalProperties": false,
+  "description": "Promote one accepted observation without new prose; requires event_key, root_session_key, and harness. Send no other operation branch or memory.",
+  "properties": {
+    "observation_id": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    }
+  },
+  "required": [
+    "observation_id"
+  ],
+  "type": "object"
+}

addedInput schema / properties / observation_review

Added value: +{
+  "additionalProperties": false,
+  "description": "Review one supported observation; requires event_key, root_session_key, and harness. Send no other operation branch or memory.",
+  "properties": {
+    "basis": {
+      "enum": [
+        "root_user_confirmed",
+        "observable_validation",
+        "independent_review"
+      ],
+      "type": "string"
+    },
+    "observation_id": {
+      "maxLength": 200,
+      "minLength": 1,
+      "type": "string"
+    },
+    "policy": {
+      "additionalProperties": false,
+      "properties": {
+        "id": {
+          "maxLength": 200,
+          "minLength": 1,
+          "type": "string"
+        },
+        "version": {
+          "maxLength": 200,
+          "minLength": 1,
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "version"
+      ],
+      "type": "object"
+    },
+    "reason": {
+      "maxLength": 1000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "support_ids": {
+      "items": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      },
+      "maxItems": 16,
+      "minItems": 1,
+      "type": "array"
+    },
+    "verdict": {
+      "enum": [
+        "accepted",
+        "rejected"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "observation_id",
+    "verdict",
+    "basis",
+    "policy",
+    "reason",
+    "support_ids"
+  ],
+  "type": "object"
+}

removedInput schema / properties / project

Removed value: -{
-  "description": "Project name",
-  "type": "string"
-}

addedInput schema / properties / project_key

Added value: +{
+  "description": "Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / project_name

Added value: +{
+  "description": "Creation/display metadata only; never participates in project identity equality. Prefer the database-persisted name returned by lifecycle or project output.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / root_session_key

Added value: +{
+  "description": "Verified root session key; supply with harness or omit both. Required for session-scoped observations, observation_review, observation_promotion, and evidence with metadata; blank counts as absent.",
+  "type": "string"
+}

removedInput schema / properties / scope

Removed value: -{
-  "description": "Observation scope",
-  "enum": [
-    "project",
-    "personal"
-  ],
-  "type": "string"
-}

removedInput schema / properties / session_id

Removed value: -{
-  "description": "Session ID (default: manual-save-{project})",
-  "type": "string"
-}

removedInput schema / properties / title

Removed value: -{
-  "description": "Short searchable title. Required for kind=observation",
-  "type": "string"
-}

removedInput schema / properties / topic_key

Removed value: -{
-  "description": "Stable key for observation upserts",
-  "type": "string"
-}

removedInput schema / properties / type

Removed value: -{
-  "description": "Observation category for kind=observation",
-  "enum": [
-    "decision",
-    "architecture",
-    "bugfix",
-    "pattern",
-    "config",
-    "discovery",
-    "learning",
-    "session_summary",
-    "manual"
-  ],
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "content"
-]New value: +[
+  "project_key",
+  "project_name"
+]

Changedmem_session17 fields changed

removedInput schema / properties / action

Removed value: -{
-  "description": "Session action",
-  "enum": [
-    "start",
-    "summary",
-    "checkpoint"
-  ],
-  "type": "string"
-}

removedInput schema / properties / content / description

Removed value: -"Full session summary for action=summary"

removedInput schema / properties / directory

Removed value: -{
-  "description": "Working directory for action=start",
-  "type": "string"
-}

addedInput schema / properties / event_key

Added value: +{
+  "description": "Stable lifecycle event key; retries for the same operation must resend identical content/summary.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / harness

Added value: +{
+  "description": "Verified native harness for root_session_key in project_key.",
+  "enum": [
+    "opencode",
+    "codex",
+    "claude",
+    "pi",
+    "mcp",
+    "cli",
+    "import"
+  ],
+  "type": "string"
+}

removedInput schema / properties / id

Removed value: -{
-  "description": "Session ID. Required for action=start; defaults to manual-save-{project} for summary/checkpoint",
-  "type": "string"
-}

addedInput schema / properties / operation

Added value: +{
+  "description": "Lifecycle operation; summary is allowed only for checkpoint_pre_compact (checkpoint) or finalize (final).",
+  "enum": [
+    "enroll",
+    "recover",
+    "capture_root",
+    "checkpoint_pre_compact",
+    "guide_post_compact",
+    "finalize"
+  ],
+  "type": "string"
+}

removedInput schema / properties / project

Removed value: -{
-  "description": "Project name",
-  "type": "string"
-}

addedInput schema / properties / project_key

Added value: +{
+  "description": "Exact opaque project_key copied verbatim from verified native identity; never derive it from a display name, path hint, remote, branch, worktree name, host ID, listing, or recalled content.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / project_name

Added value: +{
+  "description": "Creation/display metadata only; never participates in project identity equality. Prefer the database-persisted name returned by lifecycle or project output.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / root_session_key

Added value: +{
+  "description": "Stable verified root session key; required with harness for every operation.",
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / summary / additionalProperties
```
Added value: +false
```

changedInput schema / properties / summary / description

Previous value: -"Short checkpoint summary for action=checkpoint"New value: +"Optional only for operation=\"checkpoint_pre_compact\" (kind=\"checkpoint\") or operation=\"finalize\" (kind=\"final\"). coverage starts at 1 and to_sequence must advance the current summary for this session and kind. support_ids must be evidence ids from this project_key + root_session_key/harness session inside coverage. Canonical submission limit: 20000 UTF-16 units."

addedInput schema / properties / summary / properties

Added value: +{
+  "claims": {
+    "description": "1-32 atomic supported claims; keep the canonical summary within 20000 UTF-16 units.",
+    "items": {
+      "additionalProperties": false,
+      "properties": {
+        "content": {
+          "description": "Atomic claim content; at most 2000 code points after privacy filtering.",
+          "minLength": 1,
+          "type": "string"
+        },
+        "kind": {
+          "enum": [
+            "objective",
+            "completed",
+            "decision",
+            "changed_surface",
+            "verification",
+            "pending",
+            "blocker",
+            "next_action"
+          ],
+          "type": "string"
+        },
+        "outcome": {
+          "enum": [
+            "unknown",
+            "succeeded",
+            "failed",
+            "mixed"
+          ],
+          "type": "string"
+        },
+        "support_ids": {
+          "description": "1-16 distinct evidence ids from this project_key + root_session_key/harness session inside summary.coverage; never memory, summary, or observation ids.",
+          "items": {
+            "maxLength": 200,
+            "minLength": 1,
+            "type": "string"
+          },
+          "maxItems": 16,
+          "minItems": 1,
+          "type": "array"
+        }
+      },
+      "required": [
+        "kind",
+        "content",
+        "support_ids"
+      ],
+      "type": "object"
+    },
+    "maxItems": 32,
+    "minItems": 1,
+    "type": "array"
+  },
+  "coverage": {
+    "additionalProperties": false,
+    "description": "Inclusive session evidence coverage; start at 1 and advance to_sequence for this session and summary kind.",
+    "properties": {
+      "from_sequence": {
+        "description": "Inclusive first session event sequence; must start at 1.",
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      },
+      "to_sequence": {
+        "description": "Inclusive last session event sequence; must be >= from_sequence and exceed the current summary ending sequence for this session and kind.",
+        "exclusiveMinimum": 0,
+        "maximum": 9007199254740991,
+        "type": "integer"
+      }
+    },
+    "required": [
+      "from_sequence",
+      "to_sequence"
+    ],
+    "type": "object"
+  },
+  "generator": {
+    "additionalProperties": false,
+    "properties": {
+      "config_hash": {
+        "pattern": "^[0-9a-f]{64}$",
+        "type": "string"
+      },
+      "kind": {
+        "enum": [
+          "root_agent",
+          "harness",
+          "model"
+        ],
+        "type": "string"
+      },
+      "name": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      },
+      "version": {
+        "maxLength": 200,
+        "minLength": 1,
+        "type": "string"
+      }
+    },
+    "required": [
+      "kind",
+      "name"
+    ],
+    "type": "object"
+  },
+  "kind": {
+    "description": "Send checkpoint for operation=\"checkpoint_pre_compact\" or final for operation=\"finalize\".",
+    "enum": [
+      "checkpoint",
+      "final"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / summary / required

Added value: +[
+  "kind",
+  "coverage",
+  "generator",
+  "claims"
+]

changedInput schema / properties / summary / type

Previous value: -"string"New value: +"object"

changedInput schema / required

Previous value: -[
-  "action",
-  "project"
-]New value: +[
+  "operation",
+  "harness",
+  "project_key",
+  "project_name",
+  "root_session_key",
+  "event_key"
+]

5 tool updatesv0.4.13Aug 21, 2026
- Addedmem_context
- Addedmem_get
- Addedmem_project
- Addedmem_save
- Addedmem_session
5 tool updatesv0.4.1Jul 20, 2026
- Removedmem_context
- Removedmem_get
- Removedmem_project
- Removedmem_save
- Removedmem_session
6 tool updatesv0.3.7Jul 11, 2026
- First observedmem_context
- First observedmem_get
- First observedmem_project
- First observedmem_recall
- First observedmem_save
- First observedmem_session

Deploy Server

Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

TDQS

B3.3/5.0

Scored 2026-10-25 00:20 across 6 tools

Disambiguation4/5

mem_save and mem_session both persist information, but mem_session is explicitly limited to lifecycle events. The read-side tools (mem_recall, mem_context, mem_project) have overlapping search/context/view roles, which could cause misselection, though descriptions provide clear trigger guidance.

Naming Consistency4/5

All tools use a consistent mem_ prefix in snake_case, making names predictable and readable. Minor inconsistency exists because some names are verbs (save, get, recall) and others are nouns (context, project, session), but the pattern is still coherent.

Tool Count5/5

Six tools is well within the ideal range for a focused memory server. Each tool maps to a distinct stage of the memory lifecycle—save, recall, expand, context building, project inspection, and session events—without obvious redundancy.

Completeness3/5

The surface covers saving, searching, retrieval, context building, project views, and session lifecycle. However, there is no explicit update or delete/forget operation for memories, and listing memories beyond search results or project views is limited, which may hinder correcting or pruning stored knowledge.

Maintenance

ActivityActive

ResponsivenessNo issues

Resources

Related MCP Connectors

goldhold
io.github.jerrysrodz
Persistent memory for AI agents. Search, store, and recall across sessions.
Knowledge & Memory Autonomous Agents RAG Systems
2
https://relay.goldhold.ai/mcp
TeamShared C
io.github.xhad
Shared memory for coding agents. Stop re-explaining your codebase every session.
Knowledge & Memory Developer Tools
1981
https://teamshared.com/mcp
MemorySync AOAuth
io.memorysync
Persistent memory for AI agents. Search and store durable facts, preferences and decisions.
Autonomous Agents Developer Tools Knowledge & Memory
151
https://mcp.memorysync.io/mcp
Memoize — persistent agent memoryOAuth
io.github.harrisonford
Persistent cross-session memory shared by Codex, Claude Code, ChatGPT, and other AI agents.
Knowledge & Memory Autonomous Agents
1
https://memoize.xyz/mcp

Related MCP Servers

MCP Vector Memory
Knowledge & Memory Vector Databases RAG Systems
vertexhub-ai
A
license
Not graded
quality
Not graded
maintenance
Provides AI coding agents with persistent, long-term memory through local semantic search and SQLite storage. It enables agents to save and retrieve architectural decisions or project context across different conversation sessions without requiring cloud services.
Updated 8 months ago (2026-02-19 15:50 UTC)
MIT
LumenCore
Knowledge & Memory Developer Tools Autonomous Agents
arclightdynamics
A
license
Not graded
quality
D
maintenance
Provides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.
Updated 4 months ago (2026-06-14 18:44 UTC)
0
Apache 2.0
code-recall
Knowledge & Memory Developer Tools
AbianS
A
license
Not graded
quality
C
maintenance
Gives AI coding agents persistent memory by storing observations, decisions, and learnings in a local SQLite database with vector search, full-text search, and a rules engine.
Updated 9 months ago (2026-01-31 12:30 UTC)
4
MIT
io.github.oleksiijko/pmb-ai
Knowledge & Memory Developer Tools
oleksiijko
A
license
A
quality
A
maintenance
Local-first memory for AI coding agents using SQLite, enabling persistent recall of decisions, lessons, and project context without cloud or API keys.
Updated a month ago (2026-09-23 18:04 UTC)
10
157 PyPI
286
Apache 2.0