Thanks for the note on the Docker issue. I’ll need to see the actual error logs from the document processing Docker container to help diagnose why it’s failing on your end (or on Mac).
On my side, I’m focusing on finishing the core integration of the BrainDrive LLM, chat history and document context this week into one plugin. Once I’ve finished that, we can schedule a call to go over the new chat with documents plugin, review the architecture, and troubleshoot the Docker issue together?
Wanted to share a progress update on the Chat with Documents plugin development:
What’s Working:
Successfully integrated the plugin with BrainDrive’s LLM model (it submits chat requests to BrainDrive LLM Model - whatever model(s) you are running locally with ollama)
Note: I’m merging the foundation of the BrainDriveChat plugin (which handles LLM and chat history access) with the collection and document management logic from the previous chat with documents plugin.
Currently In Progress:
Connecting the relevant context search pipeline (retrieval from vector embeddings)
Integrating BrainDrive’s chat history system
General code refactoring to keep things clean and maintainable
Coming Up Next:
Full end-to-end testing with document uploads, vector search, and LLM responses
Polishing the UI/UX for collection and document management
I plan to wrap up these core integrations this week. Thanks for following the progress!
I have managed to remove the “waiting for services” loading state. However, the dynamic loading state still doesn’t work as expected. This flow doesn’t work as expected:
component mounted → wait for services initialization → if successful render content || if not render error
for some reason, it “frozes” on the initial state. But the good news, I was able to remove the “waiting for services”, and create collection form also works. Will continue tomorrow.
Thanks Beck. I am getting the following error when I install. I booked a call tuesday at 11 eastern to go over with you and see if we can get it working together. Thanks.
The issue comes because it conflicts with existing plugin in your database. I will update the plugin’s lifecycle manager, so it doesn’t conflict with existing plugin in db.
