Cognee

Plugin cognee in topoteretes/cognee-integrations. Commands read from the repo's manifest — yesterday.

Skills (10)

• codebase

  Use when indexing a code repository into Cognee's code graph or querying it (callers, impact analysis, paths, endpoints) from Codex.

• cognee-digest

  A multi-day digest of the user's own coding-agent sessions — sessions per day and project, most-edited files, and every lesson Cognee distilled into the knowledge graph in that window. Use only when the user explicitly asks for a weekly digest, a retro, a recap or report of their recent sessions, or

• cognee-forget

  Forget data stored in Cognee memory. Use when the user asks to forget, delete, or remove something from memory (e.g. "forget what we talked about tennis", "delete that from memory"). Finds the documents in the current dataset whose raw content matches what the user wants forgotten and deletes them.

• cognee-keys

  Manage the API keys of this plugin's Cognee agent, one per machine. Use when the user asks to list, clean up or revoke Cognee plugin keys, when a session start says this machine is on the personal key because the agent is full, or when "cognee keys" / "key limit" / "revoke a key" comes up.

• cognee-standup

  A standup or status update built from the coding-agent sessions Cognee recorded — prompts, tool calls, edited files, what was left open — per project. Use only when the user explicitly asks for a standup, a status update, a catch-up on their own recent sessions ("what did I work on yesterday / this

• cognee-switch-datasets

  Use when the user wants to switch this Codex session to another Cognee dataset (saves go there, recall is restricted to it), see which datasets are available, move memory capture to a different dataset, pin recall to the active dataset ("only recall from this dataset"), or set recall back to auto ("

• cognee-timeline

  A dated chronology of one topic across the user's recorded coding-agent sessions — the lessons the graph learned about it and the prompts that named it, oldest first. Use only when the user explicitly asks for the history or timeline of a topic across their sessions ("how did X evolve", "when did we

• local-ui

  Use only when the user explicitly asks to launch or inspect the LOCAL Cognee UI (the cognee-cli dev UI). For "is Cognee running/connected" or any configuration question, use the setup skill instead. Does not apply in cloud mode.

• memory

  Use when Codex should remember, recall, search, improve, or forget information using Cognee.

• setup

  Use when configuring the Cognee connection, checking whether Cognee is ready or connected, or diagnosing a local or cloud Cognee instance from Codex.

Similar plugins