Skip to main content

NeoCore

test License Python

Long-term memory for AI assistants that recalls only what the moment needs, and never what it shouldn't.

NeoCore gives every AI harness you use one memory: Claude Code, Codex and Hermes read and write the same memory of everything you told them, on all your machines. Tell Codex something at your desk; Hermes knows it on Telegram tonight. It can also be dropped into any assistant as a Python library. Recall makes zero LLM calls: it is local, takes milliseconds and costs nothing (the optional NeoSift filter is a small local model on your graphics card, no API either). Every recalled line is quoted verbatim and dated, with a receipt pointing to its source. Governance (who may see what, what was revoked, what was corrected) is enforced at recall time, not left to the model.

NeoCore
LoCoMo (10 conversations, 1,540 questions) 87.5% (gpt-4.1-mini reader)
LongMemEval-S (500 questions) 89.6% (gpt-4.1-mini reader, gpt-4o judge)
Governance: leaks under maximal pressure 0 leaks in 1,540 questions (an ungoverned store leaked on all 1,540)
Model calls per recall 0: p50 22 ms, offline

All numbers come from this repository's code (evals/), run through the public package. See Evals for the setup and the honest caveats.

Why another memory?

The context window is small and your history is large. Most memory layers either stuff the window with everything that matches, or call an LLM on every turn to decide what to remember and recall. NeoCore starts from a different idea. Think of how a person remembers: you don't scan your whole life to answer a question. You recall the few things this moment is about. You trust that what you recall is still true, and you know what you were told in confidence.

  • Relevant, not just similar. Hybrid recall (BM25 + local embeddings, fused) is spent on a byte budget in order of relevance. An optional relevance filter keeps only what helps with this prompt. A chat is never sent again what it already holds.
  • Newest wins. A nightly "sleep" pass groups related facts and retires the stale ones ("the API runs v1.17" gives way to "the API runs v1.18"). A retired fact never arrives without what replaced it.
  • Learns from mistakes. When something went wrong, a "Lesson:" is formed and shown first next time ("never deploy the worker while a job is running").
  • Governed by construction. Scopes, revocation, audited erasure, edited messages (only the latest revision counts) and abandoned conversation branches are all filters applied before ranking. A fact is recalled only while every message it came from may be.
  • Exact and traceable. Excerpts are verbatim slices of what was said. Their offsets point into the stored message. Relative dates are resolved (last Friday [= 19 May 2023]) and clearly marked as NeoCore's note, not speech.
  • One memory, every harness. What you decided with Claude Code on Monday is there for Codex and Hermes on Tuesday, and the other way round. Every item says which AI and project it came from.
  • Knows you from the first message. A new chat starts with a short briefing built from your facts: who you are, how you like to work, what you are working on.

Quick start: Claude Code and Codex

pipx install "neocore-memory[embed]"
neocore setup

neocore setup does four things:

  • downloads the bge-small embedder (~35 MB);
  • adds a prompt hook and a stop hook to ~/.claude/settings.json (merged, backup kept);
  • adds an MCP server and the same hooks to ~/.codex/config.toml (inside marked lines);
  • writes ~/.neocore/config.json.

Codex will ask you to trust the new hooks the first time they run. neocore uninstall removes the hooks and keeps your memory. neocore doctor checks the install. Run neocore setup --dry-run to see the plan first.

Or as a plugin

The same hooks and memory tools also come as a Claude Code plugin and a Codex plugin. Install the package first (the plugins run the neocore command), then set up the memory folder without touching your settings files:

pipx install "neocore-memory[embed]"
neocore setup --no-claude --no-codex

Claude Code:

/plugin marketplace add VincentPorquet777/neocore
/plugin install neocore@neocore

Codex:

codex plugin marketplace add VincentPorquet777/neocore
codex plugin add neocore@neocore

Pick one way per tool. If neocore setup already added its hooks, the plugin's hooks stay quiet, so each prompt still gets its memory once.

After setup:

  • Every prompt gets the memory that matters, as hook context, in well under a second. A warm local daemon serves it. A chat's first prompt also gets your briefing.
  • Memory tools for the AI to look further on purpose: neocore_search, neocore_open, neocore_timeline, neocore_facts, neocore_profile and neocore_remember. Use kind=turns on neocore_search for the original wording of a decision. The default lists facts first.
  • Every finished reply starts a background sync. It reads new turns from Claude Code and Codex transcripts (prompts and final replies only; tool output is skipped and obvious secrets are redacted) and indexes them.
  • In the background, your own Codex or Claude Code sign-in forms dated facts, runs sleep and writes lessons (see neocore.llm). No API key is needed. Nothing is sent anywhere else.
  • Relevance filter (NeoSift): on a machine with a graphics card, setup installs NeoSift, NeoCore's own small model that keeps only the memories that help with this prompt. It is free and local. Without a graphics card, set OPENROUTER_API_KEY before neocore setup to use a small hosted decision model instead (~$0.0007 per prompt), or recall injects its top matches within the budget.
  • Help improve NeoSift (opt-in): setup asks once whether to share prompts and recalled memories to train NeoSift. It is off unless you say yes. See what is shared.

Useful commands:

neocore recall "how did we deploy the worker last time"
neocore status            # counts and configuration
neocore stats --days 7    # live relevance, latency, errors, and prompt cost (below)
neocore forget claude-code:<session-id>   # erase a conversation for good (audited)
neocore sift status       # NeoSift: installed, graphics card, in use
neocore share status      # opt-in sharing: on/off, rows waiting and sent

Recall makes no model call, but the answering model still reads what it adds, and where that text sits decides whether the host's prompt cache survives. NeoCore attaches it to the newest message, after the stable system prompt, so the cached prefix is untouched. neocore stats shows the real price under prompt_cost: per host, the memory that actually reached a chat (estimated tokens) next to the fresh input, cache reads and cache writes Claude Code and Codex recorded for their model calls in the same days. It reads only their usage counts, never the conversation text.

Rules check: your standing rules, at the moment of action

Recall finds what a prompt is about. A rule such as "never force-push" has to hold when nobody mentions it, so the rules check looks at what the AI is about to do instead: a tool call about to run, or the reply about to end its turn. It makes no model calls; each check is a few regular expressions with a 2-second limit, and any error lets the AI carry on.

# hold a matching shell command once, with your words, so the AI checks it against the rule
neocore rules add no-force-push --statement "Never force-push; open a pull request instead." \
  --tool @shell --input 'git\s+push\b.*--force'
# send a reply back once if it breaks the rule
neocore rules add ticket --statement "End every reply with the ticket number, like [T-123]." \
  --require '\[T-\d+\]\s*$'
# list it at every session start
neocore rules add spelling --statement "Use British spelling." --standing

neocore rules list        # every rule and whether it is live
neocore rules check --tool Bash --input "git push --force origin main"   # dry run
neocore rules stats       # how often each rule fired, and what the AI did next
neocore rules off         # pause it (no settings change); `neocore rules on` to resume
  • Hold once (--tool/--input): the first matching tool call in a turn is stopped with the rule and your words; if it still fits the rule, the AI runs it again and it goes through. --mode note lets it run with the rule as a reminder instead (Claude Code). Tool families: @shell, @write, @agent, @browser_builtin, @browser_chrome.
  • Send back once (--forbid, --require, --max-words, --max-items, with --when and --unless): at most once per turn of yours, never in a loop.
  • No rules, no hooks. neocore setup adds the rules hooks only while you have rules, and only the events they need; neocore rules add, remove and build keep them in line on every host NeoCore is set up on. neocore uninstall removes them with the others.

Rules live in ~/.neocore/rules/rules.source.json; edit it by hand and run neocore rules build. Only records build stamped ever fire. A rule can quote you from a transcript (--words "..." --source FILE --line N, or owner_source in the file); the build refuses it unless your words are on that line word for word. Every firing is logged locally in ~/.neocore/rules/log.jsonl.

NeoSift: the local relevance filter

Recall finds candidates by words and meaning, but many of them only share words with the prompt. NeoSift is a 32M-parameter cross-encoder that reads the prompt, the end of the turn before it and each candidate memory, and gives the chance that the memory would help. Only the best are injected (score >= 0.4, at most 12).

It was trained on real coding-assistant prompts whose candidate memories were graded by a frontier model (GPT-6.1). On 103 held-out real prompts, ranking useful memories above useless ones:

Scorer Where it runs Score
GPT-6.1 (the teacher) hosted 0.970
TypeSafe Jev 1.13 hosted, ~$0.0007 per prompt 0.931
NeoSift 32M your graphics card, free 0.914

On prompts where no memory was useful, NeoSift still let something through 40% of the time, against 74% for Jev. On 885 real prompts graded after their replies, the default cut-off injected 5.7 memories per prompt and caught 66% of the memories the replies needed. Raising the cut-off trades needed memories away about as fast as it saves space.

It runs on your graphics card. One prompt (48 candidates) takes 0.07 s on an RTX 3080. neocore setup installs it when it finds an NVIDIA card or Apple silicon, and only if a speed check passes:

neocore sift install      # or: neocore setup (does it when a graphics card is found)
neocore sift remove

It lives in ~/.neocore/sift: its own Python environment (torch, transformers, ~2-3 GB), the pinned model (~120 MB, hash-checked) and a server on 127.0.0.1 that keeps nothing. If it ever cannot answer in time, that prompt gets unfiltered recall instead of none. NeoSift is fine-tuned from Ettin (Apache-2.0); see NOTICE.

Help improve NeoSift (opt-in)

NeoSift gets better with more real prompts. neocore setup asks once:

Help improve NeoSift? If you say yes, NeoCore sends the prompts it recalls memory for, the end of the turn before each, the memories it offered and their scores, encrypted, to the NeoCore team. An AI model grades them and they are used only to train NeoSift, which outputs scores and cannot reproduce text. Your content is never used as knowledge, shared or sold. It is stored encrypted so future versions keep learning from it. Off by default. Stop any time with neocore share off, or remove everything you sent with neocore share delete.

What that means exactly (the code is share.py):

  • Sent: the prompt, your previous message (first 600 characters) and the end of the assistant's previous reply (last 800 characters), which is what NeoSift reads, and the memories recall offered with their scores, after NeoCore's usual secret redaction. Never the reply to the prompt, tool output or whole conversations. Prompts of fewer than three words are skipped (nothing to learn from), and at most 300 rows a day.
  • How: compressed, over HTTPS, in small batches, at most every six hours. On arrival each batch is encrypted with a key that only our training machine holds; the receiving service cannot read it back, and it keeps a batch only until the training machine has collected it. neocore share off also drops rows not yet sent.
  • Used for: grading by an AI model and training NeoSift. Nothing else.
  • Deleting: your install sends with a random secret id (in ~/.neocore/share/id; we store only its hash). neocore share delete deletes everything sent with it, including rows already collected for training (within a day), turns sharing off and starts a new id.

One memory across machines

Run the memory on one always-on machine (a home PC or a small VPS) and connect every other machine to it. Tell Claude Code on your laptop something once; Codex on your desktop knows it in its next chat's first message.

# on the machine that keeps the memory
neocore server init --person alex --device laptop --device desktop
# on each device, with the key file that device was given
neocore connect --url https://memory.example.com --key-file laptop.key

Each device has its own key, stored hashed on the server and revocable at once. Keys carry scopes, so one server can keep separate memories that never mix. Nothing is lost while the server is away: a device's transcripts are its queue. Admin commands (neocore server scopes, audit, export, forget) never show memory text unless asked to export it. One-command installers for Linux, macOS and Windows are in scripts/install/. Full guide: docs/shared-memory.md.

Quick start: Hermes Agent

NeoCore is a memory provider for Hermes Agent (0.22.2 or newer):

hermes plugins install VincentPorquet777/neocore/integrations/hermes
hermes memory setup          # pick "neocore"

Your own Hermes conversations (the CLI, the desktop app, and your own direct messages) join the same memory as Claude Code and Codex: this machine's after neocore setup, or your memory server after neocore connect. Hermes gets the same memory tools. Groups, and anyone else who messages your agent, keep a separate memory per chat and never see yours. Settings, what is stored and the one-time downloads are described in integrations/hermes.

Quick start: any assistant

from neocore import Memory

memory = Memory("memory.db")   # uses the embedder `neocore setup` downloaded, if present

memory.add(conversation="chat-1", user="I moved to Lisbon in May for the Feedzai job.",
           assistant="Congratulations on the move!", at="2026-05-03T10:00:00Z")
memory.add(conversation="chat-2", user="My card PIN hint is in the blue notebook.",
           scope="private")

result = memory.recall("Where do I work now?", scopes=["internal"])
print(result.rendered)   # dated, verbatim, budgeted block for your prompt
print(result.receipt)    # every delivered excerpt: evidence id + character offsets
  • memory.revoke(evidence_id, reason=...) hides a message until memory.store.restore(...).
  • memory.forget(evidence_id, reason=...) deletes the text and keeps an audit tombstone.
  • memory.abandon_branch(branch_id, reason=...) drops an edited-away branch.
  • memory.form_facts(ask) forms dated facts with any model: neocore.llm has Hermes CLI, Codex CLI, Claude CLI and OpenAI-compatible backends. Without an llm setting it uses the first one installed, in that order: Hermes on the model you set up there, then Codex or Claude Code on your own sign-in.

The only required dependency is the Python standard library. pip install neocore-memory[embed] adds dense recall (numpy, onnxruntime, tokenizers).

How it works

 your prompt ──► hook ──► warm daemon ──► Governed Recall ──► (optional filter) ──► context
                                          │  permitted?  scope · revoked · branch · revision
                                          │  rank        BM25 + bge-small, reciprocal-rank fused
                                          │  render      verbatim, dated, budgeted, receipts
 finished reply ──► sync ──► store (SQLite: immutable messages + access log)
                      └──► background, your own Codex/Claude sign-in:
                           facts (dated, cite their messages) · sleep (newest wins) · lessons
  • Store (neocore/store.py): one immutable row per message. An append-only access log covers revoke, restore and forget, and a branch log covers abandoned branches. Nothing is ever updated in place.
  • Recall (neocore/recall.py): permission is decided first. Ranking only ever sees permitted messages, so a forbidden message cannot "rank its way in".
  • Formation, sleep, lessons (neocore/assistant/): facts are add-only and cite their sources. Sleep judges groups of near-duplicate facts (current, history, superseded, outdated, duplicate) and every verdict can be undone. Lessons cite the facts they draw on.

More in docs/how-it-works.md and docs/governance.md.

Evals

Everything below runs through neocore.Memory and GovernedRecall from this repository. The recall step makes no model calls. Reader and judge are the only models. See evals/README.md to reproduce them.

Benchmark Questions NeoCore Reader / judge Recall p50 Cost
LoCoMo (10 conversations, categories 1–4) 1,540 87.5% gpt-4.1-mini / gpt-4o-mini 22 ms $2.42
LongMemEval-S 500 89.6% gpt-4.1-mini / gpt-4o (official prompts) 20 ms $1.52
Governance (leaks) 1,540 0 (control: 1,540) none 14 ms $0

By category:

LoCoMo LongMemEval-S
single-hop (841) 91.8% single-session-user (70) 98.6%
temporal (321) 88.2% knowledge-update (78) 92.3%
multi-hop (282) 82.3% temporal-reasoning (133) 91.7%
open-domain (96) 63.5% single-session-preference (30) 90.0%
single-session-assistant (56) 87.5%
abstention (30, overlaps the others) 86.7%
multi-session (133) 82.0%

Recall makes no model calls in every row. The cost is the reader and judge calls through OpenRouter.

Caveats, stated plainly:

  • Tuned on these benchmarks. Recall settings (budget, top-k, the 30% fact share) were tuned on a stratified pilot of LongMemEval-S and four LoCoMo conversations, so these are not fully held-out numbers.
  • Facts formed once. Facts were formed once per session with gpt-4o-mini and are reused here (evals/data/*facts*).
  • Lenient LoCoMo judge. Our LoCoMo judge prompt is generous about wording, like the Mem0 protocol, but it is our own prompt.
  • Others' headline figures use bigger models. Zep's 94.7% on LoCoMo uses gpt-5.4 to answer and to judge; Mem0's 94.4% (LongMemEval) and 92.5% (LoCoMo) do not state their answering model or judge. With the same small answering model as ours, published LoCoMo results range from 64% to 93%, and some systems score above NeoCore. We have not re-run them. The like-for-like comparison, with sources, is in Where NeoCore stands.

Status and limits

NeoCore 0.3 is beta.

  • Battle-tested scale is modest. The assistant integration has run daily on one developer's Claude Code and Codex history (thousands of turns), and the engine has run behind three production assistants. Scale tests on large corpora are still to come.
  • NeoSift runs on a graphics card (NVIDIA or Apple silicon). Other machines use the hosted scorer or unfiltered recall.
  • NeoSift has learned mostly from one developer's coding prompts so far. On two business assistants' prompts it agreed with its teacher less well (0.68 against 0.80, an earlier round). Opt-in sharing is how it learns everyone's.
  • Windows, macOS and Linux. The daemon and hooks are developed on Windows and use only the standard library elsewhere. Please report issues.

License

Apache-2.0. See LICENSE.

Metadata

Release files for neocore-memory 0.3.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for neocore-memory 0.3.5
File Size Uploaded Provenance Actions
neocore_memory-0.3.5.tar.gz 288.8 kB With provenance Details for neocore_memory-0.3.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for neocore-memory 0.3.5
File Interpreter ABI Platform Actions
neocore_memory-0.3.5-py3-none-any.whl Python 3 none any Details for neocore_memory-0.3.5-py3-none-any.whl

Total release size: 475.9 kB

Release files / neocore_memory-0.3.5.tar.gz

Download URL neocore_memory-0.3.5.tar.gz
Size 288.8 kB
Tags Source
SHA-256 checksum
How to use checksums
99cba4509af88b0c1261963ef17092a02f37560b5ca6520b71b786e72c54b05d
BLAKE2b-256 checksum
How to use checksums
4e7fcc4ea219924ce62f830e0c12405fed54f0f4d40990d5680f0756f994376f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Release files / neocore_memory-0.3.5-py3-none-any.whl

Download URL neocore_memory-0.3.5-py3-none-any.whl
Size 187.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
874a55315578df2233f12f10675d8ade4c5470cfc9f652f31a42241ba9a04f8d
BLAKE2b-256 checksum
How to use checksums
a34e8e4fb97e9c7869460252ced9060cbeb3a8b78cbc55decdf95f5d9f072887
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

Security for neocore-memory 0.3.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for neocore_memory-0.3.5.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page