Skip to main content
Archived

This project has been archived by its maintainers, and is no longer receiving any updates.

langchain-goodmem

Use GoodMem from LangChain for document ingestion, retrieval, and agent memory. GoodMem handles storage, chunking, embeddings, and optional reranking.

Version 0.2 intentionally breaks compatibility with 0.1. See CHANGELOG.md for migration details.

Install and connect

Requires Python 3.10+, a running GoodMem server, an API key, and a space configured with an embedder.

pip install langchain-goodmem
export GOODMEM_BASE_URL="http://localhost:8080"
export GOODMEM_API_KEY="your-key"

Retrievers and tools read these environment variables. You can also pass a configured goodmem.Goodmem instance as client=; you retain ownership of it.

Write Documents and retrieve

import os
from goodmem import Goodmem
from langchain_core.documents import Document
from langchain_goodmem import GoodMemRetriever, add_documents

space_id = "5f6b1c2e-8a4d-4e3b-9c7a-2d1e0f9a8b7c"  # your space's UUID
with Goodmem(
    base_url=os.environ["GOODMEM_BASE_URL"],
    api_key=os.environ["GOODMEM_API_KEY"],
) as client:
    memory_ids = add_documents(client, space_id, [
        Document(
            page_content="Project Cobalt's launch owner is Ada.",
            metadata={"source": "https://example.org/cobalt", "team": "blue"},
        )
    ])

retriever = GoodMemRetriever(space_ids=[space_id], k=5, metadata_filter={"team": "blue"})
for document in retriever.invoke("Who owns Cobalt's launch?"):
    print(document.page_content, document.metadata["source"])

add_documents batches text and metadata through the SDK and waits for indexing by default. Set wait=False for background ingestion, then use wait_for_memory(client, memory_id) when readiness matters. Optional Document IDs must be UUIDs; existing IDs produce conflicts. GoodMemIngestionError.created_memory_ids identifies successful writes if part of ingestion fails.

metadata_filter pairs must all match; values are escaped and typed. Build richer filters with langchain_goodmem.filters (all_of, compare, one_of); never format user input into filter. Empty results return immediately.

The retriever returns Documents with source metadata, memory/chunk/space IDs, and scores. It supports LCEL, callbacks, batching, per-call k, and ainvoke through LangChain's thread executor.

If the server reports a real problem during a search — a reranker was unavailable, one space was unreachable — the Documents it did return are still returned, and each carries metadata["goodmem_partial"] = True and metadata["goodmem_statuses"] saying why. A problem that left no Documents at all returns an empty list and emits a UserWarning and a warning log line with the statuses, so it is distinguishable from a search that matched nothing. Neither case raises. Notices that carry no loss (FEATURE_DISABLED, LLM_CAPABILITY_INFERRED) are dropped; a status code this version does not know is reported as UNKNOWN.

For reranking, set reranker_id and optionally fetch_k=20. Reranking requires no LLM.

Give an agent a search tool

from langchain_core.tools import create_retriever_tool

tool = create_retriever_tool(
    retriever, "search_project_records", "Search project records.",
    response_format="content_and_artifact",
)

The agent supplies only a query. Spaces and filters remain configured by the developer. Retrieved Documents are available in ToolMessage.artifact for citations.

Other tools and development

The package also provides space/memory management tools. GoodMemRetrieveMemories returns SDK events, including chunks, optional summaries, and statuses; GoodMemRetriever flags incomplete retrieval on the Documents' metadata rather than raising. Tools use SDK data shapes and LangChain ToolException handling.

IDs must be UUIDs because the SDK puts them unescaped into URL paths. Model file uploads need GoodMemCreateMemory(upload_dir="/srv/uploads"), confined there, symlinks resolved.

See the smoke example for a complete workflow.

uv sync --all-groups
uv run pytest --disable-socket --allow-unix-socket tests/unit_tests
uv run ruff check .
uv run mypy .

Metadata

Release files for langchain-goodmem 0.2.3

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

Source distribution (sdist)

Source distribution for langchain-goodmem 0.2.3
File Size Uploaded
langchain_goodmem-0.2.3.tar.gz 163.3 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for langchain-goodmem 0.2.3
File Interpreter ABI Platform
langchain_goodmem-0.2.3-py3-none-any.whl Python 3 none any Details

Total release size: 190.8 kB

Release files / langchain_goodmem-0.2.3.tar.gz

Download URL langchain_goodmem-0.2.3.tar.gz
Size 163.3 kB
Tags Source
SHA-256 checksum
How to use checksums
d268d124edb5c3c1a429d6e29352e74e59a5bcb9656797f9ed9e9788c116b134
BLAKE2b-256 checksum
How to use checksums
8ef10499fc7f4cbdeb4d47c487e0323504d7d6bbffae0e2864b063f1fc9b5de2
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 Sep 28, 2026.

Transparency log

Release files / langchain_goodmem-0.2.3-py3-none-any.whl

Download URL langchain_goodmem-0.2.3-py3-none-any.whl
Size 27.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c0be10db2dffcafcffdac873a5621dd936a23f1402a9857bd74383878d679060
BLAKE2b-256 checksum
How to use checksums
692a7ceb9f89170a6ab8a49ec1fc4d5ec1466eef4010fb21b8a0bd43c81de12f
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 Sep 28, 2026.

Transparency log
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