How trankhanhnamhoccode/screcaap works
Screcaap is a Python modular-monolith MVP for interpreting laptop activity from periodic screenshots. Its intended path is screenshot capture through an API, background processing, and timeline/analysis results; however, the README says product endpoints and capture processing are not implemented. The graph therefore shows the documented API and worker runtime alongside the planned service, OCR, LLM, storage, and persistence areas without inventing connections between them. Edges are limited to visible imports/calls or README statements; several product modules were not sampled.
Main entry points: repositories SQL repositories · storage Image storage adapters · queue.py RQ queue setup · models User device capture models
Components 24
API and product
- FastAPI bootstrap
server/main.py - Capture routes
server/api/routes/captures.py - Timeline routes
server/api/routes/timeline.py - Capture service
server/services/capture_service.py - Timeline service
server/services/timeline_service.py - Shared schemas
shared/schemas
Processing capabilities
- Analysis service
server/services/analysis_service.py - Capture worker
server/workers/capture_worker.py - OCR adapters
server/ocr - LLM adapters
server/llm
Domain and persistence
- Domain entities
server/domain/entities.py - Processing status
server/domain/enums.py - SQL repositories
server/database/repositories - User device capture models
server/database/models - Database sessions
server/database/session.py
Runtime infrastructure
- Storage bootstrap
server/storage/bootstrap.py - Image storage adapters
server/storage - RQ worker entry
server/workers/worker.py - RQ queue setup
server/workers/queue.py - Runtime settings
server/config.py
Other components
- Laptop user
- PostgreSQL
- S3 compatible store
- Redis
Connections 13
- Laptop user → FastAPI bootstrap: uses API
README.md - Database sessions → Runtime settings: loads settings
server/database/session.py - User device capture models → Database sessions: uses base
server/database/models/capture.py - User device capture models → Processing status: uses status
server/database/models/capture.py - SQL repositories → User device capture models: maps records
server/database/repositories/capture.py - SQL repositories → Domain entities: maps entities
server/database/repositories/capture.py - SQL repositories → Processing status: converts status
server/database/repositories/capture.py - Storage bootstrap → Image storage adapters: creates client
server/storage/bootstrap.py - RQ worker entry → RQ queue setup: creates queue
server/workers/worker.py - RQ queue setup → Runtime settings: loads settings
server/workers/queue.py - RQ queue setup → Redis: connects to
server/workers/queue.py - Image storage adapters → Runtime settings: loads settings
server/storage/s3.py - Image storage adapters → S3 compatible store: configures client
server/storage/s3.py