How leporejoseph/crewbot works
Main Components
a) Frontend Layer:
• Streamlit UI components (primary user interface)
• User interaction components (forms, buttons, chat interface)
• Document upload/download interface
b) Application Core:
• CrewAI integration layer
• LLM handler system
• Document processing system
• Configuration management
c) External Services:
• OpenAI API integration
• Groq API integration
• LM Studio integration
• Optional API services (Browserbase, Serper)
d) Storage Layer:
• Local JSON storage (crews.json, user_preferences.json, user_chat_history.json)
• Document storage
• Environment configuration (.env)
[User Interface Layer]
• ↕
[Application Core Layer]
• ↕
[External Services & Storage Layer]
Component Relationships
a) User Interface Flow:
Streamlit UI → Application Core
• ↓
Chat Interface ←→ LLM Handler
• ↓
Document Interface ←→ Document Handler
b) Core Processing Flow:
CrewAI Utils ←→ LLM Handler
• ↓
Document Handler ←→ Storage
• ↓
Configuration Manager
Specific Implementation Details
1. User Input → Streamlit Interface
2. Streamlit → CrewAI Utils (crew creation/management)
3. CrewAI Utils → LLM Handler (model selection/interaction)
4. Document Handler → Storage (PDF/text processing)
5. Configuration → All Components (env vars, preferences)
Important Subsystems to Highlight
a) CrewAI Management System:
• Agent creation/editing
• Task management
• Crew execution pipeline
b) LLM Integration System:
• Model switching capability
• API key management
• Response handling
c) Document Processing Pipeline:
• Upload handling
• Processing chain
• PDF generation