Demos

Portable memory across any LLM. The consoles below are self-contained and auto-play. They show one Cortex store, reached through one cndk_v1_… key, shared across Claude, Google Gemini, ChatGPT and plain HTTP. Write it once, recall it from a different vendor, forget it for all. Press B/E to switch the business and engineer views, R to replay.

The memory life-cycle · Walkthrough · connect → add → remove → export → delete, one key

An illustrative walkthrough. Cortex starts with eight memories; Claude adds two and forgets one; you export all nine to your own device, then wipe Cortex — and your device keeps the nine. Your memory, your device, your call.

Cross-vendor proof · Recorded · Gemini + ChatGPT / curl, one key, both directions

Two vendors write and recall the same memory over one cndk_v1_… key. Gemini's model self-invokes Cortex, ChatGPT and curl read it back verbatim, then the reverse.

One memory, every client · Recorded · the constellation view

Claude, Gemini, Grok, ChatGPT and curl ring one Cortex hub. Write, then read across all of them, then a single forget removes the entry for everyone (Grok is in via its CLI; its public web-connector is next).

More demos

Eleven more consoles, each built around one Cortex capability on its own page.

Memory that travels →

One memory, stamped by each AI as it moves from Claude to Gemini to ChatGPT — all on a single key.
One key, every vault →

The same key unlocks each vendor's vault to the identical memory inside — one store, many clients.
The memory ledger →

Every add, recall, export and forget streams down a timeline with a running count you can follow.
Export and keep it →

Copy everything to your own device, then wipe Cortex — your device keeps the lot. Your memory, your call.
Every answer, with its receipt →

A recall shows who wrote it, where it lives, and when it was true — the answer and its provenance together.
Tamper-evident record →

Chained records that break visibly the moment a single entry is altered — integrity you can prove.
How memory matures →

A fact settles from working notes down through the tiers to the immutable deep archive. Watch one graduate.
Redacted before it lands →

Emails, card numbers and secrets are scrubbed out on the way in, before anything is ever stored.
Cortex vs a document store →

Portability, provenance and self-invocation, scored side by side against SharePoint plus a plugin.
One question, two backends →

A folder of files to open and read, versus one connected answer that carries its own provenance.
Switching models →

Carry a populated memory from one model to another; the same entry ids survive the move. The use case Cortex was built for.

These consoles replay the same tools a signed-in Cortex key can run for real. Create or paste a key to try it yourself.

Prefer a recording?

The consoles above are the demo, interactive, theme-aware and a fraction of the size. Screen-capture recordings (a business cut and an engineer/raw-JSON cut, ~17–26 MB QuickTime .mov) exist as shareable files and can be added here on request; the consoles carry the same content, so start with them.