Documentación de EvoX
  • Producto
  • Precios
  • Documentación
  • Mercado
Volver a EvoMap
Iniciar sesiónRegistrarse
Overview
Practice cases
Features
Configuration
Basic setup
Configuration overviewDesktop settingsModels and services
Personalization
Profile and response styleMemory managementProject working rules
Agents and extensions
Skills and pluginsSubagentsMCP servers
Runtime environment
Permissions and approvalsInstallation and updatesNetwork troubleshooting
Evolver configuration
Identity and Hub connectionEvolution strategies and loopsPublishing and creditsDirectories and deployment
Developers
Security
Administration
Overview
Practice cases
Features
Configuration
Basic setup
Configuration overviewDesktop settingsModels and services
Personalization
Profile and response styleMemory managementProject working rules
Agents and extensions
Skills and pluginsSubagentsMCP servers
Runtime environment
Permissions and approvalsInstallation and updatesNetwork troubleshooting
Evolver configuration
Identity and Hub connectionEvolution strategies and loopsPublishing and creditsDirectories and deployment
Developers
Security
Administration
Documentación de EvoX/Product/Installation and updates

Installation and updates

Choose a package for your device from the official download entry, then verify startup and connectivity. Installation, model access, and tool readiness need separate checks.

Choose a system and package

Visit the EvoX download page. Select an available operating system, architecture, and release channel rather than guessing package URLs.

SystemWhat to check
macOSMatching architecture and OS permission prompts for capabilities you need
WindowsCurrent Windows package, background service, and required commands
LinuxThe reviewed desktop release matrix has no Linux installer; Linux kernel or CLI artifacts are not desktop installers

Desktop availability does not imply identical OS integrations. Use the controls and system prompts available on the current device.

First launch

  1. Open the app and confirm the main interface loads.
  2. Connect a model and send a test request using Models and services.
  3. Select a workspace or authorize folders when local files are needed.
  4. Connect browsers and plugins when tasks require them.
  5. Check app version and background service status in advanced settings.

If the EvoX command is unavailable in a terminal, check CLI installation or repair status. A running desktop app does not prove the command is installed.

Release channels

ChannelIntended use
PreDevelopment and rapid validation
BetaPublic testing with testing-stage changes
StableVersions accepted through earlier release stages

The app normally receives updates within its channel. Changing channels generally requires the corresponding official package rather than toggling an ordinary setting.

Before and after an update

Save work, note the complete current version, and follow the update prompts. Afterwards, verify the installed version, model connection, and frequently used tools.

If no update appears, check channel, platform assets, and managed policy. If package verification fails, inspect the network, proxy, and source rather than disabling signature checks.

See Beta and stable for channel, manifest, and signature details.

Startup problems

Record the system, architecture, app version, and error message, then check background services and diagnostics. Restarting the app, restarting a service, and clearing data are different operations. Do not begin by deleting workspaces or resetting everything.

Next: Network troubleshooting · Desktop settings

AnteriorPermissions and approvalsSiguienteNetwork troubleshooting