check_ingestion_status
ChatGPTCheck the progress of background ingestion started by remember(background=True). Reports active and completed pipeline jobs for a dataset, including failures that a backgrounded call could not return inline.
Overview
Cognee gives ChatGPT a memory that lasts beyond one conversation. Everything you ask it to remember goes into your own Cognee Cloud workspace, where it is turned into a knowledge graph: entities, relationships and summaries, not just stored text. Later, in any conversation and from any client connected to the same workspace, ChatGPT can recall it with search that uses that structure, so answers draw on how facts connect rather than on keyword matches alone. Four tools: - remember: store text, or a file up to 10 MB, into a dataset. Cognee ingests it, extracts entities and relationships, and builds the graph. - recall: search your memory with a natural-language question. Cognee routes it to the right retrieval strategy and returns an answer with the supporting memories, or the raw matching passages if you ask for them. - forget: delete one item, one dataset, or everything you own. - cognify_status: check on ingestion that was started in the background. Memories are organised into datasets. By default ChatGPT writes to a dataset of its own, so what ChatGPT remembers stays separate from what your other tools remember, while recall searches across all of them. Name a dataset in the conversation to use a specific one. You sign in with your Cognee account; no API key is pasted anywhere. Each call runs against your workspace with your own identity and permissions. Workspaces that have been idle go to sleep; the first call after a quiet period wakes one and can take about a minute. Cognee is open source (github.com/topoteretes/cognee). This plugin is the hosted version of the Cognee MCP server, run by Cognee for Cognee Cloud workspaces. A Cognee Cloud account with a workspace is required.
Tools
forget
ChatGPTDelete data from memory. Can target a single data item, a specific dataset (by name or id), or everything the user owns. Removes data from the relational DB, graph DB, and vector DB.
recall
ChatGPTSearch memory with auto-routing and session awareness. When session_id is provided without datasets or search_type, searches session cache first by keyword matching. Falls through to the permanent knowledge graph if no session results match. Auto-routing picks the best search strategy when search_type is not specified.
remember
ChatGPTStore data in memory. Two modes depending on whether session_id is provided: Without session_id (permanent memory): Runs the full add + cognify pipeline to ingest data and build the knowledge graph, then the self-improvement loop (improve) unless self_improvement=False. With session_id (session memory): Stores the data in the session cache. Direct mode may also bridge it to the graph in the background; API mode uses typed cache entries and does not bridge to the graph. Omit session_id when the content should be stored as permanent graph memory. Pass either
data (text) or filename + content_base64 (a file upload, up to 10 MB), not both. File uploads are permanent-memory only and don't support session_id.Capabilities
Writes
Example Prompts
Click any prompt to copy it.
