Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
CrewMeld — Enterprise AI Digital Workforce Platform. Manage AI employees like real team members. Visual SOP orchestration, 13 LLM providers (including China-native models), 8+ messaging channels(WeCom/DingTalk/Feishu/Telegram), knowledge base with RAG, and full private deployment support. Built with Next.js, React, TypeScript & Bun.
| Date | Stars |
|---|---|
| 2026-07-31 | 502 |
| 2026-08-01 | 515 |
| 2026-08-06 | 515 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# CrewMeld > 🌐 **English** | [简体中文](./README.zh-CN.md) Enterprise AI Digital Employee Platform. Provides orchestration, deployment, and runtime capabilities for AI Agents, with support for on-premise deployment. - Website: <https://crewmeld.ai/> - User Manual: <https://proinsight.gitbook.io/crewmeld> --- ## Table of Contents - [Product Features](#product-features) - [Technical Architecture](#technical-architecture) - [Quick Start](#quick-start) - [Deployment](#deployment) - [License](#license) --- ## Product Features  The platform organizes AI capabilities around three asset categories: Digital Employees, SOPs, and Tools. ### Asset Model: Employee · SOP · Tool | Asset | Responsibility | Orchestration Granularity | Creation | |-------|----------------|---------------------------|----------| | Digital Employee | Task execution entity | — | Onboarding wizard | | SOP | Multi-role collaboration flow, supports cross-hour / cross-day execution | Step level | Visual canvas | | Tool | Atomic capability, ms-to-second scale | Operation level | Template instantiation / OpenAPI import | Dependency relationship: Tools are bound to and invoked on demand by digital employees; digital employees and human employees are orchestrated by SOPs into multi-role collaboration flows. ### 1. Digital Employee Management  A digital employee comprises identity information (name, avatar, role type, persona), tool instances, LLM model configuration, knowledge base bindings, system connections, runtime status (standby / active / paused / error), and operational metrics (tasks completed, success rate, average duration). Onboarding flow: 1. Choose a role or create directly — pick a preset role from the role library, or skip and fill in basic info directly 2. Basic info — name, description, persona (auto-prefilled from the chosen role) 3. Tool binding — attach the tools the employee needs (only deployed instances are bindable) 4. Knowledge base binding — associate document knowledge bases (many-to-many) 5. Model configuration — select LLM vendor and model 6. Confirm onboarding — review and confirm; initial status is "standby" ### 2. SOP Collaboration Orchestration  SOPs cover three responsibilities: multi-role collaboration flow, triggering and scheduling, and human approval steps. Step types: | Type | Executor | Description | |------|----------|-------------| | Digital Employee | Digital Employee | Invokes a digital employee, using its tools and knowledge base to execute the task | | Human Employee | Human Employee | Performed by a human | | Human Approval | Human Employee | Flow pauses until approval is granted, then resumes | | Conditional Branch | — | Multi-way routing | The execution state machine has 8 states: pending, running, completed, plus human-waiting (resume from breakpoint), timeout, error, failed, cancelled. All state transitions are validated; illegal transitions are rejected. Trigger types: | Type | Implementation | |------|----------------| | Scheduled | Cron expression + queue scheduling | | Event-driven | Channel messages / webhook callbacks | | Manual | Admin console "Run" button / Open API | Breakpoint resume (human approval scenario): when the flow reaches a human approval node, the engine pauses and a full state snapshot is persisted to the database; notifications are sent through approver-configured channels (Feishu / WeCom / DingTalk approval cards, email HTML cards); approvers make decisions via login-free links; the engine resumes from the breakpoint, with first-come-first-served concurrency control. Timeout mechanism: step-level timeouts automatically add a "timeout" exit; the SOP-level maximum execution duration defaults to 24 hours and is configurable. Visual canvas editor: drag-and-drop node orchestration, edges defining flow, node pr
Excerpt of 20,765 characters
Read on GitHub
18
17
5
2
Would you bet a product on this? Bounded 0–100 and slow moving.
matched fp:a6b3c98df164c75d, desc:knowledge base