Connect a company SQL database, support ticket exports, and documents in cognee, linking shared people, teams, and projects so questions about ownership, decisions, and ongoing work can draw on several sources together.
Build one company memory from a SQL database, a support ticket export and a folder of documents, linked into one graph by cognee, then answer questions that need several of those sources together. Use when someone wants to connect their company's database, tickets and docs, or asks who owns, decided or is handling something across them. Runs locally; reads the sources, writes only to cognee's memory.
Review the instructions the agent will receive before you install.
Runs the company brain cookbook in examples/cookbooks/company_brain/company_qa/. It
remembers a SQL database, a ticket export and a docs folder in the cognee dataset
company_qa, extracts them with one graph model so the same person, team or project
becomes one node, then answers a question across them. Setup, the scripts and what each
one does are in the cookbook's
README.md.
Run every command from the repo root.
[setup] line says so). Tell the user the answer comes from sample data.uv run python examples/cookbooks/company_brain/company_qa/company_qa.py --check
with the sources (--database URL [--tables a,b] --tickets FILE [FILE ...] --docs FOLDER), or
none for the sample.
[setup] MISSING: line names one fix. Don't create credentials yourself.
Tell the user which line to fix, using the README's "What it needs" table, and stop.--check, adding the user's question as
--ask "...". On the sample with no --ask, it asks a question that needs all three
sample sources.[ask] A:. Give it to the user. The [ingest] lines
say which sources went in.uv run python examples/cookbooks/company_brain/company_qa/scripts/ask.py "...".company_qa.py exits 1 with a line naming what went wrong. Run
that script from examples/cookbooks/company_brain/company_qa/scripts/ on its own to
look closer..env or a database URL's password.company_qa 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.--ui unless the user asked to browse the graph: it keeps running until
Ctrl+C.uv run cognee-cli forget --dataset company_qa
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.