[Feature]: DeepWiki
Problem Statement
It would be nice if you could update DeepWiki as a github action, the current repo info on DeepWiki is a bit old
Proposed Solution
That DeepWiki was automatically updated
Alternatives Considered
No response
Use Case
Reference the code faster
Implementation Ideas
No response
Additional Context
No response
Pre-submission Checklist
- [x] I have searched existing issues to ensure this feature hasn't been requested already
- [x] I have provided a clear problem statement and proposed solution
- [x] I have described my specific use case
I'll do it this weekend. How are you finding our docs @Varming73 ?
I remember you mentioning some changes you could add on our end to improve things, would love to see what is there.
Went over your fork and the branch there, there are some API elements that changed.
Perfect, thanks. I've changed my approach a bit in how to use Cognee. I had to wrap my head around not being able to use anything but LanceDB and Kuzu (might have forgotten the name) if I wanted to separate datasets (in my case to use it as GraphRAG-like setup instead of memory). For now I will run one MCP for memory tasks and a backend+MCP for RAG. Then I can focus on using Cognee instead of several projects.. and have to live with not being able to use Neo4j + Postgres+PGVector for the RAG setup.
Anyway: I actually have a couple (2-3) different local Cognee projects as I wanted to test different directions. I've settle on not touching the backend, maybe use a frontend I already have made for my purposes (and it uses hard delete of files, where the official frontend soft delete files) and focus on only create changes in the MCP instead. Due to having to have two instances I also had to steer away from the Cogwit backend.
I can find what I actually made earlier.. I guess soft/hard delete in the frontend might have been a choice, then I remember that I made the MCP work with Cogwit.. something about auth and something else.. What would you like me to check, then I find it.. might be in the fork in my profile actually (not the one I'm working on currently, that is only local atm.)
@Varming73 had a look, and no easy way to externally trigger it except for making an account there and getting a premium account. I don't see a value in doing that now, especially since we work a lot on docs and there is ability to pull them via MCP
Falkor PR is in progress, others are coming soon.