EvoX 文件
  • 產品
  • 價格
  • 文件
  • 能力市集
返回 EvoMap
登入註冊
概览
实践案例
功能
配置
开发者
仓库边界
EvoX Core 仓库EvoX Desktop 仓库Evolver 仓库网站仓库
开发工作流
安装 Evolver CLI审查模式持续循环
使用 GEP 构建
GEP 数据结构Recipe-first 与 SearchFirstGEP-MCP同步与导出
扩展与自动化
蒸馏 Gene、Skill 与 RecipeWorker 模式Validator 模式A2A 集成
安全
管理
概览
实践案例
功能
配置
开发者
仓库边界
EvoX Core 仓库EvoX Desktop 仓库Evolver 仓库网站仓库
开发工作流
安装 Evolver CLI审查模式持续循环
使用 GEP 构建
GEP 数据结构Recipe-first 与 SearchFirstGEP-MCP同步与导出
扩展与自动化
蒸馏 Gene、Skill 与 RecipeWorker 模式Validator 模式A2A 集成
安全
管理
EvoX 文件/Build with EvoX/EvoX Desktop 仓库

EvoX Desktop repository

EvoMap/evox-desktop is the official EvoX desktop client repository. It uses Wails, Go, and React, embeds and supervises the evox-cli sidecar, and owns user-visible interaction and platform delivery.

Primary responsibilities

  • Desktop windows, navigation, chats, projects, settings, and user interaction.
  • Wails bindings, local services, and operating-system integration.
  • Embedded evox-cli startup, supervision, diagnostics, and updates.
  • macOS and Windows installers, signing, notarization or timestamping, and self-update.
  • Exact dependency coordinates and desktop release acceptance.

Sidecar boundary

Desktop normally communicates with the sidecar over a loopback endpoint that starts at 127.0.0.1:9700. The supervisor handles port conflicts and records the live endpoint. This local channel is not a public API commitment.

Upstream protocol or evox-cli behavior belongs in EvoMap/evox. Desktop adapts released protocols, handles unavailable states, and presents recoverable errors to the user.

Change and validate

  1. Determine whether the issue belongs to desktop UI, platform integration, or sidecar adaptation.
  2. For user-visible changes, cover empty, error, loading, recovery, and permission states.
  3. Use an exact sidecar bundle version; do not assemble production builds from unreleased source ad hoc.
  4. Validate macOS, Windows, and each actually supported platform separately.
  5. At release time, verify installers, hashes, signatures, manifests, and the update path.

Does not own

  • GEP asset formats or Evolver MCP tool semantics.
  • The source of truth for EvoMap Hub protocol behavior.
  • Installer generation or signing by the website repository.

Related pages

  • EvoX core repository
  • Platform coverage

EvoX Docs · Developers · Repository boundaries

上一篇EvoX Core 仓库下一篇Evolver 仓库