$ show mindsdb/minds
MindsHub Cowork is a platform superproject that orchestrates four independent submodules into a unified AI workspace for knowledge workers. The repository itself contains no application logic — it's a pure orchestration layer using git submodules (frontend: Electron/Vite app, backend/core_api: FastAPI server, backend/core_agent: Anton autonomous agent, backend/data-vault: data engine). The superproject provides a sophisticated developer workflow via its Makefile: per-developer branch selection through a gitignored dev.env, dual run paths (local source with hot-reload vs uv-tool-installed desktop server) that follow the same refs, deliberate pin management via 'make pin'/'make baseline', and a nuclear 'make flush' for complete environment reset. Submodules are configured with 'ignore = all' so branch work never pollutes the parent git status. The Docker setup uses multi-stage builds with uv for Python and nginx for the web SPA. The REST API (documented in docs/api.html) exposes conversations, projects, artifacts, schedules, files, connectors, memories, skills, scratchpads, and search — all backed by a local SQLite database. This is hybrid in that it manages both a desktop (Electron) and web (SPA) frontend against the same API, but the dominant character is application orchestration.
The LLM identified 5 files worth highlighting for reuse:
Sophisticated Makefile implementing a per-developer submodule branch workflow. Uses dev.env (gitignored) for branch selection, supports dual run paths (local source with --reload vs uv tool install) that follow the same refs, provides 'make use' to check out branches, 'make pin' for deliberate pin commits, 'make baseline' to reset to pinned commits, and 'make flush' for complete environment wipe. Submodules configured with 'ignore = all' keeps parent git status clean. Demonstrates non-obvious skill in solving the multi-developer, multi-module branch coordination problem without polluting git history.
Clean multi-stage Dockerfile for the FastAPI backend. Builder stage uses uv to install core_agent and core_api from local submodule paths into a venv. Runtime stage copies the venv, creates a non-root 'cowork' user, sets proper ownership on data directory, and includes a health check hitting /health endpoint. Uses Python 3.12-slim base. Demonstrates modern Python containerization with uv and proper security practices.
Two-stage Dockerfile for the web SPA. Builder runs 'npm ci' and 'npm run build:web' (Vite production build). Runtime uses nginx:alpine to serve the built static assets with a custom nginx.conf that proxies /v1/* to the API service. Clean separation of build and runtime concerns.
Docker Compose defining two services: 'api' (cowork-server on port 26866 with SQLite volume) and 'web' (nginx on port 3000 proxying /v1/ to api). Includes proper health check on API /health endpoint, volume persistence for cowork data, and service dependency with condition. Production-ready local deployment configuration.
Comprehensive developer guide for the submodule workflow. Documents clone/init/pull procedures, making changes in submodules, the dev.env branch selection pattern, the dual run paths (local source vs installed server), the flush command, and the critical 'one DB, one ref' constraint (shared ~/.cowork/cowork.db between dev and desktop app). Serves as the single source of truth for contributor onboarding.