Memory with something to back it up.
Local memory for agents,
with the evidence attached.
Open source. Built on SQLite.
“Use SQLite for the portable build.”
“Let’s use SQLite for the portable build. It keeps setup simple.”
Illustrative conversationCLI MCP HTTP Local workspace
Keep the
source close.
A useful memory needs context. bigfeels keeps the evidence behind each saved fact. The memory record tracks when the fact is valid and how it has been revised. When something changes, you can correct the record.
Follow a memory through.
Choose a step to see the explicit lifecycle. This example runs in your browser with sample data. It does not save anything.
Read the memory contractbigfeels-mem remember \
"Use SQLite for the portable build." \
--space project:portable --kind decisionUse SQLite for the portable build.
Fits the tools
you use.
Start with the Python engine.
Add the interface your agent needs.
Know what
stays local.
Your store is a local SQLite database. Explicit saves and recall work without a model provider.
Automatic capture depends on the host integration. Generic MCP cannot see every conversation. Processing queued observations needs an extraction provider, which may send evidence to a remote model if you configure one.
Spaces constrain access within integrations. They are not an OS sandbox. Use separate private data directories or OS accounts for separate people.
Deletion has a review step: preview the affected records, then confirm with a short-lived token.
Read the operational detailsGive your agent
something to remember.
Install the preview from source.
Python 3.11+ and SQLite FTS5 are required.
git clone https://github.com/promptclickrun/bigfeels.git
cd bigfeels
python3 -m venv .venv
. .venv/bin/activate
python -m pip install .
bigfeels-mem --helpNo package registry release yet. The Python core has no mandatory third-party runtime dependencies.
Full installation guide