Use when the user wants to drive cognee from the terminal with cognee-cli — remember/recall/forget/improve memory commands, managing datasets and config, or database migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to connect cognee to external services — switching LLM or embedding providers (OpenAI, Azure, Gemini, Anthropic, Ollama, OpenRouter), changing databases (Postgres, PGVector, Neo4j, Neptune, Turso), S3 storage, or the MCP server for IDE integration.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
All integration config is environment variables (.env). The authoritative,
always-current list with commented examples is .env.template at the repo
root — check it before inventing variable names. Install the matching extra
before switching a backend (e.g. pip install cognee[postgres]).
Default is OpenAI (LLM_API_KEY is all you need). To switch, set
LLM_PROVIDER, LLM_MODEL, LLM_API_KEY, and (where relevant)
LLM_ENDPOINT / LLM_API_VERSION:
LLM_PROVIDER=azure, LLM_MODEL=azure/gpt-4o-mini, endpoint + api version required.LLM_PROVIDER=gemini, LLM_MODEL=gemini/gemini-2.0-flash-exp.cognee[anthropic]): LLM_PROVIDER=anthropic, model e.g. claude-3-5-sonnet-20241022.cognee[ollama]): LLM_PROVIDER=ollama, LLM_ENDPOINT=http://localhost:11434/v1, and set the embedding block + HUGGINGFACE_TOKENIZER too.LLM_PROVIDER=custom with the provider's OpenAI-compatible endpoint.cognee[aws]): LLM_PROVIDER=bedrock + AWS credentials/region.The classic trap: LLM and embeddings are configured independently
(EMBEDDING_PROVIDER, EMBEDDING_MODEL, EMBEDDING_ENDPOINT,
EMBEDDING_API_KEY). Configuring only one leaves the other on OpenAI —
either keep a valid OpenAI key or configure both.
DB_PROVIDER): sqlite (default) or postgres
(cognee[postgres]; host/port/user/password/name via DB_* vars).VECTOR_DB_PROVIDER): lancedb (default), pgvector
(cognee[postgres], needs VECTOR_DB_URL), neptune_analytics
(cognee[neptune]), turso (cognee[turso]). Anything else (ChromaDB,
Qdrant, Weaviate, Milvus, …) lives in community adapters — install from
https://github.com/topoteretes/cognee-community and register with
use_vector_adapter before use; setting VECTOR_DB_PROVIDER alone raises
"Unsupported vector database provider".GRAPH_DATABASE_PROVIDER): ladybug (default), neo4j
(cognee[neo4j], bolt URL + credentials), neptune (cognee[neptune]),
ladybug-remote, postgres (no raw Cypher / natural-language search).The repo docker-compose.yml ships ready-to-use postgres (pgvector) and
neo4j profiles with matching default credentials. From a container, reach
host services with DB_HOST=host.docker.internal.
cognee[aws]): STORAGE_BACKEND=s3 + bucket/credentials,
and point DATA_ROOT_DIRECTORY/SYSTEM_ROOT_DIRECTORY at s3:// paths.CACHE_BACKEND = sqlite (default) | postgres | redis | fs | tapes.ONTOLOGY_FILE_PATH to an OWL file, resolver/matching via
ONTOLOGY_RESOLVER / MATCHING_STRATEGY.docker compose --profile mcp up starts the MCP server on port 8001
(Streamable HTTP at http://localhost:8001/mcp), built from cognee-mcp/. Point Cursor / Claude Desktop /
Claude Code at it to use cognee memory from the IDE. Configure its DB_* env
to match the main service so both see the same data.
Embeddings from different models are not comparable — after switching the
embedding provider or model, reset local state (cognee-cli forget --all or
await cognee.forget(everything=True)) and re-ingest with remember().
To drop just the graph and vectors while keeping the ingested files, use
await cognee.forget(dataset="my_project", memory_only=True) — the dataset can
then be rebuilt under the new embedding model without re-uploading anything.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Use when the user wants to drive cognee from the terminal with cognee-cli — remember/recall/forget/improve memory commands, managing datasets and config, or database migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user needs something that ships outside cognee core — community database adapters (Qdrant, Milvus, Weaviate, Redis, Pinecone, FalkorDB, Memgraph, DuckDB, NetworkX, …), data-source connectors (Slack, Gmail, Notion, Confluence, Google Drive), custom tasks/pipelines/retrievers (Exa, ScrapeGraph, codify), Keywords AI observability — or wants to contribute a package to the cognee-community repo.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defining the shape of cognee's knowledge graph with graph_model= — writing DataPoint node classes, choosing identity and index fields so nodes merge and are searchable, declaring typed Edge fields and FromIdentity references, building a model from a JSON schema, or debugging duplicated nodes, missing edges, or InvalidReferenceTypeError.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building your own cognee processing — writing custom tasks, chaining them into a pipeline with run_custom_pipeline or the lightweight run_pipeline (from cognee.pipelines import run_pipeline), storing custom DataPoints with add_data_points, running custom extraction/enrichment over the existing graph with memify, checking pipeline run status, or debugging how data flows between tasks (batch_size, data_per_batch, ctx, Drop, enriches).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to run cognee with Docker or docker compose — trying it out from the prebuilt image, starting the API server in a container, or bringing up the full stack (UI, MCP, Postgres, Neo4j) with compose profiles.
日本語の概要は準備中です。原文の説明を表示しています。
Use when removing data from cognee memory with forget() in the SDK, HTTP API, or CLI — finding which dataset and document hold the content to delete (listing datasets and data items, reading raw content), choosing between deleting one document, a whole dataset, or only the graph/vector memory, and doing it safely.
日本語の概要は準備中です。原文の説明を表示しています。