[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-74770":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":17,"stars7d":18,"stars30d":19,"stars90d":16,"forks30d":16,"starsTrendScore":20,"compositeScore":21,"rankGlobal":10,"rankLanguage":10,"license":22,"archived":23,"fork":23,"defaultBranch":24,"hasWiki":23,"hasPages":23,"topics":25,"createdAt":10,"pushedAt":10,"updatedAt":34,"readmeContent":35,"aiSummary":36,"trendingCount":16,"starSnapshotCount":16,"syncStatus":37,"lastSyncTime":38,"discoverSource":39},74770,"ClawX","ValueCell-ai\u002FClawX","ValueCell-ai","ClawX is a desktop app that provides a graphical interface for OpenClaw AI agents. It turns CLI-based AI orchestration into a desktop experience without using the terminal. China website is https:\u002F\u002Fclawx.com.cn.","https:\u002F\u002Fclaw-x.com",null,"TypeScript",7406,1106,47,53,0,39,64,261,117,40.13,"MIT License",false,"main",[26,27,28,29,30,31,32,33],"agent","agentic-ai","agents","ai","clawdbot","moltbot","openclaw","skill","2026-06-12 02:03:27","\n\u003Cp align=\"center\">\n  \u003Cimg src=\"src\u002Fassets\u002Flogo.svg\" width=\"128\" height=\"128\" alt=\"ClawX Logo\" \u002F>\n\u003C\u002Fp>\n\n\u003Ch1 align=\"center\">ClawX\u003C\u002Fh1>\n\n\u003Cp align=\"center\">\n  \u003Cstrong>The Desktop Interface for OpenClaw AI Agents\u003C\u002Fstrong>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Ca href=\"#features\">Features\u003C\u002Fa> •\n  \u003Ca href=\"#why-clawx\">Why ClawX\u003C\u002Fa> •\n  \u003Ca href=\"#getting-started\">Getting Started\u003C\u002Fa> •\n  \u003Ca href=\"#architecture\">Architecture\u003C\u002Fa> •\n  \u003Ca href=\"#development\">Development\u003C\u002Fa> •\n  \u003Ca href=\"#contributing\">Contributing\u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Fplatform-MacOS%20%7C%20Windows%20%7C%20Linux-blue\" alt=\"Platform\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Felectron-40+-47848F?logo=electron\" alt=\"Electron\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Freact-19-61DAFB?logo=react\" alt=\"React\" \u002F>\n  \u003Ca href=\"https:\u002F\u002Fdiscord.com\u002Finvite\u002F84Kex3GGAh\" target=\"_blank\">\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fdiscord\u002F1399603591471435907?logo=discord&labelColor=%20%235462eb&logoColor=%20%23f5f5f5&color=%20%235462eb\" alt=\"chat on Discord\" \u002F>\n  \u003C\u002Fa>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fdownloads\u002FValueCell-ai\u002FClawX\u002Ftotal?color=%23027DEB\" alt=\"Downloads\" \u002F>\n  \u003Cimg src=\"https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MIT-green\" alt=\"License\" \u002F>\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  English | \u003Ca href=\"README.zh-CN.md\">简体中文\u003C\u002Fa> | \u003Ca href=\"README.ja-JP.md\">日本語\u003C\u002Fa> | \u003Ca href=\"README.ru-RU.md\">Русский\u003C\u002Fa>\n\u003C\u002Fp>\n\n---\n\n## Overview\n\n**ClawX** bridges the gap between powerful AI agents and everyday users. Built on top of [OpenClaw](https:\u002F\u002Fgithub.com\u002FOpenClaw), it transforms command-line AI orchestration into an accessible, beautiful desktop experience—no terminal required.\n\nWhether you're automating workflows, managing AI-powered channels, or scheduling intelligent tasks, ClawX provides the interface you need to harness AI agents effectively.\n\nClawX comes pre-configured with best-practice model providers and natively supports Windows as well as multi-language settings. Of course, you can also fine-tune advanced configurations via **Settings → Advanced → Developer Mode**.\n\n\u003Cp align=\"center\">\u003Cstrong style=\"font-size:1.1em; text-decoration: underline;\">For a full enterprise edition, dedicated service support, or tailored deployment guidance for your business scenario, contact us at \u003Ca href=\"mailto:public@valuecell.ai\">public@valuecell.ai\u003C\u002Fa>.\u003C\u002Fstrong>\u003C\u002Fp>\n\n---\n## Screenshot\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"resources\u002Fscreenshot\u002Fen\u002Fchat.png\" style=\"width: 100%; height: auto;\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"resources\u002Fscreenshot\u002Fen\u002Fcron.png\" style=\"width: 100%; height: auto;\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"resources\u002Fscreenshot\u002Fen\u002Fskills.png\" style=\"width: 100%; height: auto;\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"resources\u002Fscreenshot\u002Fen\u002Fchannels.png\" style=\"width: 100%; height: auto;\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"resources\u002Fscreenshot\u002Fen\u002Fmodels.png\" style=\"width: 100%; height: auto;\">\n\u003C\u002Fp>\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"resources\u002Fscreenshot\u002Fen\u002Fsettings.png\" style=\"width: 100%; height: auto;\">\n\u003C\u002Fp>\n\n---\n\n## Why ClawX\n\nBuilding AI agents shouldn't require mastering the command line. ClawX was designed with a simple philosophy: **powerful technology deserves an interface that respects your time.**\n\n| Challenge | ClawX Solution |\n|-----------|----------------|\n| Complex CLI setup | One-click installation with guided setup wizard |\n| Configuration files | Visual settings with real-time validation |\n| Process management | Automatic gateway lifecycle management |\n| App updates | Startup update checks with a prompt before downloading or installing |\n| Multiple AI providers | Unified provider configuration panel |\n| Skill\u002Fplugin installation | Built-in skill marketplace and management |\n\n### OpenClaw Inside\n\nClawX is built directly upon the official **OpenClaw** core. Instead of requiring a separate installation, we embed the runtime within the application to provide a seamless \"battery-included\" experience.\n\nWe are committed to maintaining strict alignment with the upstream OpenClaw project, ensuring that you always have access to the latest capabilities, stability improvements, and ecosystem compatibility provided by the official releases.\n\nWhen Developer Mode is enabled, the sidebar also provides a native Dreams page for OpenClaw memory review, dream diary inspection, and basic maintenance actions. The full upstream OpenClaw Dreams UI remains available from that page when deeper diagnostics are needed.\n\n---\n\n## Features\n\n### 🎯 Zero Configuration Barrier\nComplete the entire setup—from installation to your first AI interaction—through an intuitive graphical interface. No terminal commands, no YAML files, no environment variable hunting.\n\n### 💬 Intelligent Chat Interface\nCommunicate with AI agents through a modern chat experience. Support for multiple conversation contexts, message history, rich content rendering with Markdown (including GitHub-flavored tables and KaTeX-powered LaTeX math: `$inline$`, `$$block$$`, `\\(inline\\)`, and `\\[block\\]`), and direct `@agent` routing in the main composer for multi-agent setups.\nSkills you insert from the composer appear as `\u002Fskill-name` chips; click a chip to open the preview sidebar and read that skill's `SKILL.md`.\nWhen you target another agent with `@agent`, ClawX switches into that agent's own conversation context directly instead of relaying through the default agent. Agent workspaces stay separate by default, and stronger isolation depends on OpenClaw sandbox settings.\nEach agent can also override its own `provider\u002Fmodel` runtime setting; agents without overrides continue inheriting the global default model.\n\n### 📡 Multi-Channel Management\nConfigure and monitor multiple AI channels simultaneously. Each channel operates independently, allowing you to run specialized agents for different tasks.\nEach channel now supports multiple accounts, per-account agent binding, and switching the channel default account directly from the Channels page.\nFor custom channel account IDs, ClawX enforces OpenClaw-compatible canonical IDs (`[a-z0-9_-]`, lowercase, max 64 chars, must start with a letter\u002Fnumber) to prevent routing mismatches.\nClawX now also bundles Tencent's official personal WeChat channel plugin, so you can link WeChat directly from the Channels page with an in-app QR flow.\n\n### ⏰ Cron-Based Automation\nSchedule AI tasks to run automatically. Define triggers, set intervals, and let your AI agents work around the clock without manual intervention.\nThe Cron page now lets you configure external delivery directly in the task form with separate sender-account and recipient-target selectors. For supported channels, recipient targets are discovered automatically from channel directories or known session history, so you no longer need to edit `jobs.json` by hand.\n\n\n### 🧩 Extensible Skill System\nExtend your AI agents with pre-built skills. Browse, install, and manage skills through the integrated skill panel—no package managers required.\nClawX also pre-bundles full document-processing skills (`pdf`, `xlsx`, `docx`, `pptx`), deploys them automatically to the managed skills directory (default `~\u002F.openclaw\u002Fskills`) on startup, and enables them by default on first install. Additional bundled skills (`find-skills`, `self-improving-agent`, `tavily-search`) are also enabled by default; if required API keys are missing, OpenClaw will surface configuration errors in runtime.  \nThe Skills page can display skills discovered from multiple OpenClaw sources (managed dir, workspace, and extra skill dirs), and now shows each skill's actual location so you can open the real folder directly.\n\nEnvironment variables for bundled search skills:\n- `TAVILY_API_KEY` for `tavily-search` (OAuth may also be supported by upstream skill runtime)\n- `find-skills` and `self-improving-agent` do not require API keys\n\n### 🔐 Secure Provider Integration\nConnect to multiple AI providers (OpenAI, Anthropic, and more) with credentials stored securely in your system's native keychain. OpenAI supports both API key and browser OAuth (Codex subscription) sign-in.\nFor **Custom** providers used with OpenAI-compatible gateways, you can set a custom `User-Agent` in **Settings → AI Providers → Edit Provider** for compatibility-sensitive endpoints.\nWhen a compatible gateway rejects `\u002Fmodels` for non-auth reasons, ClawX automatically falls back to a lightweight `\u002Fchat\u002Fcompletions` or `\u002Fresponses` probe during API key validation.\n\n### 🌙 Adaptive Theming\nLight mode, dark mode, or system-synchronized themes. ClawX adapts to your preferences automatically.\n\n### 🚀 Startup Launch Control\nIn **Settings → General**, you can enable **Launch at system startup** so ClawX starts automatically after login.\n\n### 🔔 Update Prompts\nClawX can automatically check for new versions on startup. When an update is available, it shows an in-app prompt; downloading and installing only happen after you choose the action.\n\n---\n\n## Getting Started\n\n### System Requirements\n\n- **Operating System**: macOS 11+, Windows 10+, or Linux (Ubuntu 20.04+)\n- **Memory**: 4GB RAM minimum (8GB recommended)\n- **Storage**: 1GB available disk space\n\n### Installation\n\n#### Pre-built Releases (Recommended)\n\nDownload the latest release for your platform from the [Releases](https:\u002F\u002Fgithub.com\u002FValueCell-ai\u002FClawX\u002Freleases) page.\n\n#### Build from Source\n\n```bash\n# Clone the repository\ngit clone https:\u002F\u002Fgithub.com\u002FValueCell-ai\u002FClawX.git\ncd ClawX\n\n# Initialize the project\npnpm run init\n\n# Start in development mode\npnpm dev\n```\n### First Launch\n\nWhen you launch ClawX for the first time, the **Setup Wizard** will guide you through:\n\n1. **Language & Region** – Configure your preferred locale\n2. **AI Provider** – Add providers with API keys or OAuth (for providers that support browser\u002Fdevice login)\n3. **Skill Bundles** – Select pre-configured skills for common use cases\n4. **Verification** – Test your configuration before entering the main interface\n\nThe wizard preselects your system language when it is supported, and falls back to English otherwise.\n\n> Note for Moonshot (Kimi): ClawX keeps Kimi web search enabled by default.  \n> When Moonshot is configured, ClawX also syncs Kimi web search to the China endpoint (`https:\u002F\u002Fapi.moonshot.cn\u002Fv1`) in OpenClaw config.\n\n### Proxy Settings\n\nClawX includes built-in proxy settings for environments where Electron, the OpenClaw Gateway, or channels such as Telegram need to reach the internet through a local proxy client.\n\nOpen **Settings → Gateway → Proxy** and configure:\n\n- **Proxy Server**: the default proxy for all requests\n- **Bypass Rules**: hosts that should connect directly, separated by semicolons, commas, or new lines\n- In **Developer Mode**, you can optionally override:\n  - **HTTP Proxy**\n  - **HTTPS Proxy**\n  - **ALL_PROXY \u002F SOCKS**\n\nRecommended local examples:\n\n```text\nProxy Server: http:\u002F\u002F127.0.0.1:7890\n```\nNotes:\n\n- A bare `host:port` value is treated as HTTP.\n- If advanced proxy fields are left empty, ClawX falls back to `Proxy Server`.\n- Saving proxy settings reapplies Electron networking immediately and restarts the Gateway automatically.\n- ClawX also syncs the proxy to OpenClaw's Telegram channel config when Telegram is enabled.\n- Gateway restarts preserve an existing Telegram channel proxy if ClawX proxy is currently disabled.\n- To explicitly clear Telegram channel proxy from OpenClaw config, save proxy settings with proxy disabled.\n- In **Settings → Advanced → Developer**, you can run **OpenClaw Doctor** to execute `openclaw doctor --json` and inspect the diagnostic output without leaving the app.\n- On packaged Windows builds, the bundled `openclaw` CLI\u002FTUI runs via the shipped `node.exe` entrypoint to keep terminal input behavior stable.\n\n---\n\n## Architecture\n\nClawX employs a **dual-process architecture** with a unified host API layer. The renderer talks to a single client abstraction, while Electron Main owns protocol selection and process lifecycle:\n\n```\n┌──────────────────────────────────────────────────────────────────┐\n│                        ClawX Desktop App                         │\n│                                                                  │\n│  ┌────────────────────────────────────────────────────────────┐  │\n│  │              Electron Main Process                         │  │\n│  │  • Window & application lifecycle management               │  │\n│  │  • Gateway process supervision                             │  │\n│  │  • System integration (tray, notifications, keychain)      │  │\n│  │  • Auto-update orchestration                               │  │\n│  └────────────────────────────────────────────────────────────┘  │\n│                              │                                   │\n│                              │ IPC (authoritative control plane) │\n│                              ▼                                   │\n│  ┌────────────────────────────────────────────────────────────┐  │\n│  │              React Renderer Process                        │  │\n│  │  • Modern component-based UI (React 19)                    │  │\n│  │  • State management with Zustand                           │  │\n│  │  • Unified host-api\u002Fapi-client calls                       │  │\n│  │  • Rich Markdown rendering                                 │  │\n│  └────────────────────────────────────────────────────────────┘  │\n└──────────────────────────────┬───────────────────────────────────┘\n                               │\n                               │ Main-owned transport strategy\n                               │ (WS first, HTTP then IPC fallback)\n                               ▼\n┌──────────────────────────────────────────────────────────────────┐\n│                Host API & Main Process Proxies                   │\n│                                                                  │\n│  • hostapi:fetch (Main proxy, avoids CORS in dev\u002Fprod)           │\n│  • gateway:httpProxy (Renderer never calls Gateway HTTP direct)  │\n│  • Unified error mapping & retry\u002Fbackoff                         │\n└──────────────────────────────┬───────────────────────────────────┘\n                               │\n                               │ WS \u002F HTTP \u002F IPC fallback\n                               ▼\n┌──────────────────────────────────────────────────────────────────┐\n│                     OpenClaw Gateway                             │\n│                                                                  │\n│  • AI agent runtime and orchestration                            │\n│  • Message channel management                                    │\n│  • Skill\u002Fplugin execution environment                            │\n│  • Provider abstraction layer                                    │\n└──────────────────────────────────────────────────────────────────┘\n```\n### Design Principles\n\n- **Process Isolation**: The AI runtime operates in a separate process, ensuring UI responsiveness even during heavy computation\n- **Single Entry for Frontend Calls**: Renderer requests go through host-api\u002Fapi-client; protocol details are hidden behind a stable interface\n- **Main-Process Transport Ownership**: Electron Main controls WS\u002FHTTP usage and fallback to IPC for reliability\n- **Graceful Recovery**: Built-in reconnect, timeout, and backoff logic handles transient failures automatically\n- **Secure Storage**: API keys and sensitive data leverage the operating system's native secure storage mechanisms\n- **CORS-Safe by Design**: Local HTTP access is proxied by Main, preventing renderer-side CORS issues\n\n### Process Model & Gateway Troubleshooting\n\n- ClawX is an Electron app, so **one app instance normally appears as multiple OS processes** (main\u002Frenderer\u002Fzygote\u002Futility). This is expected.\n- Single-instance protection uses Electron's lock plus a local process-file lock fallback, preventing duplicate app launch in environments where desktop IPC\u002Fsession bus is unstable.\n- During rolling upgrades, mixed old\u002Fnew app versions can still have asymmetric protection behavior. For best reliability, upgrade all desktop clients to the same version.\n- The OpenClaw Gateway listener should still be **single-owner**: only one process should listen on `127.0.0.1:18789`.\n- Gateway readiness is based on OpenClaw core signals such as `system-presence`, `health`, and `status`; memory, Dreams, or channel failures are shown as capability degradation instead of global Gateway failure.\n- To verify the active listener:\n  - macOS\u002FLinux: `lsof -nP -iTCP:18789 -sTCP:LISTEN`\n  - Windows (PowerShell): `Get-NetTCPConnection -LocalPort 18789 -State Listen`\n- Clicking the window close button (`X`) hides ClawX to tray; it does **not** fully quit the app. Use tray menu **Quit ClawX** for complete shutdown.\n\n---\n\n## Use Cases\n\n### 🤖 Personal AI Assistant\nConfigure a general-purpose AI agent that can answer questions, draft emails, summarize documents, and help with everyday tasks—all from a clean desktop interface.\n\n### 📊 Automated Monitoring\nSet up scheduled agents to monitor news feeds, track prices, or watch for specific events. Results are delivered to your preferred notification channel.\n\n### 💻 Developer Productivity\nIntegrate AI into your development workflow. Use agents to review code, generate documentation, or automate repetitive coding tasks.\n\n### 🔄 Workflow Automation\nChain multiple skills together to create sophisticated automation pipelines. Process data, transform content, and trigger actions—all orchestrated visually.\n\n---\n\n## Development\n\n### Prerequisites\n\n- **Node.js**: 22+ (LTS recommended)\n- **Package Manager**: pnpm 9+ (recommended) or npm\n\n### Project Structure\n\n```ClawX\u002F\n├── electron\u002F                 # Electron Main Process\n│   ├── api\u002F                 # Main-side API router and handlers\n│   │   └── routes\u002F          # RPC\u002FHTTP proxy route modules\n│   ├── services\u002F            # Provider, secrets and runtime services\n│   │   ├── providers\u002F       # Provider\u002Faccount model sync logic\n│   │   └── secrets\u002F         # OS keychain and secret storage\n│   ├── shared\u002F              # Shared provider schemas\u002Fconstants\n│   │   └── providers\u002F\n│   ├── main\u002F                # App entry, windows, IPC registration\n│   ├── gateway\u002F             # OpenClaw Gateway process manager\n│   ├── preload\u002F             # Secure IPC bridge\n│   └── utils\u002F               # Utilities (storage, auth, paths)\n├── src\u002F                      # React Renderer Process\n│   ├── lib\u002F                 # Unified frontend API + error model\n│   ├── stores\u002F              # Zustand stores (settings\u002Fchat\u002Fgateway)\n│   ├── components\u002F          # Reusable UI components\n│   ├── pages\u002F               # Setup\u002FDashboard\u002FChat\u002FChannels\u002FSkills\u002FCron\u002FSettings\n│   ├── i18n\u002F                # Localization resources\n│   └── types\u002F               # TypeScript type definitions\n├── tests\u002F\n│   ├── e2e\u002F                 # Playwright Electron end-to-end smoke tests\n│   └── unit\u002F                # Vitest unit\u002Fintegration-like tests\n├── resources\u002F                # Static assets (icons\u002Fimages)\n└── scripts\u002F                  # Build and utility scripts\n```\n### Available Commands\n\n```bash\n# Development\npnpm run init             # Install dependencies + download uv\npnpm dev                  # Start with hot reload (auto-prepares bundled skills if missing)\n\n# Quality\npnpm lint                 # Run ESLint\npnpm typecheck            # TypeScript validation\n\n# Testing\npnpm test                 # Run unit tests\npnpm run test:e2e         # Run Electron E2E smoke tests with Playwright\npnpm run test:e2e:headed  # Run Electron E2E tests with a visible window\npnpm run comms:replay     # Compute communication replay metrics\npnpm run comms:baseline   # Refresh communication baseline snapshot\npnpm run comms:compare    # Compare replay metrics against baseline thresholds\n\n# Build & Package\npnpm run build:vite       # Build frontend only\npnpm build                # Full production build (with packaging assets)\npnpm package              # Package for current platform (includes bundled preinstalled skills)\npnpm package:mac          # Package for macOS\npnpm package:win          # Package for Windows\npnpm package:linux        # Package for Linux\n```\n\nOn headless Linux, run Electron tests under a display server such as `xvfb-run -a pnpm run test:e2e`.\n\n### Communication Regression Checks\n\nWhen a PR changes communication paths (gateway events, chat runtime send\u002Freceive flow, channel delivery, or transport fallback), run:\n\n```bash\npnpm run comms:replay\npnpm run comms:compare\n```\n\n`comms-regression` in CI enforces required scenarios and threshold checks.\n\n### Electron E2E Tests\n\nThe Playwright Electron suite launches the packaged renderer and main process\nfrom `dist\u002F` and `dist-electron\u002F`, so it does not require manually running\n`pnpm dev` first.\n\n`pnpm run test:e2e` automatically:\n\n- builds the renderer and Electron bundles with `pnpm run build:vite`\n- starts Electron in an isolated E2E mode with a temporary `HOME`\n- uses a temporary ClawX `userData` directory\n- skips heavy startup side effects such as gateway auto-start, bundled skill\n  installation, tray creation, and CLI auto-install\n\nThe first two baseline specs cover:\n\n- first-launch setup wizard visibility on a fresh profile\n- skipping setup and navigating to the Models page inside the Electron app\n\nAdd future Electron flows under `tests\u002Fe2e\u002F` and reuse the shared fixture in\n`tests\u002Fe2e\u002Ffixtures\u002Felectron.ts`.\n### Tech Stack\n\n| Layer | Technology |\n|-------|------------|\n| Runtime | Electron 40+ |\n| UI Framework | React 19 + TypeScript |\n| Styling | Tailwind CSS + shadcn\u002Fui |\n| State | Zustand |\n| Build | Vite + electron-builder |\n| Testing | Vitest + Playwright |\n| Animation | Framer Motion |\n| Icons | Lucide React |\n\n---\n\n## Contributing\n\nWe welcome contributions from the community! Whether it's bug fixes, new features, documentation improvements, or translations—every contribution helps make ClawX better.\n\n### How to Contribute\n\n1. **Fork** the repository\n2. **Create** a feature branch (`git checkout -b feature\u002Famazing-feature`)\n3. **Commit** your changes with clear messages\n4. **Push** to your branch\n5. **Open** a Pull Request\n\n### Guidelines\n\n- Follow the existing code style (ESLint + Prettier)\n- Write tests for new functionality\n- Update documentation as needed\n- Keep commits atomic and descriptive\n\n---\n\n## Acknowledgments\n\nClawX is built on the shoulders of excellent open-source projects:\n\n- [OpenClaw](https:\u002F\u002Fgithub.com\u002FOpenClaw) – The AI agent runtime\n- [Electron](https:\u002F\u002Fwww.electronjs.org\u002F) – Cross-platform desktop framework\n- [React](https:\u002F\u002Freact.dev\u002F) – UI component library\n- [shadcn\u002Fui](https:\u002F\u002Fui.shadcn.com\u002F) – Beautifully designed components\n- [Zustand](https:\u002F\u002Fgithub.com\u002Fpmndrs\u002Fzustand) – Lightweight state management\n\n---\n\n## Community\n\nJoin our community to connect with other users, get support, and share your experiences.\n\n| Enterprise WeChat | Feishu Group | Discord |\n| :---: | :---: | :---: |\n| \u003Cimg src=\"src\u002Fassets\u002Fcommunity\u002Fwecom-qr.png\" width=\"150\" alt=\"WeChat QR Code\" \u002F> | \u003Cimg src=\"src\u002Fassets\u002Fcommunity\u002Ffeishu-qr.png\" width=\"150\" alt=\"Feishu QR Code\" \u002F> | \u003Cimg src=\"src\u002Fassets\u002Fcommunity\u002F20260212-185822.png\" width=\"150\" alt=\"Discord QR Code\" \u002F> |\n\n### ClawX Partner Program 🚀\n\nWe're launching the ClawX Partner Program and looking for partners who can help introduce ClawX to more clients, especially those with custom AI agent or automation needs.\n\nPartners help connect us with potential users and projects, while the ClawX team provides full technical support, customization, and integration.\n\nIf you work with clients interested in AI tools or automation, we'd love to collaborate.\n\nDM us or email [public@valuecell.ai](mailto:public@valuecell.ai) to learn more.\n\n---\n\n## Star History\n\n\u003Cp align=\"center\">\n  \u003Cimg src=\"https:\u002F\u002Fapi.star-history.com\u002Fsvg?repos=ValueCell-ai\u002FClawX&type=Date\" alt=\"Star History Chart\" \u002F>\n\u003C\u002Fp>\n\n---\n\n## License\n\nClawX is released under the [MIT License](LICENSE). You're free to use, modify, and distribute this software.\n\n---\n\n\u003Cp align=\"center\">\n  \u003Csub>Built with ❤️ by the ValueCell Team\u003C\u002Fsub>\n\u003C\u002Fp>\n","ClawX 是一个桌面应用程序，为 OpenClaw AI 代理提供图形界面，将基于命令行的AI编排转换为无需终端的桌面体验。其核心功能包括自动化工作流程、管理AI驱动的渠道和调度智能任务，支持Windows平台及多语言设置，并可通过开发者模式进行高级配置。该应用使用TypeScript编写，基于Electron和React构建，确保了跨平台兼容性和用户友好的界面设计。ClawX适用于需要简化AI操作流程、提高工作效率的各种场景，如企业级自动化、个人项目管理和智能化任务调度等。",2,"2026-06-11 03:50:45","high_star"]