// Use when launching, checking, or reporting on the local Cognee UI/backend through cognee-cli -ui.
Use when ingesting, cognifying, or querying a codebase with Cognee CLI from Codex.
Use when Codex should remember, recall, search, improve, or forget information using the Cognee CLI.
Use when setting up, checking, or connecting Cognee through the cognee CLI from Codex.
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 | local-ui |
| description | Use when launching, checking, or reporting on the local Cognee UI/backend through cognee-cli -ui. |
Use this skill when the user asks to launch the local Cognee UI, check whether Cognee is running, or report how well the UI/backend work.
uv run cognee-cli -ui as the primary launcher.From the Cognee repository root:
uv run cognee-cli -ui
Expected local surfaces:
Backend: http://localhost:8000
Frontend: http://localhost:3000
Backend:
curl -i http://localhost:8000/health
Frontend:
curl -i http://localhost:3000/
Useful route checks:
curl -i http://localhost:3000/dashboard
curl -i http://localhost:3000/datasets
curl -i http://localhost:3000/search
curl -i http://localhost:3000/knowledge-graph
If authenticated checks are needed, use the repository's documented local test credentials only when appropriate and do not expose real user credentials.
Report: