VERIFIABLE COGNITION · OPEN SOURCE · ZERO TRUST

PROVE WHAT
YOUR AI DID.

korg records every step your AI agent takes to a signed, tamper-evident ledger. Verify what it actually did — in your browser, in Python, or as one Rust binary — with zero trust in us. (And yes — it remembers across every vendor, too.)

VERIFY IT YOURSELF → FORGE A RECEIPT — $1,000 → GET STARTED
INSTALL pip install korgex
04
CAPTURE ADAPTERS
715+
TESTS PASSING
30+
MCP TOOLS EXPOSED
100%
LOCAL · OPEN SOURCE
DON'T TRUST US

VERIFY WHAT YOUR
AI ACTUALLY DID.

Every run becomes a signed, tamper-evident receipt — every prompt, file, and command, hash-chained. Check a real one yourself three independent ways: in your browser, in Python, or as one Rust binary. Tamper a single byte and all three reject it. No other coding agent can hand you that.

VERIFY A REAL DELIVERABLE → FORGE A RECEIPT — $1,000 →
THE KILLER DEMO

YOU SOLVED THIS BEFORE.
NOW YOUR AI KNOWS IT TOO.

Three weeks ago in a different session, you fixed an OAuth refresh bug. Today you've forgotten exactly how. Without memory, Claude gives a generic OAuth explanation. With Korg installed:

CLAUDE-CODE / KORG-RECALL LIVE
how did i fix the oauth token refresh failing on 401 last time?
// claude calls the recall MCP tool
recall(query="oauth token refresh 401", mode="semantic", top_n=3)
[recall · semantic] 2 match(es):
  · seq=4127 score=0.84 agent=claude-code#a3b · the 401 happens because the access_token expires during the request lifecycle…
  · seq=4131 score=0.79 agent=claude-code#a3b · added a 5-second refresh window + retry-once-on-401 wrapper…
You solved this on May 7 — the 401 was from racing the token refresh. You added a 5-second refresh window and a retry-once-on-401 wrapper around fetch. Want me to apply the same pattern here?
THAT'S IT. No prompt engineering. No doc dive. No re-searching Stack Overflow. The model recalled the exact session where you solved it — across days, projects, machines if you sync.
HOW IT WORKS

THREE PIECES.
ALL RUNNING LOCALLY.

No cloud, no API keys, no vendor account. Your ledger is one JSONL file on your disk. You can grep it, version it, replay it.

01 — CAPTURE

EVERY SESSION,
AUTOMATICALLY.

A background daemon tails ~/.claude/projects/**/*.jsonl as Claude Code writes them. Every prompt, tool call, and reply appended to one open ledger. Adapters for OpenAI Codex (WebSocket) and Grok Heavy (NDJSON) ship in the box.

02 — RECALL

SEARCH BY MEANING,
NOT KEYWORDS.

A single MCP tool — recall — embeds your query with BGE-small (local, no API), cosine-ranks against your entire ledger, returns top matches. Works in Claude Code or any MCP client via npx @korgg/recall-mcp.

03 — INVOKE

RE-EXECUTE,
DON'T RE-DERIVE.

Recall returns events tagged with stable tool_names. A bridge (@korgg/introspect-mcp) exposes every ecosystem binary's callables under the same identifiers. Recall a past command. Invoke it on the current branch. Loop closes.

THE SHAPE OF MEMORY

CAUSAL.
SEARCHABLE.
STRUCTURED.

Every event carries a stable tool_name, a triggered_by parent, and a flattened embedding text. Recall walks it semantically; the bridge re-executes from the same identifiers. The loop closes deterministically.

WHY THIS DIDN'T EXIST BEFORE

THE ONLY MEMORY LAYER
THAT SPANS VENDOR BOUNDARIES.

Every other vendor has the same incentive: lock you into their memory. Korg has the opposite — the ledger format is open JSONL on your own disk.

PRODUCT MEMORY SCOPE TOOLS COVERED FORMAT
CHATGPT MEMORYper-accountOpenAI onlyproprietary
ANTHROPIC MEMORY——ships nothing today
CURSOR MEMORIESper-projectCursor onlyproprietary
KORGper-machineany tool with a capture adapteropen JSONL · greppable · yours
INSTALL · SIXTY SECONDS

PIP INSTALL.
RUN. VERIFY.

The agent is one install. Every run it makes is recorded to a verifiable ledger — prove what it did with korgex verify, or hand someone a signed receipt. Bring your own model: Anthropic, OpenAI, or a self-hosted endpoint.

STEP 01

INSTALL THE AGENT

One command. Python 3.10+.

# the verifiable coding agent
pip install korgex
STEP 02

RUN IT

It plans, edits, and runs tests — recording every step to the ledger.

korgex "fix the failing test in tests/test_auth.py"
STEP 03

PROVE IT

Verify the run wasn't altered — or mint a shareable signed receipt.

korgex verify
korgex receipt --sign --html

Want cross-vendor memory inside Claude Code too? Add the recall MCP to ~/.claude.json ("command":"npx","args":["-y","@korgg/recall-mcp"]) plus the capture daemon (pipx install korg-claude-code-adapter). Optional.

BUILT IN PUBLIC · MIT

FREE FOREVER LOCALLY.
STAR IT, FORK IT, AUDIT IT.

~715 tests across 5 languages of code. Four GitHub repos. MIT. No cloud account required.

VIEW ON GITHUB