This shows how a Claude Managed Agent builds institutional memory across sessions — a pattern for AI that genuinely gets sharper over time.
Session 1 — baseline: HOLOCRON-9 reads raw KSE intel docs, assembles a full account picture, and writes structured memory files to its Holocron Chamber at /mnt/memory/.
Session 2 — reconcile: Contradicting intel arrives overnight. The agent reads saved memory, detects conflicts, and updates the files rather than silently overwriting. Watch the diff in the chamber for exactly what changed and why.
The Memory tool is a first-class Anthropic API primitive. This harness visualizes live tool calls, reasoning, and memory snapshots as the agent works.
Client: Kuat Systems Engineering · Model: claude-sonnet-4-6 · Chamber: /mnt/memory/
⚠ Running HOLOCRON-9 live
This is different from a typical live chat demo. Clicking run live uses your Anthropic API key, server-side, to:
Provision a real agent, environment, and memory store in your own Anthropic workspace — not ours.
Run two full live agent sessions against those resources (baseline, then reconcile) — real reasoning, real tool calls, real cost on your key. This is slower and pricier than a single-call demo.
Best-effort clean the environment and memory store up afterward. The agent record can only be archived, not deleted, by this API, so it persists harmlessly in your workspace. If cleanup ever fails, everything is visible and manageable at platform.claude.com under your own account.
Your key is sent directly to our relay over HTTPS for this request only — never stored, never logged, cleared when you leave this page.
◈ HOLOCRON-9 — watch the memory build, then reconcile
Kuat Systems Engineering renewal · run the sessions live and watch the agent work
Elapsed—
Tools—
TokensEST—
CreditsEST—
Elapsed—
Tools—
TokensEST—
CreditsEST—
REPLAYLIVE
idle — press a run button
▸ what HOLOCRON-9 was asked (the user message)
Agent activity
The brief
Holocron Chamber · /mnt/memory/ (snapshot after run)
Ask HOLOCRON-9 about its memory
Powered by Haiku · reads the live /mnt/memory/ store · requires the local presenter server