📝 Description
Currently, DocChat supports ingestion of documentation via a URL. However, many users may have documentation stored locally (PDFs, Word files, Markdown, etc.) or on their mobile devices. Adding support for direct file uploads would expand usability and allow DocChat to handle offline or proprietary documentation that isn’t hosted on a public website.
✅ Proposed Solution
- Enable users to upload documentation files directly from their system or phone.
- Supported formats: PDF, DOCX, TXT, Markdown (
.md).
- Process uploaded files through the same pipeline (cleaning, chunking, embedding/tree indexing).
- Store uploaded docs in the knowledge base for reuse across chats.
- Provide progress updates during ingestion (similar to URL ingestion).
🔄 Workflow Example
- User clicks “Upload Docs” button.
- Selects file(s) from system or mobile device.
- Backend processes the file(s) → cleans, chunks, embeds/tree‑indexes.
- Knowledge base created and linked to user’s chat session.
- User can immediately start chatting with the uploaded documentation.
📂 Technical Considerations
- File upload handling (multipart/form‑data API endpoint).
- Storage strategy (local server storage, cloud bucket, or DB).
- Security: sanitize inputs, enforce file size/type limits.
- Reuse logic: if the same file is uploaded again, reuse existing knowledge base.
- Mobile UI: ensure upload works smoothly on phones.
🎯 Benefits
- Broader use cases (offline docs, proprietary manuals, internal guides).
- Easier adoption for teams with private documentation.
- Consistent experience across web and mobile.
📝 Description
Currently, DocChat supports ingestion of documentation via a URL. However, many users may have documentation stored locally (PDFs, Word files, Markdown, etc.) or on their mobile devices. Adding support for direct file uploads would expand usability and allow DocChat to handle offline or proprietary documentation that isn’t hosted on a public website.
✅ Proposed Solution
.md).🔄 Workflow Example
📂 Technical Considerations
🎯 Benefits