Ask questions about your journal, Obsidian vault, or other text notes, and continue conversations that remember earlier chats. The companion uses cognee memory with local databases, reads your notes without changing them, and saves conversations for later reference.
Chat with a companion that knows your notes folder (a journal, an Obsidian vault, any .md or .txt files) and every earlier chat, using cognee memory with local databases. Use when someone wants to ask questions about their own notes, or to talk with a companion that remembers past conversations. Runs locally; reads the notes folder, writes only to cognee's memory.
Review the instructions the agent will receive before you install.
Runs the self-hosted companion cookbook in examples/cookbooks/self_hosted_companion/. It
remembers a notes folder in the cognee dataset self_hosted_companion, then answers
messages about it; each chat is saved to memory, so a later one knows it. Setup, the
scripts and what each one does are in the cookbook's
README.md.
Run every command from the repo root.
Without a notes folder of the user's own, or to see it work first, leave out <folder>
below: the run then uses sample notes (the [setup] line says so). It needs only
LLM_API_KEY. Tell the user the answer comes from sample notes.
uv run python examples/cookbooks/self_hosted_companion/self_hosted_companion.py --check <folder>
with the notes folder the user named.
[setup] MISSING: line names one fix. Tell the user which line to fix,
using the README's "What it needs" table, and stop.--ask:
uv run python examples/cookbooks/self_hosted_companion/self_hosted_companion.py <folder> --ask "...".
Once the folder is remembered, later messages only need
uv run python examples/cookbooks/self_hosted_companion/scripts/chat.py --ask "...".[chat] companion>. Give it to the user. Each --ask is
its own chat session, saved to memory, so a later one knows it.self_hosted_companion.py exits 1 with a line naming what went
wrong. Run that script from examples/cookbooks/self_hosted_companion/scripts/ on its
own to look closer..env.self_hosted_companion before it ingests (the [clear]
line). On the user's own data, pass --clear only when they asked to start over: it
forgets everything the dataset holds, including the earlier chats.--ui unless the user asked to browse the graph: it keeps running until
Ctrl+C.uv run cognee-cli forget --dataset self_hosted_companion
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Operate cognee from the terminal to store, retrieve, update, and remove information. Covers dataset and configuration management, ingestion cost estimates, session history access, and commands for inspecting or applying database migrations.
Connect cognee to additional databases and data sources through community packages. The skill covers installing and registering adapters, importing data through connectors, configuring monitoring, and developing extension packages with examples and tests.
Define custom entities and relationships in cognee, a memory system for AI applications. This skill guides model design, identity matching, searchable fields, and troubleshooting when entities are duplicated or relationships are missing.
Build custom cognee processing by chaining Python tasks, defining data types, and saving results to graph and vector databases. Use it to enrich existing data, inspect run status, and troubleshoot how tasks pass data.
Run cognee in Docker, starting with a prebuilt image for local document ingestion and questions. It also covers Docker Compose profiles for adding the UI, MCP server, Postgres, and Neo4j, plus persistent data storage.
Find and remove stored content from cognee using its SDK, HTTP API, or CLI. Inspect documents before deletion, choose document or dataset removal, or keep raw files while clearing derived graph relationships and search vectors.