cognee.serve(). Once connected, all operations (remember, recall, forget, improve) route to the remote instance instead of running locally.
Connect to Cognee Cloud
~/.cognee/cloud_credentials.json. Subsequent calls to cognee.serve() reconnect without re-authenticating until the token expires.
Connect to any instance
For self-hosted or staging environments, pass the URL and API key directly:Local-to-local connections
Connect to a Cognee backend on the same machine or local network:cognee serve before connecting.
Usage after connection
Once connected, all SDK operations execute on the remote instance:The local UI in Cognee Cloud automatically detects running local instances on
localhost:8000 and shows their connection status.Push a prebuilt graph instead of raw data
Connecting withserve() and re-running remember() makes the remote instance
rebuild the knowledge graph. If you have already built the graph locally and want to
avoid re-deriving it (and the LLM cost that comes with it), use
cognee.push() instead. It exports the dataset’s graph as a
COGX archive and imports it on the remote
instance, preserving your local entities and relationships:
cognee push.