Wegent

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

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.

_{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.

mermaid
1flowchart LR
2    Electron["Electron<br/>Desktop host"]
3
4    subgraph DSH["DSH Runtime"]
5        direction TB
6        Core["DSH Core<br/>Plugin discovery, dependency injection, and lifecycle"]
7        App["dsh-app-wework<br/>Wework product shell and UI extension points"]
8        UI["dsh-ui-*<br/>Tasks, project spaces, settings, apps, and automation"]
9        ElectronPlugin["dsh-electron-host<br/>Electron capability bridge"]
10        ExecutorPlugin["dsh-executor-runtime<br/>Task execution and event adapter"]
11        TerminalPlugin["dsh-terminal-runtime<br/>Local interactive terminals"]
12
13        Core --> App
14        Core --> UI
15        Core --> ElectronPlugin
16        Core --> ExecutorPlugin
17        Core --> TerminalPlugin
18        App --> UI
19    end
20
21    Executor["Executor<br/>Task and session execution"]
22    Codex["Codex<br/>Coding agent"]
23    Workspace["Local project<br/>Files and commands"]
24
25    Electron -->|"Starts and hosts"| Core
26    Electron -->|"Starts and supervises"| Executor
27    ElectronPlugin <-->|"Restricted desktop capabilities"| Electron
28    UI <-->|"User actions and UI updates"| ExecutorPlugin
29    ExecutorPlugin -->|"Create, follow up, approve, cancel"| Executor
30    Executor -->|"Status, messages, tool events, results"| ExecutorPlugin
31    Executor <-->|"Launch, control, and events"| Codex
32    Codex <-->|"Read, modify, and execute"| Workspace
33    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

Download the latest Wegent Desktop installer and install it.
Open the app and add or select a local project.
Create a task and describe the work to perform.
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:

bash
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 20+ and pnpm:

bash
pnpm install
pnpm --filter wework dev

To run the macOS desktop app:

bash
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

Directory	Responsibility
`wework/`	Wegent Desktop (Electron, Vite, React)
`executor/`	Local and remote agent task execution environments
`frontend/`	Wegent platform web administration
`backend/`	REST API and core business logic
`executor_manager/`	Executor scheduling and orchestration
`chat_shell/`	Chat runtime
`knowledge_runtime/`	Knowledge retrieval services
`knowledge_doc_converter/`	Document parsing and conversion
`shared/`	Modules shared across services

Documentation

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.

_Axb	_MicroLee	_Feifei	_FicoHu	_Icycrystal4	_Yanhe	_{YaFei Liu}	_Moqimoqidea
_Johnny0120	_Parabala	_{Jake Zhang}	_Joyway78	_{Yi Xiang}	_Birch	_{junlong chen}	₊₇
_Xuemin	_lvmowei	_Fengkuizhi	_Jm.hu	_{Just Quan}	_{Kerwin Bryant}	_Kva	_fishermen
_xiaoqiang	_RockysGit	_Erdawang	_Junbaor	_Twelveeee	_Fingki	_李枨煊	_Jolestar
_Code-wangdi	_{Sense_wang}	_{Li Daiyan}	_{Jasper Zhong}	_Ray	_RichardoMu	_{_}	_Andrewzq777
_Ch15084	_Gdouyang	_Graindt	_Qingcheng	_qinxll	_Salt-hai	_Wxcfox