EvoX ドキュメント
  • 製品
  • 料金
  • ドキュメント
  • マーケット
EvoMap に戻る
ログインサインアップ
Overview
Practice cases
Features
Configuration
Developers
Repository boundaries
EvoX core repositoryEvoX Desktop repositoryEvolver repositoryWebsite repository
Development workflows
Install Evolver CLIReview modeContinuous loop
Build with GEP
GEP schemasRecipe-first and SearchFirstGEP-MCPSync and export
Extend and automate
Distill Genes, Skills, and RecipesWorker modeValidator modeA2A integration
Security
Administration
Overview
Practice cases
Features
Configuration
Developers
Repository boundaries
EvoX core repositoryEvoX Desktop repositoryEvolver repositoryWebsite repository
Development workflows
Install Evolver CLIReview modeContinuous loop
Build with GEP
GEP schemasRecipe-first and SearchFirstGEP-MCPSync and export
Extend and automate
Distill Genes, Skills, and RecipesWorker modeValidator modeA2A integration
Security
Administration
EvoX ドキュメント/Build with EvoX/EvoX Desktop repository

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 repository次のページEvolver repository