đī¸ đī¸ System Architecture
This document provides a detailed overview of Wegent's system architecture, component design, and technology stack.
đī¸ đģ Development Setup
This document provides detailed instructions on setting up a local development environment for Wegent.
đī¸ Dynamic Context (Injecting Request-Scoped Context)
Background
đī¸ Test Framework Documentation
This document describes the unit testing framework setup for the Wegent project.
đī¸ đ CRD Architecture
This document provides a detailed technical reference for Wegent's CRD (Custom Resource Definition) architecture, designed for developers who need to understand the internal structure and implementation details.
đī¸ Skill Development Guide
This document provides technical implementation details for the Skill system, including architecture, Provider development, and API reference.
đī¸ Collaboration Models Development Guide
This document provides detailed configuration examples, real-world cases, and technical implementation details for collaboration models.
đī¸ MCP Tool Refactoring Guide
English | įŽäŊä¸æ
đī¸ External Knowledge MCP
English | įŽäŊä¸æ
đī¸ Skill Runtime Flow
This document explains how Wegent selects, resolves, propagates, and consumes skills across execution scenarios. The focus is on why skill resolution must stay centralized in backend, and why sandbox / local-device startup cannot rely on skill names alone.
đī¸ External Knowledge Sources
English | įŽäŊä¸æ
đī¸ Knowledge Indexing Protection
Background
đī¸ Entity Permission Extension
This document describes Wegent's unified resource sharing permission architecture, covering the current authorization mechanism, permission processing logic, extension architecture design, and how to integrate internal customized authorization systems via IExternalEntityResolver.
đī¸ Web Scraper Service
Scope
đī¸ Exposing Capabilities Guide
This document describes the standard way to expose functional capabilities in the Wegent project, using the Knowledge Base MCP implementation as an example to show how to make your features available to AI Agents.
đī¸ Local Device Architecture
This document describes the technical architecture of local device support, including communication protocols, heartbeat mechanisms, and security design.
đī¸ Pre-Execute Hooks
Pre-execute hooks allow you to run custom scripts before task execution in the Executor. This is useful for custom initialization, security checks, environment setup, or integration with external systems.
đī¸ Runtime Local Work
Wework runtime local work surfaces Codex and Claude Code work that already exists on a user's device. It does not import that work into central TaskResource or Subtask rows, and it no longer depends on the Backend projects table to build the sidebar list. The list comes from runtime threads returned by online device executors and is shown in two groups:
đī¸ Runtime Cleanup
Runtime cleanup manually removes execution environments that have not been updated for a configured period. It only deletes runtime Pods or containers. It does not delete Backend Task records or message history.
đī¸ Local Device Command RPC
Local device command RPC lets the Backend send a preconfigured shell command to a specific online local executor device and wait for the completed result. It is intended for operational checks, workspace diagnostics, and backend-initiated probes. It does not participate in the Task/Subtask lifecycle and does not create chat messages.
đī¸ Connector Apps Architecture and Deployment
Connector Apps let Wework connect to internal systems without changing Codex source code or requiring a ChatGPT login. The upstream may be either an MCP server or an ordinary HTTP API. Responsibilities are separated: Wegent Admin manages definitions, visibility, and fixed provider headers, Wegent Backend reads ConnectorApp resources from kinds and adapts upstream protocols, and Executor exposes one local MCP endpoint to Codex. Wework has no Connector settings page; it only synchronizes available capabilities after connecting to Wegent Cloud.
đī¸ Global Capability Sync
Global capability sync lets Backend deliver user-enabled Skills, Plugins, and MCP servers to online local executor devices. Project tasks can reuse these local capabilities, while non-Project tasks continue to use task-scoped .claude config directories for isolation.
đī¸ Interactive Form Defer Flow
This document describes the standard render and resume flow for the interactiveformquestion MCP tool. The flow lets an Agent show a structured form while running, then continue from a later user message after the user submits the form.
đī¸ Sandbox Workspace Archive
Sandbox workspace archive preserves file state before a Sandbox runtime is deleted by the 24-hour idle cleanup, then restores those files when the same Task creates a new Sandbox runtime during a later conversation. The feature reuses the existing executor Pod workspace archive pipeline. Executor and sandbox archives both use home/ and workspace/ roots, with runtime_type selecting the runtime-specific home path.
đī¸ Wework Message Scroll Verification
The Wework desktop chat list uses virtual scrolling. After sending a message, scrolling must cover the asynchronous layout measurements for both the user message and waiting indicator until the list is stably pinned to the bottom, keeping the thinking indicator fully visible. As a streaming response grows, the view should follow it only while the user remains at the bottom; otherwise the user's current viewport must be preserved.
đī¸ Task Runtime State Machine
Background
đī¸ Chat Shell Graceful Shutdown
Chat Shell's /v1/responses endpoint is a long-lived streaming API. When Kubernetes terminates a Pod, the service must stop accepting new traffic before waiting for existing streams to finish. Otherwise users can see interrupted SSE responses.
đī¸ User Runtime Config
English | įŽäŊä¸æ
đī¸ Wework Telemetry and Product Analytics
Wework separates product analytics, desktop error diagnostics, and service observability:
đī¸ QuickCard Input Presets
Overview
đī¸ Chat Shell Context Governance
Overview
đī¸ Shared Skill Directory
Wework provides a Skills settings page that unifies local Claude and Codex personal skill directories under ~/.agents/skills. The feature targets online Claude Code local devices and runs through local device command RPC; the browser does not access the filesystem directly.
đī¸ Chat Shell Attachment Context (Preview & On-Demand Read)
If you want the broader three-stage rollout, design trade-offs, and maintenance
đī¸ Cloud project collaboration architecture
The current V4 UI source of truth is /Users/hongyu9/Downloads/wework-delivery-v4-TODO.pen. Implement the interaction from that design instead of deriving page layout from this document.
đī¸ đ ī¸ Developer Guide
English | įŽäŊä¸æ
đī¸ Database Migrations Guide
This guide covers database migration management using Alembic for the Wegent Backend application.
đī¸ OpenTelemetry Setup Guide
This guide explains how to set up and configure OpenTelemetry for distributed tracing and metrics in Wegent.
đī¸ Responsive Development Guide
Overview