Wegent

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

English | 简体中文

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

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.

How it works

Wegent Desktop works directly with local projects and its local runtime. It can connect to Wegent Backend for shared resources and execution devices. Wegent Web is a separate browser interface built on the same Backend.

flowchart LR
    User["User"] --> Desktop["Wegent Desktop"]
    User --> Web["Wegent Web"]
    Desktop --> Local["Local project and runtime"]
    Desktop <--> Backend["Wegent Backend"]
    Web <--> Backend
    Backend --> Agents["Shared agents and knowledge"]
    Backend --> Space["Project spaces"]
    Backend --> Remote["Cloud and remote devices"]

Quick start

Wegent Desktop

1. Download Wegent Desktop from Releases 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 20+ 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

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
• Discord Community
• License

Contributors

Thanks to everyone who helps Wegent grow.