Architecture of mdiri-ai/soduwork
mdiri-ai/soduwork is 4,487 source files holding 35,360 symbols across 7 modules, written mainly in JavaScript, Python, Shell. The largest module is client, with 2,212 files, and 9 files are entry points into the dependency graph.
How soduwork fits together
Work enters through the desktop client in the client directory, whose Electron main process in client/main.js handles accounts, agent sessions, plugins and files behind the app window. The server in hub-backend/app/main.py is the Hub, and the hub-backend module decides which Runner or local agent carries out each task. A Runner connects to the Hub over a WebSocket, gives each dispatch an ID so the same task is never taken twice, and runs each harness in its own subprocess. The hub-frontend directory holds the web admin console, where administrators manage organizations, accounts, models and plugins. The tools directory holds the scripts that start SoduWork from a source checkout, and start.py at the root is the entry point for local use.
Largest modules
- client: 2,212 files and 401,919 lines of code
- hub-backend: 1,485 files and 263,035 lines of code
- hub-frontend: 257 files and 35,596 lines of code
- tools: 87 files and 11,179 lines of code
- skills: 42 files and 4,750 lines of code
- ops: 3 files and 98 lines of code
- root: 2 files and 18 lines of code
Languages
By file count: JavaScript 2,547 files, Python 1,523 files, Shell 16 files, Dockerfile 1 file, TypeScript 1 file.
Documentation
Repowise documents soduwork in 2,574 pages generated from the source, 42 of them written explanations of the repository and its modules.
More on soduwork: summary and FAQ, codebase overview, code health.
Related guide: Best dependency graph tools for monorepos