Nexus
Permanent memory and search by meaning for Claude. Nexus runs on your computer. You need no API key, no account, and no separate database install. What Claude learns in one session is there in the next.
Install: follow the install guide at hellblazer.github.io/nexus. It has a version for Claude Code, for the nx CLI alone, and for Claude Desktop, on macOS, Linux and Windows.
The package on PyPI is conexus. The command it installs is nx.
Quick start
The common case: Claude Code on macOS or Linux, with uv and git already installed.
On macOS:
uv tool install conexus --python 3.12 # install nx; --python 3.12 is required, Python 3.14 does not work yet
nx self install # move nx to the layout Nexus manages
nx init # download and start the storage service; answer yes to start at login
nx doctor # every line must show ✓ ("credentials not set" is normal)
On Linux, the first command also names the CPU build of torch. Without --torch-backend cpu, uv installs the CUDA build on x86-64: 4.3 GB of downloads and 8 GB on disk that Nexus never uses. The flag needs uv 0.9.19 or newer (uv self update), and uv prints a warning that it is experimental.
uv tool install conexus --python 3.12 --torch-backend cpu
nx self install
nx init
nx doctor
Then start claude and type these two lines inside Claude Code, not in the terminal:
/plugin marketplace add Hellblazer/nexus
/plugin install conexus@nexus-plugins
The install guide has the requirements, the Windows path, the Claude Desktop extension, and how to index your first repository.
Update, remove, problems
- Update: run
nx self install, thennx upgrade. Do not update withuv tool install conexusor--force: that removes the local search model and search returns nothing. Details: Update Nexus. - Remove: Remove Nexus completely covers exporting your knowledge first, removing the Claude integration, and deleting the service and data.
- Problems: see Problems. If nothing there helps, paste the recovery runbook as the first message of a Claude Code session. It checks the install step by step and asks before it changes any data.
What you installed
One service on your computer: Postgres 17 with pgvector, holding three stores. Scratch lasts one session. Memory holds project facts. Knowledge holds everything you index: code, documents, PDFs, and the decisions you record. The search model runs locally, so your data does not leave the machine.
Once a day the MCP server sends one message with six values: a random install id, the conexus version, the install mode, operating system, CPU type, and Python version. No hostname, paths, collection names, or content. The service also keeps a keyed fingerprint of the network address the message came from, never the address itself; see the privacy policy. nx telemetry off stops it; nx telemetry status shows the setting.
Learn
- Getting started: twelve lessons, all done inside Claude Code.
- Working with RDRs: record a decision before you build, in eight lessons.
- Research with Nexus: what you say to Claude at each step of research work, and what you see.
- Research in Nexus: the thinking behind the method, what was borrowed from experimental science and what was left out.
- The Nexus Tuple Space: how sessions, agents, and hooks coordinate.
- Coordination: how sessions and agents coordinate through the tuple space, and which steps the hooks, the channel, and Claude each do.
- How Agents Build and Ship Nexus: how agent sessions, the conexus instance, GitHub and a second build machine coordinate through the tuple space to build, test, review and release Nexus.
- CLI reference, architecture, storage tiers, and the docs tree.
- Managed service, for a hosted deployment with server-side embeddings.
Push delivery into your session (Claude Code channels)
By default, a message that arrives while you are away — an agent's report, a peer session's reply — waits until your next prompt, when a hook delivers it. Claude Code's channel preview can push it into a running session instead, but only when the session is launched with a channel flag, every time; nothing Nexus installs can set that flag for you.
- Launch with
claude --channels plugin:conexus@nexus-plugins(no confirmation dialog once the plugin is on Claude Code's channel allowlist), orclaude --dangerously-load-development-channels server:nexus(works everywhere the preview does, with a one-keystroke confirmation dialog on every launch). - For the dialog-free form, put the plugin on the allowlist: on macOS, write
/Library/Application Support/ClaudeCode/managed-settings.json(admin-written) with{"channelsEnabled": true, "allowedChannelPlugins": [{"marketplace": "nexus-plugins", "plugin": "conexus"}]}. - Make it stick: add
alias claude='claude --channels plugin:conexus@nexus-plugins'to your shell's startup file. - Check it worked: the startup screen shows "Channels (experimental) messages from plugin:conexus@nexus-plugins inject directly in this session · restart without --channels to stop";
nx doctor'stuples.channel_deliveryrow reports the waiter's own status once it has run here (alive, last wake, messages announced and pending), or an informational "no record" line for a session whose waiter has not run yet.
Without the flag, mail still arrives at your next prompt through the drain hook — degraded, not broken. Channels are a Claude Code research preview, not available on Amazon Bedrock, Google Cloud Agent Platform, or Microsoft Foundry. See Coordination and Getting started for more.
License
Nexus, the nx command, and the plugin are free to use. The license covers the Nexus code only. Everything you make with it is yours: the repositories you index, the notes and memory Claude keeps, the documents you store, the RDRs you write, and anything Claude produces in a session are not covered by this license and carry no obligation from it.
The code is AGPL-3.0-or-later (LICENSE). That matters only if you modify Nexus itself and offer the modified version to others. Commercial licenses are available for organizations that need other terms; see LICENSING.md.
1 maintainer
Metadata
1 maintainer
Release files for conexus 7.76.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| conexus-7.76.0.tar.gz | 7.9 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| conexus-7.76.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 12.0 MB
Release files / conexus-7.76.0.tar.gz
| Download URL | conexus-7.76.0.tar.gz |
|---|---|
| Size | 7.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ff8b1e1ce0761e1052c4b9616eebdd464ee86c5e05fc16bd63ccc2fe6daa67a8
|
|
BLAKE2b-256 checksum How to use checksums |
c41ef3e369073c480d97a9c0b948dab653a76b821a03a4191961ba49dc9befa8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 9, 2026.
Transparency logRelease files / conexus-7.76.0-py3-none-any.whl
| Download URL | conexus-7.76.0-py3-none-any.whl |
|---|---|
| Size | 4.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3241ff7219f1a5ce959d063d2926fd5a626ba7c0d9a3c08dadd9018578f43d05
|
|
BLAKE2b-256 checksum How to use checksums |
2549543d56d0ef6ea44049976bdd8eaeb08a59358bb7fec5f01b90338b587af6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 9, 2026.
Transparency log
