How kshamagowda/ai-conversational-agent works
This is a full-stack conversational agent: a browser user registers or logs in, creates conversations, and sends messages; the API authenticates requests, stores messages and extracted memories, retrieves conversation history and user memories, and asks Groq to generate a personalized reply. The frontend and Express API, authentication, conversation/memory processing, and persistence/AI integrations are shown as distinct areas. README documents analytics, security middleware, and Railway-backed storage; unsampled implementation details are represented only where documented, and edges are limited to shown calls or documented relationships.
Main entry points: server.js Express server · database.js SQLite connection · messageController.js Message orchestration · app.js Chat interface
Components 19
Browser client
- Chat interface
client/app.js - Page and styling
client/index.html
API and auth
- Express server
server/server.js - Auth routes
server/routes/authRoutes.js - Registration and login
server/controllers/authController.js - JWT verification
server/middleware/authMiddleware.js - Protected profile
server/routes/protectedRoutes.js
Conversation and memory
- Conversation routes
server/routes/conversationRoutes.js - Conversation management
server/controllers/conversationController.js - Message routes
server/routes/messageRoutes.js - Message orchestration
server/controllers/messageController.js - Memory extraction
server/services/memoryExtractor.js - Memory service
server/services/memoryService.js - Response generation
server/services/groqService.js
Persistence and AI
- SQLite connection
server/database/database.js - Database schema
server/database/schema.js
Other components
- User / browser
- Groq API
- Railway volume
Connections 24
- User / browser → Chat interface: uses
README.md - Chat interface → Page and styling: renders
README.md - Chat interface → Express server: sends HTTP/JSON
README.md - Express server → Auth routes: mounts
server/server.js - Express server → Conversation routes: mounts
server/server.js - Express server → Message routes: mounts
server/server.js - Express server → Protected profile: mounts
server/server.js - Auth routes → Registration and login: routes to
server/routes/authRoutes.js - Conversation routes → JWT verification: authenticates
server/routes/conversationRoutes.js - Conversation routes → Conversation management: routes to
server/routes/conversationRoutes.js - Message routes → JWT verification: authenticates
server/routes/messageRoutes.js - Message routes → Message orchestration: routes to
server/routes/messageRoutes.js - Protected profile → JWT verification: authenticates
server/routes/protectedRoutes.js - Registration and login → SQLite connection: reads/writes users
server/controllers/authController.js - Conversation management → SQLite connection: reads/writes conversations
server/controllers/conversationController.js - Message orchestration → SQLite connection: reads/writes records
server/controllers/messageController.js - Message orchestration → Memory extraction: extracts memories
server/controllers/messageController.js - Message orchestration → Response generation: requests response
server/controllers/messageController.js - Response generation → Groq API: calls completions
server/services/groqService.js - Memory service → SQLite connection: uses connection
server/services/memoryService.js - Express server → SQLite connection: initializes
server/server.js - Express server → Database schema: loads schema
server/server.js - Database schema → SQLite connection: uses connection
server/database/schema.js - SQLite connection → Railway volume: stores persistently
README.md