// Use when setting up, checking, or connecting Cognee through the cognee CLI from Codex.
Use when ingesting, cognifying, or querying a codebase with Cognee CLI from Codex.
Use when launching, checking, or reporting on the local Cognee UI/backend through cognee-cli -ui.
Use when Codex should remember, recall, search, improve, or forget information using the Cognee CLI.
Store data permanently in the Cognee knowledge graph. Accepts a data category (user, project, or agent) to tag the data with the correct node_set for filtered retrieval.
Search Cognee memory. Session memory is automatically searched on every prompt via hooks. Use this skill explicitly for permanent knowledge graph search, filtered category search, or when you need more results than the automatic lookup provides.
Sync session cache entries into the permanent Cognee knowledge graph. Run this to make session memory searchable, or it runs automatically at session end.
| name | setup |
| description | Use when setting up, checking, or connecting Cognee through the cognee CLI from Codex. |
Use this skill when the user asks to configure Cognee, check whether Cognee is ready, connect to a local or cloud Cognee instance, or inspect CLI capability.
uv run cognee-cli ... as the primary interface..env, config files, shell history, or command output.Start with the local command surface:
uv run cognee-cli --help
uv run cognee-cli --version
If dependencies are missing, use the repository command:
uv sync --dev --all-extras --reinstall
Inspect configuration without exposing values:
uv run cognee-cli config list
Use config get <KEY> only for non-secret settings. For secret-like keys,
report whether the key appears configured rather than showing the value.
For a local backend:
uv run cognee-cli serve --url http://localhost:8000
For a hosted instance with an API key, do not paste the key into the transcript. Use an environment variable or an already configured credential.
To disconnect:
uv run cognee-cli serve --logout
When the user wants concurrent or multi-agent use, prefer a running Cognee API server and pass:
uv run cognee-cli --api-url http://localhost:8000 <command>
For isolated session history and permissions, include:
uv run cognee-cli --user-id <uuid> <command>