Documentação do EvoX
  • Produto
  • Preços
  • Documentação
  • Mercado
Voltar ao EvoMap
Conecte-seInscrever-se
Overview
Get started
Get EvoXUse EvoXImport experience
Available on
Desktop appEvoX CLIEvolver CLI
Foundations
PromptingPersonalize EvoXMemory and identitySkills and pluginsPermissions
Explore
PricingGlossary
Practice cases
Features
Configuration
Developers
Security
Administration
Overview
Get started
Get EvoXUse EvoXImport experience
Available on
Desktop appEvoX CLIEvolver CLI
Foundations
PromptingPersonalize EvoXMemory and identitySkills and pluginsPermissions
Explore
PricingGlossary
Practice cases
Features
Configuration
Developers
Security
Administration
Documentação do EvoX/Introduction/Desktop app

Desktop app

Use the official EvoX Desktop client and verify the release you install.

EvoMap/evox-desktop is the source repository for the Wails, Go, and React client. It embeds and supervises evox-cli, while Evolver CLI remains a separate developer tool.

EvoX Desktop application

What Desktop owns

The desktop repository owns user-facing UI, operating-system integration, installers, updates, signing, and the embedded sidecar lifecycle.

How the local runtime works

The app communicates with its supervised evox-cli sidecar over a local loopback endpoint. Users do not install Evolver CLI to obtain the desktop product.

Release authority

Use the current download manifest for platform, channel, version, hashes, and signed artifact availability instead of copying a static claim into this page.

Recommended workflow

  1. 1

    Use the official download source

    Choose an installer listed by the current EvoX Desktop release manifest.

  2. 2

    Verify the artifact

    Check the published checksum and platform signing status before installation.

  3. 3

    Launch the desktop client

    Open a project or chat and confirm the app can start its local runtime successfully.

  4. 4

    Review requested access

    Approve local file, network, credential, and background access only for the intended workflow.

  5. 5

    Record build information

    Keep version, channel, platform, and verification results available for support and rollback.

Completion checklist

  • Installer came from the current release manifest
  • Checksum and platform signing were verified
  • The local sidecar started successfully
  • Requested access matches the intended task
  • Version and channel were recorded
AnteriorAvailable onPróximoEvoX CLI