#1 Persistent memory for AI coding agents based on real-world benchmarks
TypeScript agentmemoryagentsaiclaudeclaudecodecodexcopilotcursorgenaiharnesshermesmemoryompopenclawopencodepi
docs: embed iii console screenshots in README
Rohit Ghumared87cfa69219b
diff --git a/README.md b/README.mdindex 82044dc2..bb26126d 100644--- a/README.md+++ b/README.md@@ -723,6 +723,12 @@ The viewer server binds to `127.0.0.1` by default. The REST-served `/agentmemoryagentmemory runs on the [iii engine](https://iii.dev), so the official [iii console](https://iii.dev/docs/console) gives you OpenTelemetry traces, the raw key/value state store, the stream monitor, and a direct function invoker for every piece of memory machinery. Use it to watch a `memory.search` call hit BM25 → embeddings → reranker in real time, replay a hook invocation, or poke individual functions without going through MCP.+<p align="center">+ <img src="assets/iii-console/dashboard.png" alt="iii console dashboard — system counters, application flow, registered triggers, live WebSocket status" width="720" />+ <br/>+ <em>Dashboard: functions, triggers, workers, streams, live flow graph. Screenshot from <a href="https://iii.dev/docs/console">iii.dev/docs/console</a>.</em>+</p>+**Install once:**```bash@@ -749,6 +755,12 @@ Then open `http://localhost:3114`.| **Traces** | OpenTelemetry waterfall / flame / service-breakdown views. Filter by `trace_id` to see exactly which functions, DB calls, and embedding requests a single `memory.search` produced. || **Logs** | Structured OTEL logs correlated to trace/span IDs. |+<p align="center">+ <img src="assets/iii-console/traces-waterfall.png" alt="iii console trace waterfall view showing per-span duration" width="720" />+ <br/>+ <em>Traces: waterfall / flame / service breakdown for every memory operation.</em>+</p>+**Traces are already on:**`iii-config.yaml` ships with the `iii-observability` worker enabled (`exporter: memory`, `sampling_ratio: 1.0`, metrics + logs). No extra config needed — the moment agentmemory starts, every memory operation emits a trace span and a structured log the console can read.diff --git a/assets/iii-console/dashboard.png b/assets/iii-console/dashboard.pngnew file mode 100644index 00000000..dcdf047bBinary files /dev/null and b/assets/iii-console/dashboard.png differdiff --git a/assets/iii-console/states.png b/assets/iii-console/states.pngnew file mode 100644index 00000000..7a6f503dBinary files /dev/null and b/assets/iii-console/states.png differdiff --git a/assets/iii-console/traces-waterfall.png b/assets/iii-console/traces-waterfall.pngnew file mode 100644index 00000000..976c10ccBinary files /dev/null and b/assets/iii-console/traces-waterfall.png differ