repowiserepowise

mdiri-ai / soduwork Architecture and code health

The AI-native engine for teams and their agents. Multi-harness, multi-agent, self-hosted.

★ 6,513stars on GitHubJavaScriptMIT

Claude Code, Cursor, Codex or VS Code. No key. You approve one sign-in in your browser.

Setup instructions on GitHub

Releases on GitHub (latest v1.13.19, Nov 19, 2026)

Repowise maps public repos from their source. Not affiliated with mdiri-ai. What is Repowise?

github.com/mdiri-ai/soduworkIndexed at 62fc760

What is soduwork?

SoduWork is an AI-native engine for teams and their agents, where a request ends when the person who asked signs off. Teams self-host it and use a web admin console, a desktop client and a central Hub to assign work to AI agents and review what they deliver. The core idea is that an agent does the work, a separate AI review checks it against acceptance criteria, and the requester approves the result. Its primary language is JavaScript, with Python on the server side. Its code health is 7.6 out of 10 (Good), ranked #103 of 4,000+ indexed repos. The last commit to soduwork was on Nov 20, 2026, and 51 people have contributed.

As of commit 62fc760, indexed Nov 20, 2026. What it is comes from a model reading the README; the rest is measured from the source and git history, not from the maintainer.

For agentssoduwork.md

Repo facts: type, license, health, rank, contributors
soduwork facts
LicenseMIT
Code health7.6 / 10 (Good)
Health rank#103 of 4,000+ indexed repos
Last commitNov 20, 2026
Contributors51
Bus factor1
Size4,487 files, 716,595 lines

Explore soduwork

Ask about this code in your agent

This connects Repowise to soduwork's code. It does not install soduwork.

Useful if you want to change or fork soduwork: your agent can ask how it is put together and get answers that cite its files.

Ask about soduwork

Answers come from soduwork's README and source, with the files they cite. Two free answers a day without an account.

Featured answer

SoduWork is an AI-native engine for teams and their agents, where a request is only finished when the person who asked signs off. Teams self-host it and reach it through a web admin console in hub-frontend, a desktop client in the client directory, and a central Hub in hub-backend/app/main.py. The Hub decides which Runner or local agent carries out each task, and a Runner connects over a WebSocket, gives each dispatch an ID so no task is taken twice, and runs each harness in its own subprocess. The core flow is that an agent does the work, a separate AI review checks it against acceptance criteria, and the requester approves the result. The repository has 4487 files, with the largest layers being Application at 1526 files and Service at 539, plus API at 78, UI at 71, Utility at 74, Config at 16, Types at 2, and Docs & Tooling at 127. To start reading, open client/main.js for the desktop side, hub-backend/app/main.py for the server, and start.py at the root for local use.

Files per layer in soduwork8 layers.

Basis: Inferred · knowledge graph· as of 62fc760

Want this for your own codebase? Map your repo free

About this page

Get a page like this for your own codebase

Repowise built this map of mdiri-ai/soduwork from its source and git history. It parses every symbol, draws the dependency graph, scores each file's health from complexity, duplication, coverage and churn, finds hotspots and owners in the history, and writes documentation for every module. Your coding agent reads the same index over MCP, so its answers cite real files.

Free for 2 public repos, with a page like this one. No card. See how Repowise works

Prefer local? pip install repowise && repowise init indexes your own checkout, no account needed. Star Repowise on GitHub

mdiri-ai/soduwork FAQ

What is SoduWork?

SoduWork is an AI-native engine for teams and their agents. Teams self-host it and use a web admin console, a desktop client and a central Hub to assign work to AI agents and review their output.

How does SoduWork work?

SoduWork moves each request through a shared issue pool. AI adds acceptance criteria, an agent does the work, a separate AI review checks it, and a person signs off.

What language is SoduWork written in?

SoduWork's primary language is JavaScript. Its code also includes Python, shell and TypeScript files.

How is the SoduWork code organized?

The client directory holds the Electron desktop app, hub-backend holds the Python server, hub-frontend holds the admin web console, and tools holds the start and deploy scripts.

When should I use SoduWork?

SoduWork suits teams that want AI agents to do assigned work and want a person to approve the result. It also lets one person save a working method as a plugin for reuse by the team.

What license does SoduWork use?

SoduWork uses the MIT license, identified as MIT.

Code health

7.5out of 10Good

Hotspots average 6.0, the place fixes pay off most.

On the leaderboards:#11 of 24 JavaScript repos

Key features of soduwork

  • One harness does the work and a second harness on a different model reviews it against the acceptance criteria.
  • A request can be assigned to a colleague or an agent, and a person signs off on the delivered work.
  • A chat that produced a good result can be saved as a plugin that the team can reuse and improve.
  • One workbench runs plugins on every harness, and you can switch harnesses mid-conversation while keeping your history and files.
  • Who asked for the work, who did it, which plugin ran and who approved it is kept on record.

How mdiri-ai/soduwork works

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.

The codebase has 4,487 files and 35,360 symbols in 7 modules, led by JavaScript, Python and Shell. Code health is 7.5 out of 10, rated good.