Practical overview
When it fits
Consider Null Drift when building an agent that needs thread-separated state accumulation, recall, or checkpointing, particularly when the project’s Rust services and listed CrewAI or LangGraph adapters suit your architecture.
Who it is for
- Developers adding persistent episodic memory to AI agents.
- Teams using CrewAI or LangGraph that want to explore the listed adapters.
- Builders who want to manage agent state through thread-isolated HTTP operations.
Documented uses
- Add text and a salience value to an agent thread’s memory.
- Request a thread’s dominant state for use in an agent workflow.
- Save an active memory index to a binary checkpoint and restore it to daemon memory.
- Explore reducing model context tokens by accumulating state rather than repeatedly supplying a growing event history.
Requirements & limits
The repository is public and identifies an AGPL-3.0 license.
- The architecture has distinct daemon and gateway services; the README’s Docker Compose command starts both.
- The gateway path uses fastembed with ONNX Runtime, while the README also describes injecting embeddings directly into the daemon.
- CrewAI and LangGraph adapters are listed; the excerpt does not provide their setup instructions.
- The README reports token, latency and memory benchmarks, but these are project claims rather than independently confirmed results.
- The project is licensed under AGPL-3.0, which may affect how developers can use or distribute modifications.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start the services with Docker Compose
Build and start the documented Null Drift backend and gateway using Docker Compose.
Before you start
- Docker Compose, as required by the README command.
- The Null Drift repository, including its Compose configuration.
Steps
From the repository, run the command below.
docker compose up --build -dUse the gateway exposed at
http://localhost:8000, as described in the README.
Expected outcome
The README says this starts the nulld backend and exposes the gateway on localhost:8000.
Guide limitations
- This documented setup procedure does not cover agent integration or demonstrate that a particular deployment succeeds.
Inject and recall a thread’s memory
Use the documented gateway examples to add a memory item to a thread and request its dominant state.
Before you start
- A running Null Drift gateway reachable at
http://localhost:8000. - A thread ID to use in the request query parameter.
Steps
Send a POST request to
/inject?thread_id=agent_007with JSON text and a salience value, following the README example.Send a GET request to
/recall?thread_id=agent_007to request the thread’s dominant state.
Expected outcome
The requests add an item to the named thread and ask the gateway to return its dominant state.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- CodNoob100/null-drift · Official homepage title · retained in its source language

