TOMC Memory

TOMC Memory

English | 简体中文 · v0.3.1 research preview · MIT

When a fact changes, only the latest version comes back. TOMC Memory prepares a smaller, task-specific context from a long history or from notes you saved, on CPU, with each kept value linked to its source line. It works as an MCP server for Codex, Claude Code and other MCP clients, and as a Python API before your own LLM call.

After installing, say "Try TOMC Memory" to your assistant, or run tomc try.

Start here

What it stores

The Python prepare_context helper is stateless. The MCP tools save notebooks only when you call remember_memory, and save prepared results only if you turn that on (tomc settings --save-mcp-results on). Everything stays in a local SQLite file. Security and privacy

Understand the method

Method semantics explains state replay, relation joins, counts and budget handling. Architecture shows where the compiler sits between your history and your model. Comparison with other tools describes how compilation differs from token selection and persistent memory systems. Context ownership explains why TOMC leaves the active chat to the host.

Read the evidence

Evidence collects the assistant trials, the v0.3.0 stale-value benchmark and the BEAM and RULER results with their conditions. Paper results holds the paper snapshot tables (manuscript commit 7399657). Claims and limitations explains how to read them, and Reproducibility shows how to recheck the arithmetic offline with make reproduce. The paper is not public yet.