DSH HUB
HomePlugin StorePlugin PacksCommunityRankingsResourcesPublish Guide
Plugin source
Back to catalog

wecode-ai /

wecode-ai/Wegent

Topic repository only

Plan, build, and deliver with an open-source, self-hostable AI workspace for coding, collaboration, and automation.

★ 890 Stars148 Forks143 IssuesN/A Community rating0 Confirmed installs
View on GitHubProject homepage
READMESource: main@0f5b3c97

Wegent

An open-source AI work system spanning your local desktop, cloud agents, and remote machines.

English | 简体中文

CI License GitHub Issues LINUX DO

Wegent includes a desktop workbench and a self-hostable web platform. Wegent Desktop works with local projects, files, commands, tests, and code changes. Wegent Web provides browser-based agents, knowledge, automation, and administration. Wegent Backend connects these applications to shared project spaces, models, and execution devices.

Download the latest Wegent Desktop · Documentation · Contributing

Wegent Desktop

Wegent Desktop organizes local coding work by project and task. The task view keeps the conversation, tool activity, tests, changed files, and diffs together; the project-space view provides the board, shared files, automation, and execution status.

A real Wegent Desktop coding task showing the verified result, changed files, and an expanded source-code diff in one workbench

Running and reviewing a local coding task in Wegent Desktop.

A real Wegent Desktop project workspace with its kanban board, project navigation, and a remote-machine test task in progress

A project space in Wegent Desktop with its task board, shared files, automation, and execution status.

Features

  • Desktop workbench — Organize local projects, tasks, sessions, files, tool activity, tests, and diffs.
  • Reusable agents — Combine models, prompts, Skills, knowledge, tools, and collaboration settings.
  • Project spaces — Share task boards, files, discussions, automation, execution history, and deliveries.
  • Multiple execution targets — Run tasks locally, on remote work machines, or with server-managed executors.
  • Self-hosting — Deploy Wegent Web and Backend for team access, APIs, permissions, scheduling, and knowledge services.

Why Wegent

The local coding experience built on Codex is the foundation of Wegent Desktop. It works directly with the code, files, commands, and development environment in your projects. Connect it to Wegent Backend when coding work needs to move beyond one computer or one person. Once connected, the desktop workbench and Web use the same projects, tasks, and execution devices.

  • Run tasks on the right device — Keep using the code, files, commands, and development environment already on a local machine, or run a task for the same project on a remote work machine or server-managed executor.
  • Move a project forward as a team — Project spaces connect task boards, shared files, discussions, execution status, and deliveries instead of leaving conversations and code changes on separate computers.
  • Automate repeated project work — Project spaces can configure automation and execution queues to keep routine work moving.
  • Keep services and data under team control — Self-host Web and Backend for shared access, permissions, model configuration, scheduling, knowledge services, and remote-device management.

If work always stays on one computer, Wegent Desktop provides a familiar Codex coding experience. Connect it to Wegent to extend that experience when tasks must move across people, devices, or a self-hosted environment.

Wegent Web

Wegent Web provides the browser interface for remote agents. Agents can use configured models, knowledge, Skills, and tools while Wegent Backend manages their tasks and execution.

A Wegent remote agent using tools to generate and display a Gantt chart

A Wegent remote agent uses tools to generate a Gantt chart.

How it works

Wework is the Wegent desktop workbench. Electron owns desktop windows, system capabilities, and process management. DeepSeek Harness (DSH) is the embedded application and plugin runtime, and the Wework product UI is composed from a set of DSH plugins. Executor manages tasks and sessions, then drives Codex to perform the actual work in local projects.

flowchart LR
    Electron["Electron<br/>Desktop host"]

    subgraph DSH["DSH Runtime"]
        direction TB
        Core["DSH Core<br/>Plugin discovery, dependency injection, and lifecycle"]
        App["dsh-app-wework<br/>Wework product shell and UI extension points"]
        UI["dsh-ui-*<br/>Tasks, project spaces, settings, apps, and automation"]
        ElectronPlugin["dsh-electron-host<br/>Electron capability bridge"]
        ExecutorPlugin["dsh-executor-runtime<br/>Task execution and event adapter"]
        TerminalPlugin["dsh-terminal-runtime<br/>Local interactive terminals"]

        Core --> App
        Core --> UI
        Core --> ElectronPlugin
        Core --> ExecutorPlugin
        Core --> TerminalPlugin
        App --> UI
    end

    Executor["Executor<br/>Task and session execution"]
    Codex["Codex<br/>Coding agent"]
    Workspace["Local project<br/>Files and commands"]

    Electron -->|"Starts and hosts"| Core
    Electron -->|"Starts and supervises"| Executor
    ElectronPlugin <-->|"Restricted desktop capabilities"| Electron
    UI <-->|"User actions and UI updates"| ExecutorPlugin
    ExecutorPlugin -->|"Create, follow up, approve, cancel"| Executor
    Executor -->|"Status, messages, tool events, results"| ExecutorPlugin
    Executor <-->|"Launch, control, and events"| Codex
    Codex <-->|"Read, modify, and execute"| Workspace
    TerminalPlugin <-->|"PTY"| Workspace

DSH does not execute coding tasks itself. dsh-app-wework defines the product shell and extension points, dsh-ui-* provides the product modules, dsh-electron-host bridges restricted Electron capabilities, dsh-executor-runtime communicates bidirectionally with Executor throughout execution, and dsh-terminal-runtime manages local interactive terminals. Executor is the task execution layer, while Codex is the concrete coding agent it drives.

Wework can also connect to Wegent Backend for shared project spaces, models, and remote execution devices. Wegent Web is a separate browser interface built on the same Backend.

Quick start

Wegent Desktop

  1. Download the latest Wegent Desktop installer and install it.
  2. Open the app and add or select a local project.
  3. Create a task and describe the work to perform.
  4. Review the agent activity, command output, and file changes.

Wegent Web and Backend

To start the self-hosted web application and Backend in standalone mode with Docker:

curl -fsSL https://raw.githubusercontent.com/wecode-ai/Wegent/main/install.sh | bash -s -- --standalone

Open http://localhost:3000 and follow the setup flow to create the administrator password and configure a model. See the Installation Guide and Standalone Mode for other deployment options.

Development

Requires Node.js 22.15+ (22.x) or 23.8+ (Node.js 24 recommended), and pnpm:

pnpm install
pnpm --filter wework dev

To run the macOS desktop app:

pnpm --filter wework dev:mac

See wework/README.md for desktop development, build, and release instructions. wework/ is the current desktop application source directory.

Repository map

Products and services

Directory Responsibility
wework/ Wegent Desktop (Electron, Vite, React)
wework-mobile/ Independent Expo application for iOS and Android
frontend/ Wegent Web (Next.js, React)
backend/ Default public API, business logic, and data models
backend-rs/ Rust hybrid gateway and APIs that have completed migration
executor/ Rust task executor, local-device runtime, and Codex integration
executor_manager/ Server-side executor scheduling, sandboxes, and orchestration
chat_shell/ Lightweight chat and agent runtime
knowledge_runtime/ Knowledge indexing and retrieval API
knowledge_doc_converter/ Document parsing and asynchronous conversion service

Shared code and developer tools

Directory Responsibility
knowledge_engine/ Reusable Python kernel for parsing, indexing, vector stores, and retrieval
shared/ Python models, protocols, utilities, and telemetry shared by services
packages/ TypeScript chat and collaboration modules shared by Web and Desktop
sdk/ Plugin authentication, build, creation, and DingTalk workspace SDKs
wegent-cli/ Python CLI for managing Wegent CRD resources

Infrastructure, tests, and documentation

Directory Responsibility
docker/ Service images, standalone resources, and the docker/telemetry/ observability stack
scripts/ Installation, release, acceptance, repository-policy, and development automation
tests/ Cross-service Playwright integration tests and installation tests
docs/ English and Chinese user docs, developer docs, architecture, and historical designs
patches/ Third-party dependency patches used by pnpm patchedDependencies
LICENSES/ Third-party license texts required for repository distribution
.github/ CI, release workflows, composite actions, and repository automation

Root entry points

File Responsibility
start.sh, install.sh Local startup and self-hosted installation
build_image.sh, build_image_mac.sh Multi-architecture and host Docker image builds
docker-compose*.yml Default, build, and E2E Compose orchestration
package.json, pnpm-workspace.yaml JavaScript/TypeScript workspace definition
pyproject.toml, uv.lock Repository-level Python tooling and lock metadata
AGENTS.md, CLAUDE.md Contributor rules and compatibility symlink

Documentation

  • Wegent Desktop documentation
  • Desktop development and release
  • Wegent quick start
  • Installation and deployment
  • Core concepts
  • Developer guide
  • Troubleshooting

Contributing

Bug reports, documentation improvements, code contributions, and new ways of using Wegent are all welcome.

  • Contributing Guide
  • Security Policy
  • GitHub Issues
  • DingTalk Community: “wework社区交流”, group ID 190890002451
  • Discord Community
  • License

Contributors

Thanks to everyone who helps Wegent grow.

qdaxb
Axb
feifei325
Feifei
Micro66
MicroLee
FicoHu
FicoHu
icycrystal4
Icycrystal4
kissghosts
Yanhe
luckjun529-lang
junlong chen
cc-yafei
YaFei Liu
sdadunderscoresdad
+7
moqimoqidea
Moqimoqidea
sunnights
Jake Zhang
hustfisher
fishermen
johnny0120
Johnny0120
parabala
Parabala
joyway1978
Joyway78
yixiangxx
Yi Xiang
cocowh
Birch
sleetdrop
sleetdrop
lvmowei
lvmowei
2561056571
Xuemin
fengkuizhi
Fengkuizhi
jnhu76
Jm.hu
DavidLeeUX
Kva
Twelveeee
Twelveeee
earthAlone2026
xiaoqiang
maquan0927
Just Quan
kerwin612
Kerwin Bryant
RockysGit
RockysGit
qwertyerge
Erdawang
junbaor
Junbaor
fingki
Fingki
flyhope
李枨煊
friendfei
friendfei
WangZhuo2015
wang zhuo
Qinxl0921
qinxll
LiDaiyan
Li Daiyan
haosenwang1018
Sense_wang
code-wangdi
Code-wangdi
jolestar
Jolestar
DeadLion
Jasper Zhong
rayzhang0603
Ray
RichardoMrMu
RichardoMu
Ged0
_
pcbeingused333
alexcastgonz
andrewzq777
Andrewzq777
ch15084
Ch15084
gdouyang
Gdouyang
graindt
Graindt
haohaitao
haohaitao
qingchengliu
Qingcheng
salt-hai
Salt-hai
wxcfox
Wxcfox

Made with ❤️ by WeCode-AI Team

—/ 5

No ratings yet

Manifest verification required

Commit 0f5b3c9723f0

Community comments

No comments yet. Be the first to write one.

DSH HUB

A community index for DSH plugins. Not an official GitHub or DeepSeek AI product.

CommunityResourcesAPIAbout