Skip to content

Conversation

@Abdulnaser97
Copy link

I was trying to understand how cognee works under the hood so I created a diagram for it using code-canvas.com. I think it will be pretty helpful for contributors to quickly onboard to the inner-works of cognee.

Here is the generated diagram for cognee grouped by the application's use-cases and their runtime data flows:
Open cognee's interactive diagram

image image

I built code canvas to simulate a senior engineer who have been working on cognee's codebase for pretty long and can explain to you any functionality of the repository visually through diagrams.

Here is what users are saying about codecanvas

"I used to spend 4 hours asking GPT how a use case in a codebase works and I keep going back and forth until I am able to draw a diagram to summarize my understanding,
CodeCanvas gives me that diagram in 40 seconds"


Some Notes:

  • The diagram is already generated for cognee, completely free, no monthly subscription. Consider it as my contribution to help fellow contributors lower their context onboarding friction before they can start contributing.
  • The diagram file is stored in the repository itself, so the readme link will only work after merging. Until then, you can view the diagram from the link I shared above.
  • Read the 1 pager guide to learn how to refine simulations to capture specific codebase logics you might want to cover.
  • I am aware the mapping to the source code is shiften a couple lines off in some cases, I am working on fixing the bug asap.
  • You can reach me out anytime on discord discord.gg/t3ezMyMPqr

@pull-checklist
Copy link

Please make sure all the checkboxes are checked:

  • I have tested these changes locally.
  • I have reviewed the code changes.
  • I have added end-to-end and unit tests (if applicable).
  • I have updated the documentation and README.md file (if necessary).
  • I have removed unnecessary code and debug statements.
  • PR title is clear and follows the convention.
  • I have tagged reviewers or team members for feedback.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 30, 2025

Walkthrough

This PR adds a new "How does cognee work under the hood?" subsection to the README.md's Hosted platform section, featuring two external walkthrough links and an embedded CodeCanvas screenshot for visual reference. No functional code changes.

Changes

Cohort / File(s) Summary
Documentation Updates
README.md
Added new "How does cognee work under the hood?" subsection under Hosted platform with external walkthrough/tutorial links and embedded CodeCanvas screenshot

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

  • Content addition only; verify link validity and screenshot relevance
  • No code logic or dependencies to validate

Possibly related PRs

Suggested reviewers

  • Vasilije1990
  • dexters1
  • borisarzentar

Poem

🐰 A README grows with wisdom new,
Links and screenshots, shiny too!
Under the hood, the docs now gleam,
Helping users chase the dream!

Pre-merge checks and finishing touches

❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Description Check ⚠️ Warning The PR description provides a human-generated explanation of the change with clear intent and includes screenshots as required. However, the description is missing several key sections from the repository's template: the "Type of Change" section (where the author should specify this is a "Documentation update"), the "Pre-submission Checklist" with its multiple governance checkboxes, and the "DCO Affirmation" statement. While the core descriptive content is present and meaningful, the structural template elements are largely absent, which means the submission does not follow the expected format for pull request documentation in this repository. To address this, the author should revise the PR description to include all required template sections: explicitly select "Documentation update" under Type of Change, complete the Pre-submission Checklist by checking relevant boxes that apply to this change, and add the DCO Affirmation statement at the end. These additions will ensure the submission follows the repository's established pull request format and governance requirements.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. You can run @coderabbitai generate docstrings to improve docstring coverage.
✅ Passed checks (1 passed)
Check name Status Explanation
Title Check ✅ Passed The title "Added interactive CodeCanvas diagram for cognee" is concise, clear, and directly corresponds to the main change in the pull request. According to the raw summary, the PR adds a new subsection with walkthrough links and an embedded CodeCanvas screenshot to the README, which is accurately captured by the title. The title is specific about what was added without being vague or overly broad, making it easy for reviewers scanning the history to understand the primary change.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @Abdulnaser97, thank you for submitting a PR! We will respond as soon as possible.

Removed extra blank lines before 'Self-Hosted (Open Source)' section.
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 464d35c and 9a1af2c.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.18.1)
README.md

95-95: Link text should be descriptive

(MD059, descriptive-link-text)


97-97: Link text should be descriptive

(MD059, descriptive-link-text)

Comment on lines +93 to +99
### How does `cognee` work under the hood?

Check out this interactive walkthrough of the `cognee` codebase on CodeCanvas [here](https://www.code-canvas.com/?session=unauthenticatedGithub&repo=cognee&owner=topoteretes&branch=main&OnboardingTutorial=true).

To refine existing dataflow simulation or create new ones, follow the quick tutorial [here](https://docs.code-canvas.com/updating-diagram).

<img width="1916" alt="CodeCanvas Screenshot" src="https://codecanvas-media-public.s3.amazonaws.com/images/codecanvas-readme-screenshot.png" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Improve link text descriptiveness for better accessibility.

Lines 95 and 97 use generic "here" link text, which violates markdown best practices (MD059). Consider rephrasing the links to be more descriptive of their content.

For example:

  • Line 95: Instead of "here", link text could reference the specific walkthrough purpose (e.g., "interactive CodeCanvas walkthrough").
  • Line 97: Instead of "here", link text could indicate the content (e.g., "CodeCanvas tutorial for refining diagrams").

This improves both readability and SEO while maintaining the section's clarity.

Apply this diff to improve link text:

-Check out this interactive walkthrough of the `cognee` codebase on CodeCanvas [here](https://www.code-canvas.com/?session=unauthenticatedGithub&repo=cognee&owner=topoteretes&branch=main&OnboardingTutorial=true).
+Check out this [interactive CodeCanvas walkthrough of the cognee codebase](https://www.code-canvas.com/?session=unauthenticatedGithub&repo=cognee&owner=topoteretes&branch=main&OnboardingTutorial=true).

-To refine existing dataflow simulation or create new ones, follow the quick tutorial [here](https://docs.code-canvas.com/updating-diagram).
+To refine existing dataflow simulation or create new ones, follow the [CodeCanvas tutorial for updating diagrams](https://docs.code-canvas.com/updating-diagram).
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)

95-95: Link text should be descriptive

(MD059, descriptive-link-text)


97-97: Link text should be descriptive

(MD059, descriptive-link-text)

🤖 Prompt for AI Agents
In README.md around lines 93 to 99, the two links use generic "here" text which
hurts accessibility and SEO; replace the link text on line 95 with a descriptive
phrase like "interactive CodeCanvas walkthrough" (so the link reads something
like Check out this interactive walkthrough of the `cognee` codebase on
CodeCanvas — interactive CodeCanvas walkthrough) and replace the link text on
line 97 with a descriptive phrase like "CodeCanvas tutorial for refining
diagrams" (so the quick tutorial link explicitly names the tutorial purpose);
keep the URLs and surrounding sentence structure unchanged.

@Vasilije1990
Copy link
Contributor

Thank you, won't be merged

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants