Open-source AI-era employment platform connecting skills, jobs, enterprises, governance, and AI agents.
# Add to your Claude Code skills
git clone https://github.com/pfwjrfp5hh-byte/WorkMeshLast scanned: 6/7/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-06-07T07:56:31.162Z",
"npmAuditRan": true,
"pipAuditRan": true
}No comments yet. Be the first to share your thoughts!
30 days in the Featured rail
English | 简体中文
Make every capability visible. Help every person affected by the AI transition find the next meaningful opportunity faster.
WorkMesh, also referred to as the Future Work Platform, is an open-source prototype for future employment and workforce collaboration.
It explores how people, skills, jobs, enterprise demand, service fulfillment, governance operations, and AI-assisted decision support can be connected through one shared data loop. The goal is not to build another job board. The goal is to explore a more efficient, transparent, and explainable coordination network that offers more dignified support to people navigating unemployment, career transitions, flexible work, and continuous learning.

I am an ordinary humanities graduate, not a professional software engineer. Most of the code in this repository was completed with the help of AI. I was surprised by what AI could do, and I also felt the shared power behind Hello World. That led me to explore a skill-sharing system built around the idea of "open-source skills." As more people face unemployment or career disruption during the AI transition, perhaps a system like this can become useful.
For the system to work in the real world, it would need backing from a government body or a large organization with strong public credibility. It aims to respond to several challenges: supporting people who lose their jobs, reducing resource imbalances between enterprises of different sizes, and improving oversight of capital flows.
This is as far as I can take the system with my current abilities. If you would like to contribute to the future, you can improve it through technology or share it so more people can prepare earlier.
Traditional employment systems often split the same person into disconnected records: a resume on a recruitment website, training history on another platform, job-seeking status scattered across different systems, and delayed statistical reports on the governance side.
WorkMesh explores a different model:
The intended result is a living employment collaboration network: when one profile changes, the rest of the system can respond.
This repository contains a locally runnable multi-portal system:
| Service | Port | Entry URL | Primary Users | AI Surface |
| --- | ---: | --- | --- | --- |
| Enterprise Portal | 3000 | http://localhost:3000/enterprise/dashboard | Recruiters, operators, enterprise admins | Enterprise AI Assistant |
| Personal Web Portal | 5173 | http://127.0.0.1:5173/#/ai-assistant | Workers, job seekers, flexible talent | Opens in the Personal AI Workspace |
| Governance Portal | 8000 | http://127.0.0.1:8000/#/en/cockpit | Employment service and governance teams | Bodao AI |
| Mobile Registration Portal | 5174 | http://127.0.0.1:5174/#/register | New users | Hands off to the Personal AI Workspace |
| Shared API and Swagger | 3001 | http://localhost:3001/api/docs | Developers and integration partners | RAG and Agent Skills endpoints |
| PostgreSQL | 5432 | localhost:5432 | Shared infrastructure | Stores profiles, matching, RAG, and invocation audit records |
In the table above,
localhostand127.0.0.1refer to the visitor's own computer. Publishing the repository does not automatically create a public website. After downloading the repository and running./deploy.shor./start-local-demo.sh, users can access the system locally through these URLs.When deploying WorkMesh to a cloud server, replace
localhostwith the server IP address or your own domain, for examplehttp://203.0.113.10:3000/enterprise/dashboard. For production deployments, configure HTTPS and reverse proxy routing through Nginx, Caddy, or a cloud gateway. Separate subdomains such asenterprise.example.com,personal.example.com,governance.example.com, andapi.example.comare recommended.
flowchart LR
Person["Personal Web Portal<br/>React + Vite<br/>5173"] --> API["Shared API<br/>NestJS + Prisma<br/>3001"]
Register["Mobile Registration<br/>React + Vite<br/>5174"] --> API
Enterprise["Enterprise Portal<br/>Next.js<br/>3000"] --> API
Governance["Governance Portal<br/>HTML + CSS + JS<br/>8000"] --> API
API --> DB[("PostgreSQL<br/>5432")]
API --> Match["Skill and Job<br/>Matching Engine"]
API --> RAG["RAG Knowledge<br/>Documents"]
API --> Skills["Agent Skills<br/>Router"]
Skills --> Audit["Agent Invocation<br/>Audit Trail"]
Match --> DB
RAG --> DB
Audit --> DB
User and PersonalProfile.The following mechanisms describe the long-term direction of WorkMesh. The current repository already implements some of them. Features that are not yet complete are marked clearly later in this document.
Hello World to Hello Skill.Example: if someone has an "electrical circuit repair" skill, and an enterprise or individual publishes a matching request, a future version of the system could combine skill tags with a nearby 30km distance search.
Example: if an enterprise has a "lawn mower manufacturing" tag, and another enterprise or individual needs a product, a large order, or production support, a future version of the system could prioritize qualified enterprises in the same city and encourage regional collaboration.