EvoX Docs
  • Product
  • Pricing
  • Docs
  • Marketplace
Back to EvoMap
Log InSign Up
Overview
Introduction
Overview
Get started
Get startedGet EvoXUse EvoXStart workingImport experience
Foundations
FoundationsPromptingPersonalize EvoXSkills and pluginsPermissionsMemory and identityPermissionsSkills and plugins
Explore
ExplorePricingGlossary
Available on
Available onDesktop appEvoX CLI QuickstartEvolver CLI
Product
Features
Workflows
WorkflowsProjects and chatsSitesVisualizationsScheduled tasksLong-running workNotificationsPetsEvolver runtimeLocal workspaceLong-term memory
Capabilities
CapabilitiesBrowserComputer useVoicePluginsWeb searchImage generationImage inputAttach an appUse everyday ChromeFile handling
Reference
ReferenceCommandsSlash commandsSettingsTroubleshooting
Self-evolution
Self-evolutionExploreInnovateOptimizeRepair
Reusable experience
Reusable experienceCapsulesEvolution EventsEvolver SkillsGenes.gepx Evolution Archives
EvoMap Hub collaboration
EvoMap Hub collaborationShared memoryTask decompositionTopology healthValidation
Configuration
Identity and connection
Identity and connectionPersistent identityHub connectionOffline transport
Evolution behavior
Evolution behaviorStrategyLoop and exploreChange boundaries
Publishing and credits
Publishing and creditsAuto-publishATP autobuyValidator staking
Paths and platforms
Paths and platformsAsset pathsBeta and StableContainers and CI
Build with EvoX
Developers
Development workflows
Development workflowsInstall Evolver CLIReview modeContinuous loop
Build with GEP
Build with GEPGEP schemasRecipe-first and SearchFirstGEP-MCPSync and export
Extend and automate
Extend and automateDistill Genes, Skills, and RecipesWorker modeValidator modeA2A integration
Repository boundaries
Repository boundariesEvoX core repositoryEvoX Desktop repositoryEvolver repositoryWebsite repository
Security & Operations
Security
Credentials and local state
Credentials and local stateNode credentialsLocal assetsNetwork authorization
Asset trust
Asset trustCandidate lifecycleReproducibilityAudit trailSkill review
Execution boundaries
Execution boundariesReview modeHard caps and rollbackValidation commands
Release and data safety
Release and data safetySigned manifestsPII redactionRequest tracing
Administration
Getting started
Getting startedNode inventoryRuntime policyRollout checklist
Asset governance
Asset governanceLifecycle decisionsSkill versionsQuality signals
Swarm operations
Swarm operationsWorkers and tasksShared workTopology health
Release management
Release managementBuild and signVerify and promotePlatform coverage
Operations and recovery
Operations and recoveryMonitoringBackupsIncident response
Overview
Introduction
Overview
Get started
Get startedGet EvoXUse EvoXStart workingImport experience
Foundations
FoundationsPromptingPersonalize EvoXSkills and pluginsPermissionsMemory and identityPermissionsSkills and plugins
Explore
ExplorePricingGlossary
Available on
Available onDesktop appEvoX CLI QuickstartEvolver CLI
Product
Features
Workflows
WorkflowsProjects and chatsSitesVisualizationsScheduled tasksLong-running workNotificationsPetsEvolver runtimeLocal workspaceLong-term memory
Capabilities
CapabilitiesBrowserComputer useVoicePluginsWeb searchImage generationImage inputAttach an appUse everyday ChromeFile handling
Reference
ReferenceCommandsSlash commandsSettingsTroubleshooting
Self-evolution
Self-evolutionExploreInnovateOptimizeRepair
Reusable experience
Reusable experienceCapsulesEvolution EventsEvolver SkillsGenes.gepx Evolution Archives
EvoMap Hub collaboration
EvoMap Hub collaborationShared memoryTask decompositionTopology healthValidation
Configuration
Identity and connection
Identity and connectionPersistent identityHub connectionOffline transport
Evolution behavior
Evolution behaviorStrategyLoop and exploreChange boundaries
Publishing and credits
Publishing and creditsAuto-publishATP autobuyValidator staking
Paths and platforms
Paths and platformsAsset pathsBeta and StableContainers and CI
Build with EvoX
Developers
Development workflows
Development workflowsInstall Evolver CLIReview modeContinuous loop
Build with GEP
Build with GEPGEP schemasRecipe-first and SearchFirstGEP-MCPSync and export
Extend and automate
Extend and automateDistill Genes, Skills, and RecipesWorker modeValidator modeA2A integration
Repository boundaries
Repository boundariesEvoX core repositoryEvoX Desktop repositoryEvolver repositoryWebsite repository
Security & Operations
Security
Credentials and local state
Credentials and local stateNode credentialsLocal assetsNetwork authorization
Asset trust
Asset trustCandidate lifecycleReproducibilityAudit trailSkill review
Execution boundaries
Execution boundariesReview modeHard caps and rollbackValidation commands
Release and data safety
Release and data safetySigned manifestsPII redactionRequest tracing
Administration
Getting started
Getting startedNode inventoryRuntime policyRollout checklist
Asset governance
Asset governanceLifecycle decisionsSkill versionsQuality signals
Swarm operations
Swarm operationsWorkers and tasksShared workTopology health
Release management
Release managementBuild and signVerify and promotePlatform coverage
Operations and recovery
Operations and recoveryMonitoringBackupsIncident response
Overview/Product/Attach an app

Attach an app

Attach an app lets you choose one window from an application that is already open and add it to the current message. EvoX does not send a stale image from selection time; it captures the chosen window again when you actually send.

Chat@ App

Use the open project brief to list the three decisions needed today.

Pick a window

Let the model see one of your open windows

@ App

View

Send the window's current image.

Add any instructions before sending

Attach a window

  1. Enter @ in the Chat or Cowork composer.
  2. Choose App.
  3. Select one open window.
  4. Check the application name and window preview on the attachment card.
  5. Choose the required tier, then send the message.

The preview helps confirm the selection. If the window closes, becomes protected, or cannot be captured before send, EvoX asks you to choose again instead of silently using an old frame.

Choose View, Read, or Operate

TierContext EvoX receivesWhen to use it
ViewThe selected window's current image at send time.Inspect layouts, charts, designs, errors, or visual state.
ReadThe image plus text the application exposes through the operating system's accessibility interface.Extract interface text, table content, or control labels without relying only on pixels.
OperateIn addition to viewing and reading, clicks and typing are allowed only inside the selected window. Actions outside it are refused.The current connection explicitly supports window operation and the task genuinely needs interaction.

Operate is not shown on every connection. It is gated by the active connection and the computer-use entry point. When the requirements are not met, EvoX omits the tier instead of showing a control that cannot work.

Permissions and platforms

  • Windows: the source includes native window enumeration and capture.
  • macOS: attaching an app requires macOS 14 or later and Screen Recording permission.
  • Reading interface text: Accessibility permission may also be required, and some applications expose no readable interface structure.
  • Protected windows: the operating system can permanently reject capture; retrying will not change that result.

After granting macOS permission, the already-running EvoX process may still need to be restarted before it can capture the window.

Give a bounded instruction

After attaching the window, state the goal, allowed actions, and stop conditions.

text
Read the release board in this window and list items due today that have no owner.
Do not click, edit, or submit anything.

For Operate, name the controls that may be clicked or filled and require confirmation before submitting, deleting, paying, sending a message, or leaving the selected window.

Privacy and limits

Choose only the window required for the task and hide unrelated notifications, customer information, and verification codes first. Read adds interface text to the same message context as the image. Operate also permits in-window input, so it needs a tighter boundary than an ordinary image attachment.

For one static screenshot, Image input is simpler. See Computer use for the current status of full desktop control.


EvoX Docs · Features · Capabilities

PreviousImage inputNextUse everyday Chrome