@joshuaswarren/openclaw-engram 9.0.57 → 9.0.58
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +47 -0
- package/dist/{chunk-U5UEY7UV.js → chunk-CWVXHH36.js} +1 -1
- package/dist/chunk-CWVXHH36.js.map +1 -0
- package/dist/index.js +1052 -122
- package/dist/index.js.map +1 -1
- package/dist/{storage-CR3PELFY.js → storage-XJW3E2FQ.js} +2 -2
- package/openclaw.plugin.json +4 -0
- package/package.json +1 -1
- package/dist/chunk-U5UEY7UV.js.map +0 -1
- /package/dist/{storage-CR3PELFY.js.map → storage-XJW3E2FQ.js.map} +0 -0
package/README.md
CHANGED
|
@@ -97,6 +97,52 @@ openclaw engram doctor --json # Aggregated safe health diagnostics
|
|
|
97
97
|
openclaw engram inventory --json # Baseline memory/entity/storage footprint
|
|
98
98
|
```
|
|
99
99
|
|
|
100
|
+
## Universal Access Layer
|
|
101
|
+
|
|
102
|
+
Engram exposes the same local service layer through:
|
|
103
|
+
|
|
104
|
+
- an authenticated loopback HTTP API for scripts and local operator tooling
|
|
105
|
+
- a stdio MCP server for Codex, Claude Code, and other MCP clients
|
|
106
|
+
|
|
107
|
+
Start the HTTP server:
|
|
108
|
+
|
|
109
|
+
```bash
|
|
110
|
+
openclaw engram access http-serve --token "$OPENCLAW_ENGRAM_ACCESS_TOKEN"
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
Run the MCP server over stdio:
|
|
114
|
+
|
|
115
|
+
```bash
|
|
116
|
+
openclaw engram access mcp-serve
|
|
117
|
+
```
|
|
118
|
+
|
|
119
|
+
For MCP clients, point the command at `openclaw engram access mcp-serve`. The MCP side is intentionally stdio-first and reuses the same local storage plus service layer, so it does not need a separate host/port config surface.
|
|
120
|
+
|
|
121
|
+
HTTP highlights:
|
|
122
|
+
|
|
123
|
+
- `GET /engram/v1/health`
|
|
124
|
+
- `POST /engram/v1/recall`
|
|
125
|
+
- `POST /engram/v1/recall/explain`
|
|
126
|
+
- `POST /engram/v1/memories`
|
|
127
|
+
- `POST /engram/v1/suggestions`
|
|
128
|
+
- `GET /engram/v1/memories/:id`
|
|
129
|
+
- `GET /engram/v1/memories/:id/timeline`
|
|
130
|
+
- `GET /engram/v1/entities/:name`
|
|
131
|
+
- `GET /engram/v1/review-queue`
|
|
132
|
+
|
|
133
|
+
MCP highlights:
|
|
134
|
+
|
|
135
|
+
- `engram.recall`
|
|
136
|
+
- `engram.recall_explain`
|
|
137
|
+
- `engram.memory_get`
|
|
138
|
+
- `engram.memory_timeline`
|
|
139
|
+
- `engram.memory_store`
|
|
140
|
+
- `engram.suggestion_submit`
|
|
141
|
+
- `engram.entity_get`
|
|
142
|
+
- `engram.review_queue_list`
|
|
143
|
+
|
|
144
|
+
Recall requests support `query`, `sessionKey`, `namespace`, `topK`, `mode`, and `includeDebug`. Recall responses include `results`, `count`, `traceId`, `plannerMode`, `fallbackUsed`, `sourcesUsed`, `budgetsApplied`, and `latencyMs`.
|
|
145
|
+
|
|
100
146
|
## Explicit Capture
|
|
101
147
|
|
|
102
148
|
Set `captureMode` to control how memories are created:
|
|
@@ -234,6 +280,7 @@ openclaw engram governance-report # Read the latest or named governance
|
|
|
234
280
|
openclaw engram governance-restore --run-id <runId> # Restore one applied governance run
|
|
235
281
|
openclaw engram review-disposition <memoryId> --status rejected # Record an explicit operator review outcome
|
|
236
282
|
openclaw engram access http-serve --token "$OPENCLAW_ENGRAM_ACCESS_TOKEN" # Start the local access API + admin console shell
|
|
283
|
+
openclaw engram access mcp-serve # Run the stdio MCP server for Codex/Claude Code
|
|
237
284
|
openclaw engram work-product-status # Work-product ledger counts and latest recorded output
|
|
238
285
|
openclaw engram work-product-record # Record a typed work-product ledger entry
|
|
239
286
|
openclaw engram work-product-recall-search <query> # Preview reusable work products from the creation-memory ledger
|