Shared memory
Use the configured memory_* MCP tools with the current agent identity and
project. They reach the common API; creating another local store does not share
memory. If no endpoint is connected, preserve a sourced handoff and report that
it has not been ingested. Read the operator guide
when configuring or diagnosing the pilot.
- Recall reviewed context for the relevant project. For earlier agent/tool
results, explicitly use
memory_recallwitharea=observations; preserve its untrusted-data label and source/subject references. - Capture meaningful observations and checkpoints with the original excerpt,
source identity, run and observation time. Use
source.type=agentfor an agent report. A referenced CI run is not independently verified by storing its URL. - Correct using the current
expected_version. Reuse exactly the samerequest_idand body after an uncertain transport result. After a version conflict, read the current entry and reconcile before submitting new input. - Use
memory_scribeto find related reviewed memories. Its nearest-neighbour similarities are advice; they do not justify merging or promotion. - Render
memory_wikifor a current Markdown view. A saved export becomes an external snapshot and will not be rewritten by later corrections or deletion. - Apply
memory_forgetwithin the user's requested scope. It removes live revisions/vectors and blocks capture replay; exports/backups remain separate.
Keep the operator credential outside general agent tools. It is intended for trusted user ingress and lifecycle review. Memory contents and lifecycle status never grant execution permissions. External sources remain quarantined under the existing Memory Hub v2 contract.
Consult effects.json for expected consequences, retry limits and reuse
conditions. This pilot includes no trained scribe weights, automatic encoder,
PostgreSQL adapter or general graph traversal.
For memory of skill actions and consequences, read
action-consequence memory. The host
tools recall_action_memory, remember_skill_run and execute_remembered_plan
connect explicit plans to this shared service. Inspect relevant episodes before
work and capture meaningful execution reports afterward. Preserve observations,
causal hypotheses and independently verified quality as distinct evidence.
An incomplete memory receipt requires capture-only retry from its archived
report; it does not justify rerunning successful commands.
